Take a look and decide whether this affects your tenant, users or support teams.
Primary Audience
Why this score?
AT A GLANCE
END USERS
IT ADMINS
ROLLOUT TIMELINE
Mid–late Sept 2026
📢 Official Microsoft Message Center Announcement
Microsoft 365 admin center: Agent Registry consolidates duplicate agent entries and adds version history
Message ID: MC1477184
[What and why]
We’re improving the Agent Registry experience in the Microsoft 365 admin center by consolidating duplicate entries for the same agent into a single record. Previously, the same agent could appear multiple times when published across different scopes or when multiple published versions existed.
This update simplifies agent governance, provides a clearer inventory of deployed agents, and makes it easier for admins to manage agent lifecycle and version history from a single location. All versions of an agent will be accessible from the agent details flyout while governance actions continue to apply across the entire agent.
[Rollout schedule]
- Worldwide: Beginning in mid-September 2026 and expected to complete in late September 2026
[Impact on your organization]
Who is affected
- Global Administrators
- Global Readers
- AI Administrators
- Organizations using the Agent Registry
Platforms and services
- Microsoft 365 admin center
- Agent Registry
What will happen
- Each agent will appear only once in the Agent Registry.
- Agents that previously appeared as multiple entries due to different publishing scopes or published versions will be consolidated into a single entry.
- The Registry list will display the most recently published organizational version by default.
- Selecting an agent will open an agent details flyout that includes a version selector.
- The version selector will display available published versions and any in-progress draft versions where applicable. Selecting a version will update the agent details shown in the flyout.
- Governance actions, such as Block, will continue to apply to the entire agent across all versions.
- Total agent counts in the Agent Registry may decrease because duplicate entries are being consolidated. No agents are being removed.
- Reports, dashboards, exports, and custom processes that relied on previous per-entry counts may show different totals after rollout.
- Registry exports will include options for exporting agents and their associated versions.
- This change is enabled by default and requires no configuration.
[Action required and recommendations]
No action is required.
We recommend that administrators:
- Inform governance and operations teams that Agent Registry counts may decrease as duplicate entries are consolidated.
- Review internal reports, dashboards, scripts, and processes that depend on Agent Registry counts or export data.
- Update internal documentation and training materials to reflect the new version selector experience in the agent details flyout.
- Validate any downstream reporting that uses Agent Registry export data after rollout is complete.
[Compliance considerations]
| Question | Answer |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Agent Registry counts will change because duplicate entries are consolidated. Reports, dashboards, exports, and other administrative reporting based on prior count logic may show different totals after rollout. |
Source: Microsoft Message Center • Analysed by MWPro
