Entra Tenant Governance at Ignite 2026: Cross-Tenant Drift Detection for MSPs (Preview)
I’m writing this in San Francisco between Ignite sessions, and of all the identity announcements this week, the one I keep coming back to isn’t the shiny agent stuff. It’s the boring one about configuration.
If you’ve ever looked after more than one Microsoft 365 tenant, you know the problem. You build a lovely Conditional Access baseline, you roll it out, and six months later someone has excluded “just one” account, a break-glass policy has been switched to report-only, and nobody can tell you when or why. Now multiply that across dozens of customer tenants and you’ve got the daily life of an MSP.
At Ignite 2026 Microsoft announced Microsoft Entra Tenant Governance cross-tenant configuration management and Microsoft Entra resource policy, both in preview. It’s in the Entra Ignite announcement blog and the Book of News, and honestly, it’s the piece I’ve wanted for years.
What Tenant Governance Actually Is
Tenant Governance is a family of capabilities rather than a single feature. The overview on Microsoft Learn breaks it into five parts:
- Related tenants: discovers tenants connected to yours through B2B collaboration, multitenant apps and shared billing accounts. Yes, that can include the shadow IT tenant marketing spun up three years ago, as long as it’s linked to yours through one of those routes. A completely standalone tenant won’t show up.
- Governance relationships: approved, least-privilege cross-tenant administrative access between a governing tenant and governed tenants.
- Configuration management: compare a tenant’s actual configuration against a baseline and report drift.
- Resource policy (preview): evaluates matching Microsoft Graph requests and helps prevent non-compliant changes at request time.
- Secure tenant creation: new add-on tenants come with a governance relationship from day one.
The Ignite news is that configuration management now works across tenants, and Microsoft is also extending Tenant Governance to Agent 365 and Copilot (also preview) so you can keep agent and AI settings consistent across an estate.
How Configuration Management Works
This is configuration-as-code, built on the Microsoft Graph Tenant Configuration Management APIs, which Microsoft says are generally available. The configuration management docs describe the moving parts:
- Snapshots capture the current state of a tenant’s resources as JSON. Grab one from a “known good” tenant and you’ve got the start of a baseline. One gotcha: snapshots and snapshot jobs are deleted after 7 days, so download them.
- Baselines are the JSON definition of how you want things to look. A Conditional Access policy, for example, is the
microsoft.entra.conditionalaccesspolicyresource, with properties likeExcludedUsers,IncludedGroupsandState. - Baseline templates (preview) let you reuse an approved baseline across monitors and deployments.
- Deployments (preview) push baseline settings to the home tenant or governed tenants.
- Monitors compare reality to the baseline. Per the overview, each monitor currently runs at six-hour intervals. Cross-tenant monitors are in preview.
- Drifts tell you exactly which property changed on which resource. Fix it and the next run marks the drift as
fixed. It tells you what changed, and roughly when (within a monitor cycle), but not who changed it, so pair it with the Entra audit logs to get the who and the why.
Coverage is broad. The overview says over 200 resource types are supported across Entra, Intune, Exchange Online, Teams, Purview and Defender, and the full list lives in the Tenant Configuration Management overview on Microsoft Graph. If you’ve used community tooling to do this kind of thing before, the concepts will feel very familiar. The difference is that it’s now a first-party Microsoft service, with the cross-tenant pieces still in preview.
The Bit That Matters for Partners: GDAP Underneath
Here’s where it gets interesting for those of us in the partner world. The cross-tenant delegated administration model in Tenant Governance uses GDAP technology. Roles are defined in a governance policy template, mapped to security groups in the governing tenant, and represented in the customer tenant as group proxies. Admins sign in with their home tenant credentials, so you don’t need B2B guest accounts or local admin accounts in every tenant.
A few details from the governance relationships docs that I think are well thought through:
- Setting up a relationship is a handshake: the governed tenant invites, the governing tenant sends a request with a policy template, and the governed tenant accepts. The customer stays in control.
- Relationships can have a lifetime of 1 to 730 days (preview), and renewal needs the governed tenant’s approval. If it isn’t renewed, access is removed.
- Multi-tier governance is in preview, and access isn’t inherited down the chain. If A governs B and B governs C, A gets nothing in C without its own approved relationship. Good.
- Workload permissions are a separate layer. A relationship alone doesn’t grant every workload permission, and Azure RBAC or Defender RBAC roles are assigned in the customer tenant afterwards.
What It Costs
The licensing page is clearer than most, which I appreciate.
- Tenant Governance Basic comes with Entra P1 or P2: up to 30 monitors and 800 configuration resources per tenant per day, and snapshots of up to 20,000 resources per tenant per month. That means Microsoft 365 E3 and Business Premium tenants get it without buying anything else.
- The licensing table labels those rows “single tenant”, which confused me at first. The configuration management docs clear it up: Basic covers both home-tenant and cross-tenant configuration management, and the limits above are capacity, not a feature gate.
- Tenant Governance Premium (Entra ID Governance) adds capacity per licence (10 more configuration resources a day for monitoring and 35 more a month for snapshots), plus related-tenant discovery.
- A governance relationship with cross-tenant GDAP needs P1 or above. You need one licence for each admin who configures relationships, in the governing tenant only. The governed tenants don’t need licences, and the number of relationships doesn’t change the count.
- Most resource policy operations during preview need an Entra ID Governance service plan. P1 or P2 alone won’t do it.
Microsoft also notes that Entra ID Governance is included in Entra Suite and Microsoft 365 E7.
Why I Think This Matters
In my view, configuration drift is one of the most under-rated security risks in Microsoft 365. In my experience, plenty of security problems don’t start with a zero-day. They start with a setting that was right once and quietly stopped being right. Tenant Governance gives you an auditable way to define “right” and to know, within hours rather than months, when it changes.
For MSPs, there’s also a commercial angle. “We set your baseline and we’ll tell you when it moves” is a far more valuable managed service than “we configured it once at onboarding”. And because the relationship model is approval-based and time-bound, it’s an easier conversation with a customer’s security team than standing admin access.
Getting Started
This is preview, so it belongs in a lab or your own tenant first. Here’s how I’d approach it:
- Start in your own tenant. Take a snapshot, review it, and turn the important bits into a baseline: Conditional Access, authentication methods, role settings. The licensing page uses exactly these as its example of where to spend the 800-resource budget.
- Create a monitor and break something on purpose. Change a CA exclusion and watch the drift appear. Then put it back and watch it clear.
- Set up one governance relationship with a test or friendly tenant, using a tightly scoped policy template and a sensible lifetime.
- Write your baseline as a template so it’s versioned and reusable, and keep the JSON in source control.
- Only then look at cross-tenant deployments. Detect first, enforce later.
Caveats
- Cross-tenant monitors, baseline templates, deployments, resource policy and the Agent 365/Copilot multi-tenant support are all preview. Expect changes, and don’t promise customers SLAs on preview features.
- It isn’t yet clear to me how this sits alongside existing Partner Center GDAP relationships and Microsoft 365 Lighthouse day to day. The docs say Tenant Governance uses GDAP technology, but I’d test whether your existing CSP relationships carry over before planning around it.
- Six-hourly monitoring is drift detection, not real-time prevention. Resource policy is the prevention piece, and it needs ID Governance licensing.
- Mind the snapshot retention. Seven days goes quickly.
I’ll be piloting this properly when I’m back home and will share what I find. If you’re already testing it, I’d love to hear how you’re getting on. Drop me a message.