Ask an IT team whether their Microsoft 365 data is backed up. You will usually get a confident yes. 

Then ask a follow-up. What happens if a finance director deletes a mailbox folder in March and nobody notices until June? The confidence tends to fade around that point. 

Microsoft 365 retention policies preserve data for compliance. They do not restore it. Under Microsoft’s shared responsibility model, Microsoft guarantees platform availability and infrastructure resilience while the customer remains responsible for the data itself. Standard Microsoft 365 licenses do not include a backup solution, and the native recovery windows are shorter than most organizations assume. 

Does Microsoft Back Up Your Microsoft 365 Data? 

Not in the way the word is normally used. 

What the platform gives you is a set of recovery windows. Deleted items sit somewhere for a defined period, then they are gone. Useful, but not a backup.

A backup is an independent, point-in-time copy that can be restored to a known good state after the fact. A recycle bin is a delay before permanent deletion. That difference stays theoretical right up until it isn’t: ransomware encrypting synced content, a departing employee clearing out a mailbox, a retention policy misconfigured and pushed tenant-wide, or a quiet deletion that surfaces four months later. 

Retention labels and litigation holds add preservation, which is genuinely useful and constantly mistaken for protection. A hold stops data from being purged. It will not roll a SharePoint library back to how it looked last Tuesday. 

Why This Surfaces During Migrations 

Nobody tests these assumptions on a normal Tuesday. A cutover forces the issue. 

Data moves, source systems get decommissioned, and someone asks three months later where the pre-migration state went. We see the same three things: archives stranded on a server nobody switched off, retention policies never rebuilt for the destination tenant, and a recovery expectation that was never accurate to begin with. Our work on data archival planning and implementation covers how to set that baseline before a migration rather than after, and our guidance on protecting sensitive information during Office 365 migrations covers the controls that belong in the plan. 

Questions We Keep Getting 

Q: Does Microsoft back up my Microsoft 365 data?  
A: Not under a standard license. Microsoft’s shared responsibility model covers platform availability and infrastructure resilience. The data remains yours to protect, through the native add-on or a third-party tool. 

Q: How long can deleted data actually be recovered? 
A: In Exchange Online, purged items stay in the Recoverable Items folder for 14 days by default, extendable by an administrator to 30 days maximum. In SharePoint Online and OneDrive, deleted items stay in the site and site collection Recycle Bins for a combined 93 days, and that period is not configurable. 

Q: Isn’t a retention policy the same as a backup? 
A: No. Preservation stops data being purged. It does not create a restore point, and it cannot return a site or mailbox to a previous state. 

Q: What does Microsoft 365 Backup cost and cover? 
A: It is a pay-as-you-go add-on billed through Azure at $0.15 per GB per month of protected content, with restores included and data retained for 365 days. Exchange restore points are captured every 10 minutes across the prior year. For SharePoint and OneDrive, restore points older than two weeks become weekly snapshots. 

Q: What about Teams chat? 
A: Teams messages live in hidden mailbox folders that end users cannot restore from, so confirm coverage explicitly rather than assuming it. Under FRCP Rule 37(e), collaboration data carries the same spoliation exposure as email. 

How Messaging Architects Can Help 

We assess what your tenant actually protects, where retention ends and recovery begins, and which regulatory obligations need more than native tooling delivers. More on how we work sits on the Messaging Architects blog and at our parent company, eMazzanti Technologies. 

Test a restore before you need one. That exercise settles the question faster than any policy document will.