A woman reviews an analytics dashboard linking city buildings, factories, banks, hospitals, and shops.
Running a dozen Microsoft 365 tenants used to mean a dozen browser profiles, a pile of admin accounts and a lot of Ctrl+Tab. Microsoft now wants that work to happen in one place. On November 17, 2026, the company announced multi-tenant management capabilities in the Microsoft 365 admin center. Through All tenants, authorized administrators get one familiar place to manage Microsoft 365, Copilot, AI agents, and AI spend consistently across eligible, connected tenants.

The release has four parts, and they ship at different maturity levels. Tenant switching is generally available. Cross-tenant agent management, desired-state configuration and AI cost management are all in public preview. Microsoft also says availability and supported features can vary by eligibility, licensing, admin roles, geography and rollout status. Before you rebuild your MSP runbook around this, it's worth knowing exactly what "one place" covers and what it doesn't.

A woman reviews an analytics dashboard linking city buildings, factories, banks, hospitals, and shops. Why Microsoft built it​

Microsoft's case is simple: every extra tenant adds work. Enterprises split tenants across subsidiaries, regions and business units, and managed service providers hold one per customer. Each tenant has its own policies, configuration and, more and more often, its own AI agents and Copilot bills. Repeating deployments slows service delivery, inconsistent policies make compliance harder, and consumption-based AI billing adds a cost that has to be governed tenant by tenant.

AdminDroid's blog places the launch among Microsoft's Ignite 2026 announcements. It describes the release as adding cost and configuration management alongside the existing AI agent management, so the agent piece builds on an existing experience rather than starting from scratch.

Section summary: This is a consolidation play aimed at MSPs and multi-tenant enterprises. Only tenant switching is production-grade today.

Tenant boundaries still apply​

Centralized administration does not merge tenants into one big tenant, and Microsoft says so plainly:

  • Partners get access through Granular Delegated Admin Privileges (GDAP) relationships in Partner Center.
  • Enterprises set up governance relationships through Microsoft Entra Tenant Governance.
  • Delegated roles in each governed tenant decide which tenants an admin can reach and what they can do there.

Microsoft's documentation uses two terms. The governing tenant is where admins work from, and governed tenants are the ones they administer. Microsoft Learn also warns that Microsoft Entra Tenant Governance is not the same as Multitenant Collaboration (MTO) in Microsoft 365. Admins who have set up MTO for cross-tenant collaboration should not assume it enables any of this.

Tenant switching (generally available)​

With tenant switching, admins move between authorized tenants in the Microsoft 365 admin center without signing out and back in, and without keeping a separate admin account in each tenant. According to Microsoft Learn, the switcher moves you from the governing tenant into a governed tenant's administrative context without a separate browser session or a local admin account in that tenant.

Cross-tenant agent management (public preview)​

This is the most fully documented piece. Sign in to the admin center with a governing-tenant account and go to All tenants > Agents. Microsoft Learn says the All tenants scope only appears when the governing tenant has at least one supported tenant relationship and the signed-in admin holds a supported delegated role.

From there, admins can:

  • View a consolidated inventory with summary cards for Total agents, Risky agents and Assigned tenants.
  • Add a custom agent to the inventory. Microsoft states that adding an agent does not install it in other tenants automatically.
  • Install an agent in all eligible tenants or a chosen subset. The workflow covers configuration, required permissions, and which users or groups can use the agent in each tenant.
  • Block agents. Each block is applied separately per selected tenant. Tenants where you only have read access stay visible, but you can't change them.
  • Review per-tenant details on the Overview, Data & tools, Security & compliance, Permissions and Activity tabs. Activity data can be exported to CSV.

Microsoft repeatedly stresses one point: agent status is tenant-specific. A single agent can have different availability, permissions, risk data and activity in different tenants, so check which tenant is selected before you click anything.

Who can do what​

Delegated role in governed tenantView inventoryAdd, install, block, change availability
AI AdministratorYesYes
Global AdministratorYesYes
Global ReaderYesNo

Microsoft's own guidance is to use the least-privileged role that gets the job done and to limit Global Administrator use. For most agent work, AI Administrator is the role to grant.

Licensing​

Viewing and managing agents across connected tenants needs no additional license. Viewing agent risk and activity requires a Microsoft Agent 365 license assigned to the end user. Without it, the inventory works but the risk and activity views won't show that data.

Section summary: You get one inventory with per-tenant actions. Installs and blocks are explicit choices for each tenant, and risk telemetry is tied to Agent 365 licensing.

Desired-state configuration (public preview)​

Configuration drift happens slowly: one admin changes a setting here, a regional team changes another there, and the tenants no longer match. Microsoft's answer is a four-step lifecycle. You define a baseline, deploy it to tenants, monitor for drift, and review and fix the differences.

How it works, based on Microsoft Learn's preview documentation:

  1. Sign in with a governing-tenant account and select All tenants.
  2. Open Configuration management to create and manage baselines, or Tenants to assign baselines and check status.
  3. Create a baseline. Microsoft-provided baselines are available. For Entra Tenant Governance relationships, custom baselines can be built from a snapshot of an existing tenant, by uploading or editing JSON, or by selecting settings manually.
  4. Assign the baseline to one or more tenants. A tenant can have more than one assigned baseline.
  5. Monitor status. A tenant with no baseline shows Not monitored. A matching tenant shows Compliant, and a tenant with differences shows Drifted. The preview can also show Unknown, but Microsoft hasn't documented what causes it yet.
  6. Use Fix drifts to compare expected and actual values, choose the settings to fix, and submit.

The preview also adds configuration snapshots and tenant comparison. Current examples of supported resources include Copilot, Entra, Exchange, Intune, Security & Compliance and Teams. Comparison works on exactly two tenants at a time, so you can't line up a whole tenant estate side by side yet.

Partner Center relationships get an extra step in the assignment flow. You can enter tenant-specific values, such as users, groups and recipients, during assignment or skip that and do it later.

What can go wrong​

  • Assigning a baseline changes settings. It isn't a dry run. Microsoft says assignment deploys the desired configuration, and tells admins to check baseline contents, target tenants and permissions before submitting.
  • Delegated access isn't enough on its own. You also need the fine-grained permissions for every workload and setting in the baseline. If a baseline touches Exchange and Intune, you need rights in both.
  • Monitoring data can lag. Results reflect the most recent completed monitoring run, so a change you just made may not show up immediately.
  • A snapshot marked as processing isn't finished. The confirmation after submission only means the job is queued.

Section summary: Drift detection across tenants is useful. Treat baseline assignment as a change deployment, not a report.

AI cost management (public preview)​

Consumption billing for Copilot and agents brings a new way to overspend. Microsoft acknowledges that setting up spending policies, enabling the right users, and monitoring usage is manageable in one tenant, but repeating that work across dozens or hundreds of tenants quickly becomes impractical.

Microsoft Learn's cost management page explains that admins can review consumption across governed tenants, identify tenants that need policies or controls, analyze the users and services driving usage, and apply reusable spending configurations at scale. The unit is Copilot Credits, defined as the usage unit shown in Microsoft 365 Cost Management for eligible AI experiences enabled by usage-based billing.

The detail most likely to catch people out is how templates work. Microsoft states that a template isn't itself a tenant policy. Applying a template creates an independent spending policy in each selected governed tenant by copying the template's current settings. In practice, the template is a starting point, not a live link. Editing the template later doesn't update the policies already created from it, so adjusting a policy across 40 customers means changing each tenant's policy.

On roles, the same page lists AI Administrator or Billing Administrator as able to edit spending policies and manage limits and alerts. A Global Administrator can create a new Azure subscription directly from the Microsoft 365 admin center when the supported billing path is available.

The stakes are real. HubSite 365, summarizing Microsoft's Copilot billing guidance, reports that the limit is a hard limit, so the affected service is interrupted when it is reached. A template copied across a portfolio with a limit set too low could stop Copilot service for several customers at once. Test with one tenant before rolling it out widely.

For single-tenant admins, these policies already live under Copilot > Cost Management in the admin center. The multi-tenant view extends that experience across tenants rather than replacing it.

Section summary: You get consolidated visibility and copy-once templates, not centrally synchronized budgets.

Analysis: a big step, with caveats​

On the plus side, this matters most for MSPs. Many of them have relied on Microsoft 365 Lighthouse, third-party tools or custom PowerShell to get a cross-tenant view. Moving agent inventory, drift detection and AI spend into the native admin center reduces the need for extra tools. The decision to keep tenant boundaries through GDAP, Entra Tenant Governance and per-tenant roles, instead of a single super-admin, is also the right security call.

The caveats:

  • Three of the four features are previews. Microsoft notes that labels and workflows may change before general availability.
  • Some gaps are still visible. Comparison is limited to two tenants, the Unknown drift status is undocumented, and template-created policies don't sync back.
  • Admin rights become more powerful. One compromised governing-tenant account with broad GDAP roles can now install agents and push configuration across a whole customer base. Short-lived role assignments, phishing-resistant MFA and least-privilege roles matter more than ever.

Does "one place" mean one view? Mostly yes. Does it mean one control? Not quite. You still act tenant by tenant, just from a single screen.

Before you start: checklist​

  1. Partners: Check active GDAP relationships and delegated roles in Partner Center.
  2. Enterprises: Check governance relationships and permissions in Microsoft Entra Tenant Governance, not MTO.
  3. Give admins AI Administrator for agent work and Billing Administrator for spending policies, and avoid Global Administrator where you can.
  4. If you need agent risk and activity data, confirm Agent 365 licensing for end users.
  5. Pilot baselines and spending templates on one or two non-critical tenants first.
  6. Find everything under All tenants in the Microsoft 365 admin center. If it isn't there, check your relationship status and roles before assuming the rollout hasn't reached you.

For WindowsForum readers already following GDAP migrations, Copilot usage-based billing and Agent 365 governance, this release is where those threads come together. Tenant switching is ready to use now. Treat the other three features as previews to test carefully.

 

References

  1. Multi-tenant management: Tenants, agents, and AI spend in one place Microsoft 365 Blog 2026-11-17T18:30:00+00:00
  2. Multi-tenant management: Tenants, agents, and AI spend in one place techcommunity.microsoft.com
  3. Manage agents across multiple tenants in the Microsoft 365 admin center | Microsoft Learn learn.microsoft.com