Microsoft is simplifying how AI agents are managed across its platforms by consolidating agent management into a single place and converging the various management experiences under a single control plane called Agent 365.
This change should give AI administrators a unified catalog of all agents running in the organization, whether they originate from Microsoft, third-party providers, or custom-built solutions, along with consistent visibility and simplified oversight from a single location.
Timeline
1 May 2026
How does this affect your organization?
On 1 May 2026, the Agent registry and Agent collections sections in Microsoft Entra will be retired.
The complete agent inventory will be available in the Microsoft 365 admin center under Agent 365.
Microsoft Entra continues to play an important role as the identity foundation for agents through Agent ID, and all identity governance, Conditional Access policies, and security controls for agents remain unchanged and fully available there. Applying security and governance controls for agents requires the appropriate licensing for Microsoft Entra Agent ID, which Microsoft introduced last December.
Microsoft also explains the required admin roles to manage the different locations.
To see all agents in Agent 365, users need the AI Administrator role.
To see all agents with a Microsoft Entra Agent ID in the Microsoft Entra admin center, users need the Agent ID Administrator role. Identity administrators can be assigned these roles for complete agent visibility.
The agents themselves continue to work as before, and no functionality is being removed. The change is purely about where administrators go to view and manage the agent inventory.
Retirement of the agent registry Graph API
One additional technical change to be aware of is that the existing agent registry Graph API (affecting the endpoint /beta/agentRegistry/…) will be deprecated soon and replaced by a new Agent 365 API (affecting the endpoint /beta/copilot/admin/…, currently in early access). Any agents registered through the current API will need to be re-registered once the new API becomes generally available.
