Considerations and Limitations

This section lists considerations and known limitations in Veeam Backup for Microsoft Office 365.

In This Section

Infrastructure

  • Veeam Backup for Microsoft Office 365 does not support encryption at-rest for the following types of backup repositories:
  • A local directory on a backup proxy server.
  • Direct Attached Storage (DAS) connected to the backup proxy server.
  • Storage Area Network (SAN).
  • Network Attached Storage (SMB 3.0 shares).
  • Backup proxy servers and the Veeam Backup for Microsoft Office 365 server must be deployed within the same or a trusted domain.
  • [For Microsoft Outlook] Preliminary releases such as Insider releases or releases provided by Monthly Channel Updates are not supported; Veeam Backup for Microsoft Office 365 supports only RTM/GA versions. For more information, see this Microsoft article.
  • If the Veeam Backup for Microsoft Office 365 console and a management server are deployed on different machines, make sure that the management server is trusted for delegation. For more information, see this Microsoft article.
  • If any of the machines with any of the Veeam Backup for Microsoft Office 365 components have been renamed (or its FQDN has been changed), or any machine has been added to a different domain, then all the components become unavailable to each other. If any of the above has occurred on a server that acts as a backup proxy server, then such a server becomes Offline in the Veeam Backup for Microsoft Office 365 console. To make a server available, re-add it, as described in Adding Backup Proxy Servers.
  • IPv6 is not supported for Microsoft Azure China region.
  • Notifications about backup jobs completion results may not work properly for Microsoft Azure China and Germany regions.

Backup Repositories

Object Storage Repositories

Backup

Restore

For more information about enabling In-Place Hold and Litigation Hold, see this Microsoft article.

Related Topics

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.