A huge challenge for any organisation managing a Microsoft 365 tenant is the slow and painful drift away from the desired configuration over time. A configuration that you either spent a lot of time implementing yourself, or paid a lot of money for someone else to implement. Personally, I have worked with organisations which have built their own scripts and for MSP’s which have invested in third-party tools, all to solve this problem.
Now, Microsoft are putting their foot it in with their new Unified Tenant Configuration Management feature (or UTCM for short) which enables admins to control, manage and monitor configuration settings across single or multiple workloads.
While this feature hasn’t been clearly announced yet, and the Graph API’s endpoints are blocked for public use, I’ll explore what we know from the API documentation so far.
Page Contents
What is Unified Tenant Configuration Management (UTCM)?
Right now, Unified Tenant Configuration Management (UTCM) is a set of APIs within Microsoft Graph that provides a native way to control and manage configuration settings and monitor drift across your Microsoft 365 workloads.
At its core, it solves the problem of “configuration drift”. It allows you to take a snapshot of your current configuration to serve as a “source of truth” (or baseline). Once you have that baseline, you can create monitors that periodically check your actual tenant configuration against your saved baseline.
If a setting in the tenant doesn’t match your baseline, the API flags it as a drift. Simple as that, nothing fancy or overly complex, just a “good enough” way to monitor for drift in your Microsoft 365 tenant.
Key Concepts
To understand how to leverage UTCM, you need to get your head around three main resources exposed by the API:
Configuration Snapshots
A snapshot is a point-in-time capture of your tenant’s configuration settings which is the foundation of the drift detection process. You can use the configurationSnapshotJob resource to extract settings from your tenant. You can extract up to 20,000 resources per tenant per month and snapshots are kept for 7 days before being automatically deleted.
Configuration Monitors
Once you have your desired configuration (or baseline), you create a Monitor. The monitor component of UTCM that compares your live tenant settings against your baseline. Monitors run automatically every 6 hours and you cannot currently change this frequency.
You can create up to 30 monitors per tenant. However, there is a strict limit on the volume of resources you can monitor: 800 configuration resources per day. Also, if you update the baseline of a monitor, all previous drift history for that monitor is wiped, so you need to be careful when making changes.
Configuration Drift
When a monitor runs and finds a difference to the baseline, it generates a configurationDrift record. This detail allows administrators to review exactly what changed and when. Each active drift stays available until you resolve them. Then, once a drift is marked as “fixed”, it is retained for 30 days before deletion.
Supported Microsoft 365 resources
UTCM support workloads from the following key Microsoft 365 services:
- Microsoft Defender
- Microsoft Entra
- Microsoft Exchange Online
- Microsoft Intune
- Microsoft Purview
- Microsoft Teams
From these supported services, in total UTCM support more that 300 different resource types each of which will have various associated properties. A full breakdown of the schema and all supported properties, including there types, are publicly hosted here: schemastore.org/utcm-monitor.json.
UTCM or Third-party?
If you have been managing Microsoft 365 tenants for a while, you may already be using tools like Microsoft 365 DSC, Inforcer, CoreView or CIPP (just to name a few) to manage the exact problem that UTCM sets out to help solve. But, does UTCM make these tools redundant? well not just yet… Here is comparison of some key points:
| Feature | UTCM (Native) | Third-Party (Non-native) |
|---|---|---|
| Maturity | Beta (Preview). APIs are subject to change and may have rough edges. | High. Mature communities and established support models. |
| Interface | API Only. Currently, there is no nice UI in the admin portal. You must build your own reporting or use Graph Explorer. | Rich UI. Dashboards, "single pane of glass" views, and visual diff reports are standard. |
| Multi-Tenancy | Do-it-Yourself. You can build scripts to check multiple tenants, but it requires development effort. | Native. Designed specifically for MSPs to push one baseline to 50+ tenants instantly. |
| Remediation | Detection Only. UTCM flags the drift, but you must manually fix it or write a script to revert it. | Auto-Fix. Many tools offer "fix my drift" buttons or automated remediation pipelines. |
| Cost | Likely Included. While API limits apply, this is built into the platform (subject to GA licensing). | Variable. SaaS tools often have per-user costs. |
Wrapping up
It would have been great to explore and be hands-on with these new API’s, however being so early days, they look to be in a state of development or “private preview” where only white listed tenants can use it.
Inherently also, there is no mention of licensing requirements for this product in the documentation yet. Maybe, it will be licensed similar to Baseline Security Mode, where you just need to license the core products you are monitoring and the monitoring product itself is free. I’m sure we’ll find out nearer its release, which is also unknown.


Greate Articel, thank you very much Daniel!
I testet it out…. I have some problems with the “resourceLocation”. My snapshots are failing. Do you have the same behavior? Is it still limited in some regions, do you know this?
Thanks a lot Stefan
I think there are some limitations while in preview, so supported resources are hit and miss… 🙂