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
JUNE 2, 2026
AgentsMicrosoft announced Scout at Build 2026 on June 2, 2026, as the first product in a new agent category called Autopilots. Scout is an always-on agent operating across Microsoft 365 apps including Teams, Outlook, OneDrive, and SharePoint, with its own governed Microsoft Entra identity. It is available in private preview for Frontier enterprise customers requiring a GitHub Copilot subscription, built on the OpenClaw open-source agent framework. The announcement was published on the Microsoft 365 Blog by Omar Shahine, Corporate Vice President, Microsoft 365.
JUNE 2, 2026
AgentsOn June 2, 2026, Microsoft announced the Agent Control Specification (ACS) and ASSERT at Build 2026, authored by Sarah Bird on the Microsoft Foundry Blog. ACS is an open industry specification, part of the Agent Governance Toolkit, that places deterministic safety and security controls at five validation checkpoints in an agent's lifecycle: input, LLM, state, tool execution, and output. Controls are expressed as portable, versionable, auditable policy and are designed to work across any agent framework. ASSERT, a separate open-source project, converts written policies into executable evaluation scenarios. ACS launched with customer and partner endorsement including KPMG, Zscaler, IBM, and Arize AI.
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.