Summary
- Agent Registry in the Microsoft 365 admin center will consolidate duplicate entries for the same agent into a single record.
- Admins will see one agent entry with a version selector in the agent details flyout, showing published and draft versions where available.
- Governance actions such as blocking will apply to the full agent across all versions, and registry counts/exports may change because duplicates are being collapsed rather than removed.
- Organizations using Agent Registry should review any reports, dashboards, scripts, or documentation that depend on previous per-entry counts or export structure.
Microsoft is updating the Agent Registry in the admin center to consolidate duplicate entries into single records with version history between mid September and late September 2026. This change improves inventory clarity but may alter total counts in reports and exports. Administrators should inform stakeholders and review internal reporting scripts that depend on prior count logic.
Administrator impact: No direct administrator action is required.
End user impact: No direct end user impact is expected.
Score rationale: This is an informational service update that simplifies management and changes reporting totals without requiring tenant configuration.
The Microsoft 365 admin center’s Agent Registry will consolidate duplicate agent entries into single records with version history, simplifying management. This change, rolling out worldwide in September 2026, affects admins and may alter agent counts and related reports. No action is required, but review of dependent processes is recommended.
Primary Service: Admin
Admin Impact: Low
User Impact: Low
Release Start: 15 Sept 2026
Release End: 30 Sept 2026
Published: 23 Sept 2026
Expires: 30 Oct 2026
Last updated: 23 Sept 2026
Services: Admin, M365
Category: Prevent or fix issues
Tags: Admin Action, User Adoption
History
9/22/2026 Item Added to Message Center
Microsoft Message
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: Does the change alter how admins can monitor, report on, or demonstrate compliance activities?
Answer: 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.