Articles

What is Microsoft 365 configuration backup, and why Microsoft does not do it for you

Microsoft 365 configuration backup is a dated copy of the tenant's settings and policies, the Conditional Access policies, mail flow rules, Intune profiles and the rest, that you can compare with today and restore from. It is a different thing from data backup, which copies mail, files and chats.

Most Microsoft 365 backup products do the second, and a tenant can have every mailbox backed up and no copy of a single policy. Microsoft has started building the capture side of configuration backup. It has not built the restore side.

What does Microsoft keep for you?

More than nothing, and less than people assume:

  • Recycle bins. Deleted users and Microsoft 365 groups can be restored for 30 days, deleted app registrations too, and SharePoint and OneDrive keep deleted files for 93 days.
  • Retention. Retention policies in Purview keep mail, files and chats for as long as you set.
  • The audit log. It records that a setting changed, who changed it and when, for a limited time that depends on your license.

All three are about data or about events. None of them keeps a setting as it was.

What does Microsoft not keep?

The admin centers save a change the moment you press Save and keep no earlier version of it. That leaves gaps like these:

  • A previous version of a Conditional Access policy. Entra can bring back a policy deleted in the last 30 days, but a policy that was changed has nothing to go back to.
  • A deleted transport rule. Exchange Online has no recycle bin for mail flow rules. The audit log shows the cmdlet that removed it, not the rule.
  • An Intune profile as it was. A configuration profile edited last week, or deleted outright, cannot be recovered by Microsoft.

The audit log is often mistaken for a backup. It tells you a policy changed on Tuesday. It does not give you Monday's policy.

Which settings change most and break hardest?

Five areas account for most bad days:

  • Conditional Access. One wrong condition can lock out the whole organization, or quietly let everyone in.
  • Mail flow rules and connectors. A rule that redirects or drops mail, or a connector that points at a gateway you retired.
  • Anti-phishing and spoof settings. Turned down to let one sender through, and never turned back up.
  • Intune compliance and configuration profiles. A compliance policy feeds Conditional Access, so a broken one can block every device at once.
  • Sensitivity labels. A changed label can alter encryption and access on every document that carries it.

How do people do it by hand today?

Three approaches, each useful, each with a limit.

Graph exports. Microsoft Graph PowerShell reads most Entra and Intune settings, and a short script writes them to JSON on a schedule. The limit is that a policy is mostly references: groups, named locations and filters by ID. Intune spreads across many endpoints, several of them beta, and secrets inside profiles are never returned. You get files, not a way to put them back.

Export-TransportRule. Exchange Online can export the whole rule collection as one XML file, and Import-TransportRule loads it again. It covers mail flow rules only, not connectors, anti-phishing or anything else, and it brings back the collection as a whole rather than one rule from last Tuesday. Read the documentation on what an import does to the rules already there before you run it.

Microsoft365DSC. An open-source PowerShell module, led by Microsoft engineers and maintained by the community, that exports a tenant's configuration as a Desired State Configuration file across many workloads and can compare two exports. It is the most complete free option. It also expects you to be at home with PowerShell DSC, to keep a long list of dependent modules current, and to apply a restore as configuration, which is a different act from putting one policy back after previewing it.

All three leave you owning the scripts, and none of them warns you when a Microsoft change to an endpoint or a cmdlet means a setting is no longer being captured.

What about Microsoft's own snapshot API?

As of October 2026, Microsoft has Tenant Configuration Management APIs in public preview on the Microsoft Graph beta endpoint, under admin/configurationManagement, often called Unified Tenant Configuration Management (UTCM). Microsoft presents them as the supported path forward from Microsoft365DSC, and the Microsoft365DSC site itself now points its users to them. They cover three things:

  • Baselines. A configurationBaseline describes the settings you expect.
  • Snapshots. createSnapshot captures named resource types, such as microsoft.entra.conditionalAccessPolicy. It runs as a job, and you fetch the result through configurationSnapshotJobs.
  • Monitors. A monitor watches named resource instances for drift from the baseline.

Community reports say a snapshot is kept for seven days, so you have to export and store it yourself. The APIs are in preview and subject to change. There is no restore of a single item with a preview and a rollback. Microsoft now helps with taking the copy; putting a setting back is still your job.

What does a real backup need?

A pile of JSON files is a record. A backup needs three more things:

  1. A diff between two points in time. Compare last Friday with this morning, or a backup with the tenant as it is now, and see each added, changed and removed setting with the old value beside the new. Without that, nobody finds the change in time. Configuration drift in Microsoft 365 covers why the built-in tools do not show it.
  2. A restore that previews and can roll back. Read the tenant first, show what would be recreated or updated, write nothing until someone confirms, and keep a way to undo the restore itself.
  3. A journal. Every restored item with its value before and after, and who ran it. That journal is what makes the rollback possible, and it is what you show when someone asks what happened.

How often should you back it up?

Daily, for most tenants. Settings change in small steps all week, and a weekly copy can miss the version you need. Also take one before any planned change: a migration, a new baseline, a change of service provider. Keep the history long enough to reach back past the time it usually takes someone to notice a problem, which is often weeks.

A backup lets you put a setting back. It does not explain to a new administrator why the setting is there; for that, keep a written as-built document alongside it.

Would you rather not maintain the scripts?

If you would rather not keep the exports and the restore scripts running, GlacierPoint Snapshot backs up 484 setting types across 9 admin centers, compares any two backups, and restores the settings you pick with a preview first and a rollback after.

Start free