Microsoft is bringing more cross-customer administration into the Microsoft 365 admin center. Its November 18, 2026 announcement combines generally available tenant switching with public-preview capabilities for AI cost management, agent management, and desired-state configuration.

For CSP partners, managed service providers, and systems integrators, the opportunity is a more consistent operating model across customer tenants. The immediate caution is that a single “All tenants” experience does not mean every capability has the same release status, licensing requirements, or availability.

Separate generally available functionality from preview features

Tenant switching across eligible, connected customer tenants is generally available. AI cost management, agent management, and desired-state configuration are in public preview.

That distinction should appear in internal rollout plans and customer-facing service descriptions. A partner can evaluate the centralized experience without representing preview features as universally available production capabilities.

Microsoft says access depends on prerequisites, licensing, administrative roles, and regional availability. Availability may also vary by tenant, cloud, and rollout. The announcement does not provide a universal license matrix or guarantee that every partner will see every feature immediately.

The authoritative next step is to check the current multitenant management documentation against the actual partner and customer environment.

What the All tenants experience brings together

The centralized experience is intended to support movement between authorized customer tenants, visibility into AI consumption, management of supported agent information, and reusable configuration baselines.

These capabilities address related but distinct operating problems. Tenant switching reduces administrative friction. AI cost management supports oversight of consumption and spending policies. Agent management provides a place to work with supported agent information. Desired-state configuration helps compare customer environments with defined baselines.

The scope remains supported management tasks across eligible tenants. This is not an announcement that every Microsoft 365 administrative operation can now be performed in bulk across every customer.

Partners should map the available functions to their own service processes rather than assuming the interface replaces all existing tools and workflows.

GDAP remains the access boundary

Cross-tenant administration is governed by granular delegated admin privileges, or GDAP, relationships established in Partner Center. Active relationships and delegated roles determine which customers an administrator can reach and which actions that administrator can perform.

Centralization does not create blanket permission across a partner’s customer base. Microsoft explicitly describes the experience as preserving customer tenant boundaries and autonomy.

Before rollout, review active relationships and role assignments. Confirm that the people using the experience have the permissions required for the intended tasks, but avoid broadening access simply to make a pilot easier.

It is also useful to document who owns each customer relationship and how access changes are approved. Where a tenant or action is missing, investigate eligibility, roles, licensing, and rollout status before assuming that a new permission grant is the answer.

AI cost management: define the operating process first

Microsoft describes spending-policy templates that can establish customer spending profiles and be applied across supported customers. Estate-level visibility lets partners monitor consumption across customers and then investigate individual tenants.

That could support a managed service for AI adoption and spending oversight. However, the announcement does not specify every enforcement behavior, covered AI workload, or charging interaction.

In particular, do not promise that a spending policy is a hard billing cap unless the documentation for that specific capability confirms it. Visibility, policy configuration, and enforceable limits are different things.

A practical pilot should establish which consumption is visible, how it maps to the customer’s financial review, and who responds when usage departs from expectations. Agree on the escalation process before offering a recurring cost-management service. Customers need to know whether the partner is observing usage, recommending changes, or authorized to make changes on their behalf.

Agent management: validate coverage before promising completeness

The announcement describes viewing and managing supported agent information across eligible tenants. It does not establish a complete inventory of every agent that might exist anywhere in a customer’s environment.

Partners should test which agent types and management actions are supported for their customers. Match that coverage to the proposed service scope and identify any separate administrative processes that remain necessary.

This matters particularly when an offering is described as governance. A centralized view is useful, but governance also requires clear ownership, approval rules, and an agreed response when an agent no longer meets policy. Those are service-design responsibilities, not outcomes guaranteed merely by enabling an interface.

Desired-state configuration: standardize carefully

Desired-state configuration allows partners to define supported baselines, apply them to eligible tenants, and identify drift from the defined state.

A shared baseline can improve consistency, but not every difference is a defect. Customer-specific requirements and approved exceptions need to be represented in the operating model.

Begin with a limited, documented baseline and a small pilot group. Review detected differences before broader application, and establish a change approval process for settings that affect users or security behavior.

Do not equate drift detection with automatic remediation. The announcement describes identifying differences and applying supported baselines; it does not establish the exact remediation behavior for every setting. Confirm those details before promising continuous enforcement.

Partner next steps

Review GDAP relationships and delegated roles in Partner Center, check the documentation for eligibility and licensing, and open All tenants in the Microsoft 365 admin center.

For the pilot, record which features are available in each selected tenant, which tasks succeed under the intended roles, and what limitations affect the service. Keep a clear distinction between verified behavior and assumptions still awaiting documentation or testing.

Bottom line

Microsoft is creating a more centralized way to administer customer AI costs, agents, and configurations. Partners should take advantage of the opportunity to test a consistent workflow, while keeping preview status, GDAP scope, licensing, and customer-specific controls visible in every rollout decision.

Microsoft Partner Center announcement