Microsoft has introduced a public preview for managing agents across multiple customer or subsidiary tenants from a single experience in the Microsoft 365 admin center. For partners responsible for several customer environments, the change is less about a new agent feature and more about operational control at scale. Instead of moving tenant by tenant for common agent administration tasks, administrators can now use a consolidated experience to review inventory, take supported actions, and switch into governed tenants more efficiently.
The announcement is especially relevant for CSP distributors, CSP indirect resellers, CSP direct bill partners, and systems integrators that manage customer tenants. It also matters for larger organizations with subsidiary tenants and centralized IT governance. Microsoft is positioning the feature as a way to reduce repetitive administration while keeping actions scoped to the administrator’s delegated role in each tenant.
What changed
The new capability, now in public preview, brings multi-tenant agent management into the Microsoft 365 admin center. Administrators can view and manage agents across tenants they govern from one location. Microsoft describes several supported tasks: viewing a consolidated agent inventory, adding agents, installing or blocking agents across eligible tenants, reviewing tenant-specific risk, and using activity insights where licensing requirements are met.
A practical feature is the tenant switcher. Instead of signing out or maintaining separate administrator sessions for each customer or subsidiary tenant, administrators can move directly into a governed tenant from the management experience. For CSP partners, access still depends on Granular Delegated Admin Privileges, commonly known as GDAP. That means a partner’s ability to act in a customer tenant remains limited by the roles the customer has delegated.
Microsoft also notes that an Agent 365 license is required to view an end user’s agent activity and risky-agent insights. Partners should treat that as a planning point for customers that want deeper monitoring and risk visibility, not just basic inventory or deployment control.
Why this matters
Agent adoption is likely to grow unevenly across organizations. Some departments will move quickly, others will wait, and customers will need governance that keeps pace with experimentation. Without centralized oversight, administrators can face a fragmented picture: which agents exist, where they are installed, which tenants are exposed to risk, and which users are active.
For partners managing multiple customers, the traditional approach can become repetitive very quickly. Even simple tasks such as checking inventory, validating whether an agent is allowed, or moving into a tenant for follow-up can consume significant time when multiplied across dozens or hundreds of environments. A single management plane can help reduce that overhead.
The governance angle is just as important. As agents become more embedded in business workflows, customers will ask partners for help with policy, risk review, adoption reporting, and lifecycle management. Multi-tenant visibility gives partners a better foundation for managed services around agent readiness and governance. It can also help partners standardize operating procedures across customer tenants while respecting each customer’s delegated permissions and policies.
Default behavior and impact
This announcement does not mean partners automatically gain broader authority in customer tenants. Microsoft specifically frames actions as scoped to the administrator’s delegated role in each customer tenant. In practice, that means GDAP configuration remains essential. If a partner does not have the right delegated roles, the new interface will not magically grant them the ability to install, block, or review agents beyond those permissions.
The feature is also in public preview, so partners should avoid presenting it as a fully mature production dependency without validation. Preview features can evolve, and user interface details, eligible workloads, reporting depth, and licensing behavior may change before general availability. Partners should test the experience in a controlled way before building customer commitments around it.
For customers that want activity and risky-agent insights, licensing must be reviewed. Microsoft states that an Agent 365 license must be assigned to an end user in order to view that user’s agent activity and risky-agent insights. That can affect the business case for customers expecting comprehensive monitoring across all users.
Partner next steps
Partners should start by identifying which customers are most likely to benefit from multi-tenant agent management. Good candidates include customers actively deploying agents, customers with multiple business units or subsidiaries, and customers asking for stronger governance around AI-enabled work. CSP partners should also review their GDAP relationships to confirm that delegated roles align with the management tasks they intend to perform.
Next, test the preview in a low-risk environment. Review the consolidated inventory, validate install and block workflows where available, and confirm how the tenant switcher behaves across customers. Document what your administrators can and cannot see under different delegated roles so your service desk and managed services teams understand the permission model.
Partners should also update governance conversations with customers. Agent management should be part of broader AI operations planning, including who can approve agents, how risky agents are reviewed, how exceptions are handled, and how customer-specific policies are documented. If customers want visibility into activity and risk insights, include Agent 365 licensing in the discussion early.
Finally, consider whether this preview creates a new managed service opportunity. A standardized monthly review of agent inventory, blocked agents, risky activity, and deployment recommendations could be valuable for customers that lack internal capacity to govern agent sprawl.
Bottom line
Microsoft’s public preview for multi-tenant agent management is a meaningful operational improvement for partners and administrators responsible for more than one tenant. It reduces the friction of managing agents one environment at a time and gives partners a clearer path to scalable governance services.
The most important caveats are permissions, licensing, and preview status. Review GDAP roles, validate Agent 365 requirements for deeper insights, and test the workflows before turning the capability into a customer-facing promise.