The Agents Button in Copilot Is Going Away: Admin & Governance Guide

#RegoConsulting #SimpleSharepoint #Copilot #Microsoft365 #AgentGovernance #ChangeManagement #AIReadiness #MCP #DigitalTransformation

Unified Plugin Registry, Interface Changes, and Change Management Controls

Microsoft is consolidating how users find and manage extensions across workplace tools.

The Agents button in Copilot is officially retiring as Microsoft introduces a central plugin registry. Specifically, this shared catalog lets IT leaders publish, find, and govern tools across Microsoft 365 apps. Rollout of the central plugin registry began in late September 2026 and finishes by late October 2026. Shortly after, by the end of November 2026, the legacy Agents, Agents and Skills, and Customize buttons will give way to a single Plugins button across user screens.

Architecture of the Central Plugin Registry

First, understanding how plugins package tools clarifies why Microsoft is unifying these screens:

• Unified capability bundles: A single plugin now combines skills, Copilot connectors, Model Context Protocol (MCP) servers, and declarative agents together.
• Shared experience across apps: Therefore, users find and enable extensions consistently inside Copilot screens and Microsoft 365 desktop apps.
• Zero admin action for rollout: In addition, Microsoft confirms that tenant admins do not need to take technical steps to start the interface change.

Governance and Access Control Rules

Second, managing user access to published plugins requires proactive administration:

• Scope assignments: Admins can scope individual plugins to all users, limit access to specific Entra ID security groups, or block them tenant-wide.
• Centralized approval workflows: As a result, security teams can review extensions in the Microsoft 365 admin center before users find them in the catalog.
• Risk mitigation: Consequently, controlling plugin visibility keeps unvetted MCP servers or external connectors away from company data pipelines.

Action Plan for Change Management Teams

Because this UI update breaks old screenshots and training guides, teams should complete three steps:

• Update internal documentation: Revise user guides and intranet help articles that show the old button names.
• Establish approval workflows: Define clear team roles for reviewing, approving, and blocking new plugins submitted to the registry.
• Implement recurring catalog audits: Additionally, check active plugins regularly inside the admin portal to make sure approved tools stay in use.

How our team supports your AI governance strategy:

• Plugin Approval Architecture: We help you build governance models that map plugin review rights directly to Microsoft Entra security groups.
• Training and Asset Refresh: We update your internal documentation and screenshots so employees navigate the new Plugins button smoothly.
• Catalog Management Reviews: We set up regular review routines to audit registered tools and remove unapproved extensions.

Updating your change management assets ensures a smooth move as Microsoft unifies its AI extensions. Reach out to our team today to align your tenant governance.