Which Microsoft 365 workloads does the backup cover?
A Microsoft 365 backup should cover Exchange Online mailboxes, calendars and contacts, SharePoint sites, OneDrive for Business files, and Microsoft Teams data. Confirm how Teams chats, channel files and associated SharePoint or OneDrive content are protected, as coverage can vary between backup services.
Microsoft 365 backup coverage should include the cloud data, configuration and relationships needed to recover business information—not just the files visible in each application. A suitable policy normally covers the core Microsoft 365 workloads, together with the specific data types and permissions your organisation relies on.
Exchange Online coverage should extend beyond email messages. Check whether the backup includes user and shared mailboxes, calendar items, contacts, tasks, attachments, mailbox folders and relevant mailbox metadata. Confirm whether deleted items, archived content and mailbox permissions are included, as these may be treated differently from ordinary mailbox data.
SharePoint Online protection should account for both individual sites and the structure around them. This can include documents, libraries, lists, pages, site contents, versions, permissions and sharing settings. A backup that only protects documents may not recreate the working site accurately after accidental deletion, corruption or an administrative error.
OneDrive for Business coverage should include files, folders, versions, sharing information and ownership details. It is important to establish how the service handles files belonging to a departed user, transferred ownership, synchronised folders and data removed from the user’s active account. OneDrive content may also be connected to Teams conversations or shared working processes, so its recovery should be assessed in that context.
Microsoft Teams requires particular care because its data is distributed across several Microsoft 365 services. The backup should state whether it protects:
- one-to-one and group chat messages;
- channel conversations and replies;
- files shared in channels;
- files shared in private or group chats;
- team and channel structure;
- membership, ownership and permissions;
- meeting recordings, transcripts and associated files; and
- relevant meeting, application and configuration data.
Teams channel files are generally associated with SharePoint, while files shared in chats may be associated with OneDrive. Chat and channel messages can also be held in different Microsoft 365 locations. For that reason, selecting Teams in a backup console does not necessarily mean every related item is protected. The backup provider’s workload definition should explain whether these connected locations are captured together and whether they can be restored in a usable form.
Some Microsoft 365 services may fall outside the standard workload set or may have limited support. Examples can include Planner plans, Forms responses, Lists, Loop content, Power Platform data, application settings, meeting recordings and certain tenant-level configuration. These services should not be assumed to be protected merely because the organisation uses the same Microsoft 365 tenant. Ask for a documented coverage matrix that identifies supported data, excluded data, retention behaviour, recovery options and any licensing or configuration requirements.
Coverage also needs to be considered at the level of identities and access. A backup may preserve the content but not recreate the original user account, group, permission assignment, sharing link or external collaborator. Check whether restores can be directed to the original location, an alternative account, a new site or an export, and whether metadata such as timestamps, owners, versions and permissions is retained.
For a practical assessment, list every Microsoft 365 workload used by the business and map it to the information that would be needed after a deletion, departure or security incident. S2 IT can help organisations review that coverage against their actual Microsoft 365 configuration, rather than relying on a general claim that the tenant is backed up.
Microsoft 365 backup coverage should be checked whenever the tenant changes. New users, shared mailboxes, sites, teams and groups may not be included automatically, depending on how the backup policy identifies protected workloads. Confirm whether protection is assigned by user, group, site, workload or licensing status, and whether newly created objects are discovered without manual intervention.
Also check how the service treats inactive accounts, service accounts, guest users and objects removed from an active policy. These details can create gaps even when the main Microsoft 365 applications appear to be covered. A useful review should compare the backup console with the organisation’s current tenant inventory and record any objects that require separate inclusion.