CISO
Enterprise Architect
CIO
Industry relevance
Financial Services
Healthcare
APRIL 17, 2026
Entra Agent Registry retires May 1. Agent 365 is now the single source. Organizations using the current registry Graph API must re-register agents after the new API ships or face inventory gaps.
Microsoft confirmed that the Agent registry and Agent collections blades in the Microsoft Entra admin center will be retired on May 1, 2026. The complete agent inventory moves to Agent 365 in the Microsoft 365 admin center, which becomes the single source of truth for agent discovery and management. Microsoft Entra continues to provide the identity foundation through Agent ID including Conditional Access, identity governance, and security signals. The existing agent registry Graph API will be deprecated and replaced by a new API powered by Agent 365. Organizations that have registered agents via the current API will need to re-register them under the new API once the timeline is confirmed. This consolidation positions Agent 365 as the unified control plane for all agent governance across the enterprise.
GOVERNANCE IMPLICATION
The retirement of the Entra Agent Registry blade on May 1 is not an administrative change. It is an architectural shift that directly affects how regulated organizations demonstrate agent inventory completeness to auditors and examiners. Any agent visible only in the Entra registry that is not re-registered in Agent 365 may disappear from the consolidated inventory view, creating a gap between what the organization claims to govern and what the system can show. For organizations in financial services and healthcare that must demonstrate complete agent visibility under FINRA and OCC examination frameworks, this gap could appear in an audit as an unaccounted-for agent, exactly the kind of Governance Debt that is difficult to explain retroactively.
THE GOVERNANCE QUESTION
Does your organization know which agents are registered via the current Entra registry Graph API, and will those registrations survive the May 1 convergence, or will gaps appear in your inventory after the cutover?
CONTROL GAP
Organizations with agents registered via the current Graph API have no automated migration path. Manual re-registration is required once the new API ships, and Microsoft has not yet confirmed the deprecation date or the new API availability date.
REGULATORY RELEVANCE
FINRA
OCC
PRIMARY SOURCE
Agent Registry convergence with Microsoft Agent 365
Microsoft Learn
April 9, 2026
Read the primary source →(opens in new tab)CONTINUE READING
MAY 11, 2026
AgentsMicrosoft Copilot Studio published April 2026 feature updates on May 11, 2026, authored by Nitasha Chopra, VP and COO of Copilot Studio. Key releases include the Analytics Viewer role reaching GA providing read-only access to agent analytics separated from configuration rights; agent nodes embeddable directly into workflows to delegate AI reasoning within deterministic automation; MCP server-enabled tools in preview for external system connectivity within workflows; and a centralized admin-controlled DLP-enforced environment for the Workflows Agent. The post also confirms Microsoft Agent 365 is now generally available as the centralized control plane for agents.
MAY 5, 2026
AgentsMicrosoft's 2026 Work Trend Index Annual Report, published May 5, 2026, includes the first WTI telemetry on AI agent volume. Active agents on Microsoft 365 grew 15x year-over-year across all customer segments, rising to 18x in large enterprises. This is the first time Microsoft has disclosed agent volume scale as part of its annual workforce research.
MAY 1, 2026
AgentsMicrosoft's May 1, 2026 What's New in Agent 365 announcement introduced registry sync, allowing organizations to connect the Agent 365 registry to external agent platforms. Initial preview connections include Amazon Web Services and Google Cloud, with additional partner platforms planned. When connected, agents built on those platforms appear in the Agent 365 unified registry with governance actions including agent deletion available directly from the registry interface. Without registry sync connections configured, Agent 365 shows only Microsoft-hosted agents.