Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 02:30 UTC Customize Public modeDiscuss ChangeIntel on Discord

Simplifying agent management with Agent 365

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

What the notice says

Microsoft’s text, with source markup removed
Updated April 9, 2026: We have updated the content. Thank you for your patience.  Introduction We’re consolidating agent management experiences to make it easier to observe, govern, and secure all agents in your tenant. Agent 365 will be the single source of truth, offering a unified catalog, consistent visibility, and simplified management. As part of this consolidation, we’re retiring legacy agent management experiences in the Microsoft Entra admin center. We recognize this change is being communicated with a shorter notice period, and we’re sharing it as early as possible to help you plan. When this will happen Effective May 1, 2026, the following experiences will be retired in the Microsoft Entra admin center: Agent registry blade Agent collections blade How this affects your organization Who is affected Microsoft 365 tenants with administrators who currently view or manage agents using:The Agent registry or Agent collections blades in the Microsoft Entra admin center Developers or admins using the existing agent registry Graph API What will happen The Agent registry and Agent collections blades in the Entra admin center will no longer be available after May 1, 2026. Administrators can continue to view agent inventory in the All agents view in the Microsoft 365 admin center (MAC). Agent 365 becomes the single source of truth for agent discovery, visibility, and management. Microsoft Entra continues to provide the identity foundation for agents through Agent ID. The existing agent registry Graph API will be retired and replaced by a new API powered by Agent 365.Agents registered using the current API will need to be re‑registered using the new API. Details on the API retirement timeline and availability of the new API will be shared in a follow‑up communication. There is no change to agent functionality, access, or governance capabilities as part of this retirement. What you can do to prepare No immediate admin action is required for the retirement of the Entra admin center blades. If your organization uses the existing agent registry Graph API:Review upcoming communications for the new Agent 365–powered registry API. Plan to re‑register agents once the new API becomes available. Update internal documentation or admin guidance to reference Agent 365 and the Microsoft 365 admin center for agent inventory. Share this change with helpdesk or platform administrators as appropriate. Learn more:  Agent Registry convergence with Microsoft Agent 365 | Agent ID | Microsoft Entra | Microsoft Learn agentRegistry resource type | Microsoft Graph | Microsoft Learn Microsoft Entra releases and announcements | Fundamentals | Microsoft Entra | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization.

What changed

Between archive captures, newest first
    • Tags User impact, Admin impact, Retirement → Updated message, User impact, Admin impact, Retirement

    Updated April 9, 2026: We have updated the content. Thank you for your patience.  Introduction We’re consolidating agent management experiences to make it easier to observe, … May 1, 2026, the following experiences will be retired in the Microsoft Entra admin center: Agent registry blade Agent collections blade How this affects your …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 02:30 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current