Articles

Configuration drift in Microsoft 365: how to find what changed

The tenant you configured a year ago is not the tenant you have today. Nobody decided that. It happened one small change at a time.

Where drift comes from

  • Temporary exceptions. A user is excluded from a Conditional Access policy for a trip, a mail flow rule is disabled to get one message through, and nobody comes back to undo it.
  • Many hands. Several administrators, a help desk and a service provider all hold rights to change settings, and none of them sees what the others did.
  • Microsoft. New settings arrive with a default, existing defaults change, and features move between admin centers.
  • Troubleshooting. A setting is loosened to rule it out as the cause. The cause turns out to be something else. The setting stays loose.

Each change is small and reasonable. Together they are the difference between the tenant you think you have and the one you have.

Why the built-in tools show only part of it

  • The audit log records events, one at a time, across several logs, for a limited time. It can answer "who changed this policy on Tuesday" if you already know to ask. It cannot answer "what is different from March".
  • Secure Score compares the tenant with Microsoft's recommendations, not with your own decisions. A deliberate exception and an accidental one look the same.
  • The admin centers show the present. Their settings pages do not keep the earlier value of a setting.
  • Tenant Governance configuration monitors, in the Microsoft Entra admin center, are the exception and the newest of these. With Microsoft Entra ID P1 or P2, a monitor compares the tenant with a baseline you supply every six hours and lists what differs. It reports and does not restore, it covers only the resources in your baseline, within a quota, and Microsoft keeps its snapshots for seven days. How to detect configuration drift in Microsoft 365 sets it beside the other options.

Finding drift needs two things the tenant does not keep for long: a copy of the configuration at a known date, and a way to compare it with today.

Doing it yourself

The approach is simple and the work is in the upkeep:

  1. Export on a schedule. Read the settings you care about with Microsoft Graph PowerShell and the Exchange Online and Teams modules, and write them to files, as JSON.
  2. Remove the noise. Timestamps, version counters and the order of lists change on their own. Strip them, or every comparison shows hundreds of differences that mean nothing.
  3. Compare. Keep the files in a Git repository and read the difference between two dates.

Microsoft365DSC, a free tool from Microsoft's community, automates much of this for people who are comfortable with PowerShell Desired State Configuration. Either way you own the scripts: Microsoft changes its interfaces often, and the export that worked in spring needs attention by fall. How to detect configuration drift in Microsoft 365 has a working script, an audit log alert and the other options side by side.

What GlacierPoint Snapshot does

  • A copy at a known date. A backup reads 484 configuration types across 9 admin centers: Entra ID, Exchange Online, Defender, Purview, SharePoint and OneDrive, Teams, Intune, Power Platform and the Microsoft 365 admin center. Scheduled backups run daily or weekly on a computer you choose.
  • A comparison without the noise. Compare a backup with the tenant as it is now, or two backups with each other. Values that change on their own are left out, so what remains is what somebody changed: added, removed, or changed, setting by setting, with the old value beside the new one.
  • A way back. For a change you did not want, tick the item and restore it, after a preview, with a journal that can roll the restore back. A change you did want stays; the next backup records it.

The app runs on your computer and signs in as you. We hold no access to your tenant, and you can keep the backups on your own computer. More on security, and every permission by name.

Start free