#AvePoint Cloud Backup for Microsoft 365 January 2022

Release Date for the Commercial Environment: January 9, 2022

Release Date for the U.S. Government Environment: January 16, 2022

• Cloud Backup for Microsoft 365 now provides the backup and restore capability for Yammer communities.

• For customers using SharePoint Online, Exchange Online, Project Online, Teams, Microsoft 365 Groups, or Yammer service, you can now use the Global Search function to search for sites or mailboxes across the services to restore.

• [BYOS] A tooltip is now displayed when you provide Azure storage account information on the Storage Location page. If you configured a firewall on your Azure storage network, you need to follow the steps in the user guide to configure ARM VNet rules or add reserved IP addresses.

• The design of the Restore page has been improved. The Restore page now provides two entries for finding the items to restore. You can choose the classic one to search with specific properties of an object type or drill down to a specific recovery point of that service, or you can choose to use the Global Search function to search across all sites or mailboxes that have been protected by Cloud Backup.

• [Yammer] In the Restore wizard, you can use either the Yammer community address or display name to search for Yammer communities that you want to restore.

• [Teams] Support restoring channel conversations as posts for customers who are using app profile authentication to scan Teams.

• Updated the service type logos in Cloud Backup for Microsoft 365.

• You can now restore private channels that have been renamed to their original location.

• The Object ID is now used as the unique identifier for Exchange Online mailbox and Public Folder.

• We supported hosting the BYOS index file on AvePoint storage in the November 2021 release and manually synchronizing the index from AvePoint storage back to BYOS. In this release, there is now a timer job to automatically sync the index back to BYOS.

• Objects protected by Exchange Online backup job will appear Failed in the job report if it already has six consecutive failed backup attempts.

• [On-Demand Feature] By default, the successful item level objects will not be included in the job report. If you want to view the successful item level objects in the job report, contact AvePoint Support for assistance.

• If you have appended a new storage account as a storage location and your legacy storage location can no longer be accessed, the incremental backup jobs to start later will fail. However, if the backup job is a full backup job of a new cycle, it will not be impacted in this case.

• Added a new error code "SP-CannotCreateSubsite" in job reports for troubleshooting. If your tenant does not allow the creation of subsites, the subsites cannot be restored.

• If you are using app profile authentication to scan public folders and have configured service account pools for Exchange Public Folders, the Cloud Backup job can automatically use the service account pool users to run a backup.

• If you use the app profile authentication method to scan the Teams, the restore job to restore the channel conversations as posts will restore the messages in the name of the Microsoft Delegated app authentication user.

• The Data export feature in Cloud Backup for Microsoft 365 Standalone Tool will use the object ID as the unique identifier for the mailbox.