Microsoft 365 Backup: Exchange, OneDrive and SharePoint Data

Microsoft 365 backup: shared responsibility, limits of built-in retention features, tool selection criteria, Teams coverage and typical restore tasks.
Technical summary
Technology
Microsoft 365, Exchange Online, OneDrive, SharePoint Online, Teams, Microsoft 365 Backup, Microsoft Graph
Topic
Independent backup and restore of Microsoft 365 data
Level
Intermediate
Prerequisites
  • Microsoft 365 global administrator or relevant role permissions
  • Exchange Online PowerShell module
  • Corporate retention policy
In this article8 sections

“We moved to Microsoft 365, so we don’t need backups anymore.” This assumption causes trouble when a deleted project folder is looked for months later. Microsoft takes responsibility for the availability of the service and the resilience of the infrastructure. Returning data lost through user error, malicious deletion, ransomware or a faulty synchronization to the date you want is your job. Below we explain how built-in retention features differ from real backups, the scenarios that require backups, tool selection criteria and typical restore operations. So that restore tests can be used in audits, record the scope, the result and the owner of the evidence within backup and restore testing audits.

The shared responsibility model

In the SaaS model, responsibility is split into layers. Microsoft manages the physical data center, hardware, application infrastructure and replication between data centers. This replication protects the service against the loss of a data center; but a deletion or encryption done on your side is reflected to all copies just as fast. Replication isn’t backup. What remains on the customer side:

  • The data itself and who can delete what (authorization).
  • Identity security: a deletion made by a compromised account is a legitimate operation from Microsoft’s point of view.
  • Retention periods, legal retention requirements and the data of departing employees.
  • An independent copy from which you can restore data as of a specific date.

Service continuity, i.e. how the workflow continues during Microsoft 365 outages, is a separate topic and is described in the continuity in Microsoft 365 and cloud infrastructure article. The topic here is independent protection of data.

Built-in retention features and their limits

Microsoft 365 offers several mechanisms to bring back deleted items for a certain time. They are useful, but they aren’t backups: they are kept within the same service, accessible to the same administrator accounts, and for a limited time.

Feature Default behavior Limit
Exchange Recoverable Items Deleted items are kept for 14 days; can be increased to 30 days Permanently deleted when the period expires
Deleted mailbox The mailbox of an unlicensed/deleted user can be recovered for 30 days Permanently deleted after 30 days
SharePoint/OneDrive recycle bin Two stages, 93 days in total Permanent deletion or expiry
Version history Versions are kept in document libraries Depends on the version limit and library settings
OneDrive/SharePoint “restore” Returns the library to a point within the last 30 days Limited to 30 days, affects the whole library
Purview retention policies and holds Protect content even if it is deleted A compliance tool; not designed for bulk restore

Default values can change over time; verify the current settings in your own tenant against Microsoft documentation and the admin center. One of the first settings we recommend in new tenants is raising the Recoverable Items period to 30 days with Exchange Online PowerShell:

Connect-ExchangeOnline
Get-Mailbox -ResultSize Unlimited | Set-Mailbox -RetainDeletedItemsFor 30
Get-Mailbox -SoftDeletedMailbox | Select DisplayName, WhenSoftDeleted

The most misunderstood feature is retention policies. They protect content in a hidden area and make it findable with eDiscovery; but they aren’t a suitable tool for returning a user’s 3,000-file folder to a specific date with its original folder structure and permissions. A compliance tool, not a restore tool.

Scenarios that require backups

  • Ransomware and mass encryption: The OneDrive sync client uploads encrypted files to the cloud. If noticed within the 30-day restore window, you can go back with the built-in tool. If noticed late, or if versions were affected too, an independent copy is needed.
  • Malicious or compromised administrator: With administrator rights, permanent deletion, emptying the recycle bin and changing retention settings are possible. An attacker does these first.
  • Departing employee: The mailbox and OneDrive of a user whose license is removed are deleted when the period ends. When a legal need arises months later, the data may be gone.
  • Deletion that goes unnoticed for a long time: If a folder deleted from a project site is looked for six months later, the recycle bin period has long expired.
  • Faulty bulk operations and migration: A wrong PowerShell script, a sync tool or an error made during a tenant-to-tenant migration can affect many objects.

Backup tool selection criteria

There are two main paths: Microsoft’s own product, Microsoft 365 Backup, and third-party backup products (Veeam Backup for Microsoft 365 and similar). Compare these criteria, not the brochure:

Criterion Microsoft 365 Backup Third-party solution
Storage location Within the Microsoft 365 service boundary On-premises repository, object storage or the provider’s cloud
Restore speed Focused on large-scale restore Depends on API throttling
Scope Exchange, OneDrive, SharePoint Teams, groups and other workloads, depending on the product
Independence Same provider, separate management layer Different environment and identity infrastructure possible
Billing Usage-based, through an Azure subscription License + storage cost

Before buying, also ask these questions:

  • API and throttling: Does the tool use Microsoft Graph or the APIs Microsoft offers for backup? Is it compatible with the deprecation timeline Microsoft announced for Exchange Web Services (EWS)? In large tenants, the first full backup can take days because of throttling; put this on the calendar.
  • Identity isolation: Are the backup console and repository protected with credentials independent of Microsoft 365 administrator accounts? Is immutable storage supported?
  • Data residency: Is the region where backups are kept compatible with personal data processing obligations?
  • Granularity: Can you restore a single email, a calendar item, a file version, and a site together with permissions? Is export to a different location or as PST/files available?
  • Backup frequency: How many recovery points can be created per day? This directly determines the RPO.

The workloads and retention periods supported by Microsoft 365 Backup keep changing; verify the coverage in Microsoft’s current documentation.

Coverage: Exchange, OneDrive, SharePoint, Teams

Exchange Online: User and shared mailboxes, archive mailboxes, calendars and contacts. Since shared mailboxes can be unlicensed, they are out of scope in some tools. This is an item often skipped; check one by one that they are included.

OneDrive: Users’ personal files. If departmental data moved from on-premises server infrastructure has mistakenly stayed in OneDrives, that data is at risk when the employee leaves; this topic is covered for migration planning in the migration from file server to SharePoint and OneDrive article.

SharePoint: Site collections, document libraries, lists and permissions. Every team created with a Microsoft 365 group or Teams has a SharePoint site behind it. If the backup job was set up by selecting sites one by one, the team created last month isn’t in the backup. Define the scope with an automatic inclusion rule.

Teams: Team files are kept in SharePoint, and channel and chat messages in Exchange-based storage. A “full” Teams backup therefore consists of multiple sources. In some products, message backup requires protected APIs that Microsoft charges for separately. See that channel messages and private and shared channels are really covered by restoring in your own tenant, not in a demo environment.

Restore scenarios

A single email or folder

If the item is within the Recoverable Items period (14 days by default, 30 days at most), “Recover deleted items” in Outlook is enough. If the window has passed, an item-level restore is done from the backup tool. Restore to the original mailbox as a separate folder; it doesn’t mix with existing data, and the user sees what came back.

A whole site or library

In a ransomware or faulty bulk operation, the first job is finding the time of impact; look in the audit log for the minute the bulk change started. If the incident is within 30 days, SharePoint’s library restore feature is a fast option; otherwise a recovery point from before the incident is chosen in the backup. Time first, then restore. A deleted site collection within its retention period can be brought back from the SharePoint admin center or with the Restore-SPODeletedSite cmdlet.

Departing employee

Decide the fate of the data before the license is removed: converting the mailbox to a shared mailbox, keeping it as an inactive mailbox with a retention policy, or keeping it only in the backup. If the license was removed 30 days ago, time is short. To move content from a deleted mailbox to another mailbox, this method is used in Exchange Online:

$deleted = Get-Mailbox -SoftDeletedMailbox -Identity "[email protected]"
New-MailboxRestoreRequest -SourceMailbox $deleted.ExchangeGuid `
  -TargetMailbox "[email protected]" `
  -TargetRootFolder "Ayse Yilmaz" -AllowLegacyDNMismatch

Implementation checklist

  • Have the workloads to back up and the objects to exclude been defined in writing?
  • Do new users, shared mailboxes, groups and sites enter the scope automatically?
  • Is the backup repository protected independently of Microsoft 365 administrator identities?
  • Is the retention period consistent with the corporate retention policy?
  • Has the first full backup been completed, and is the duration of subsequent incremental backups monitored?
  • Are single-item, single-user and one-site restore tests done every quarter?
  • Has the departing employee process been documented together with the backup and licensing steps?

In terms of copy count and testing discipline, the 3-2-1-1-0 backup rule applies to Microsoft 365 data too. You can find how we handle tenant configuration and backup setup on our Microsoft 365 and cloud services and backup and disaster recovery pages. For the scope of Microsoft’s own solution, the Microsoft 365 Backup overview document is the starting point.

Frequently asked questions

Doesn’t Microsoft 365 already back up my data?

Microsoft protects the availability of the service by replicating its infrastructure and offers a way to bring back deleted items for a limited time. An independent backup, separate from administrator accounts, from which data as of a specific date can be restored, is the customer’s responsibility.

Do the recycle bin and retention policies replace backup?

They don’t. The recycle bin and Recoverable Items are time-limited; retention policies are for compliance and aren’t designed for bulk restore with folder structure and permissions. All of them stay within the same service and the same administrator access.

Should we choose Microsoft 365 Backup or a third-party solution?

Microsoft 365 Backup offers fast, large-scale restores within the service boundary. Third-party solutions keep data in a different environment with independent identity. Evaluate storage location, coverage, restore speed and cost together.

What should be checked in Teams backup?

Teams data lives in more than one place: files in SharePoint, messages in Exchange-based storage. Test in your own tenant that the tool really covers channel messages and private and shared channels, and whether it uses paid APIs if needed.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek System Support

Server installation, configuration, incident response and scheduled maintenance. Active Directory, virtualization and backup are managed with the same discipline.

Knowledge Center

Other articles