Notes for Microsoft 365

Last published : Apr 02, 2026
Note the following points:
General notes
  • For primary backups, Forever Incremental, Consolidate full, and Custom full templates only deduplication disk storage is supported. Duplicate backups can be targeted to any supported storage.
  • When you run any Microsoft 365 consolidate full job, ensure that no other jobs are running on the deduplication disk storage.
Exchange notes
  • For Exchange Online restore, ensure that the destination mailbox is already created.
  • For Exchange Online restore, only the name, comment, permissions, and retention settings for folders are restored.
OneDrive notes
  • For OneDrive restore, ensure that the user OneDrive is already created.
  • For OneDrive restore, to receive an email invite for direct access permission that is shared with groups, you must enable the Let people outside the organization email the groups setting and click Save. To enable the setting, go to Edit group > About > Edit settings.
    Note: This setting is only available in the Microsoft 365 portal and does not exist in Backup Exec.
  • For OneDrive, Deep Directory only supports restore of a specific number of items. For more information, refer to the following link:
https://docs.microsoft.com/en-us/answers/questions/597035/is-there-any-number-restriction-of-sub-folders-in.html
  • For OneDrive Notebook restore, if the Notebooks folder is not available in the root directory, it is created automatically.
  • For OneDrive, backup of Preservation Hold Library is supported but you can only restore Preservation Hold Library to a file system.
  • For OneDrive, only the latest version of the item at the time of a backup, is protected as part of that backup job.
SharePoint notes
  • For SharePoint, if any list item attachments are removed or updated after a backup is completed, those attachments are restored as a part of the restore operation. The restore operation does not delete or modify any attachments, which are not part of the backup data.
  • For Sharepoint, TLE (Top Level Entity) and Site name are always the same. The restore browse view also displays the same names.
  • If a document is backed up with pending approval status, it is approved during the restore operation.
  • After a new SharePoint site is created, Microsoft API may take some time to make the site available for backups in Backup Exec.
  • When you restore an event, ensure that you select all the records for repeated events from the restore browse view.
  • If you restore a deleted non-repeated event multiple times, duplicate entries of the event are created.
  • During file system restore, in the folder created for each event, any character that is not allowed in the file/folder name is replaced with an underscore (_).
  • SharePoint Online only restores the latest version of the item and for file system restore, all versions are restored.
  • For a list or document, field level unique constraints, validation formula, and custom content type required constraint are not changed during restore. If the constraints and validation formula are changed after backup, it is recommended to keep them consistent with backup.
  • The Site Actions within Managed site features are always restored, irrespective of the Backup Exec overwrite settings.
  • After upgrade, all items with unique permissions are backed up again. Size of the first incremental can be larger.
  • If the restore of settings or permissions fail, the restore job is not marked as failed. The job is marked as success with exception.
  • If there is a change in the permission of an item, then the entire item is backed up again.
  • Restore of the Restricted View role is supported on entity level. In case of disaster recovery, restricted view role is not restored for any entity.
  • If the backup has a default group with new name, then in case of a disaster recovery scenario, you can see two groups. One is the default group created by SharePoint site and the other is created from the backup.
Teams
  • Microsoft Teams backup is performed using Graph Export APIs. These are metered APIs and there is a cost associated with the download of each message with these APIs. Refer to the Microsoft documentation for more information about the associated cost.
https://learn.microsoft.com/en-us/graph/teams-licenses \- model=B
Get messages across all channels \- under model=B
BackupExec uses model=B based on the recommendation by Microsoft.
  • The following applications in channel tabs are protected and can be restored: PowerPoint, Excel, SharePoint, PDF, Word, OneNote, Visio, Power BI, Planner, Document Library, Website, Polly, and Whiteboard. The tabs display applications only if the reference data is available.
Applications added to a conversation are supported for backup and restore if Teams creates a channel tab for them. Applications that are added directly to a conversation without creating a tab are not supported for backup and restore. For example, PDF and Power BI.
  • After the restore operation, you may see messages with the name of the Azure AD application that was created during tenant configuration. This is because the restore operation works in the context of the Azure AD application and not in the context of any specific user.
  • After backup, if a Teams user gets a higher privilege role assigned (for example, owner) then the restore process does not revert this role. The higher privilege role is preserved.
  • For file system restore, the folder hierarchy is created based on Teams site url path. Sites include Teams site and Private channels site.
Related information