MC1447677 High
Microsoft 365 Copilot: Unified management experience for connectors in the Microsoft 365 admin center
Summary AI-generated
Microsoft is unifying Copilot connector and plugin management into a single experience in the Microsoft 365 admin center to simplify administration and discovery.
Suggested actions AI-generated
- Review internal documentation and training materials referencing connector management
- Inform connector administrators about the new experience
- Validate operational procedures for connector management workflows post-rollout
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1188234 (Updated) Microsoft 365 Copilot: Manage and deploy user-level connectors in Microsoft 365 admin center
- MC1259822 (Updated) Microsoft 365 Copilot: Introducing Federated Copilot Connectors
- MC1484008 Microsoft Copilot: Introducing the Microsoft plugin registry for Microsoft Copilot experiences
- MC1454973 Manage Copilot connectors (Global setting) from Agent 365 - SetFederatedConnectors CLI toggle is retiring
- MC1187780 New experiences for Copilot management in Microsoft 365 admin center
- MC1404326 (Updated) Microsoft 365 admin center: New usage report for Copilot connectors
Original post from Microsoft
[What and why]
Microsoft is unifying Microsoft 365 Copilot connector management into a single experience in the Microsoft 365 admin center. After this rollout, administrators will manage Microsoft 365 Copilot connectors and Copilot plugins from one location: Microsoft 365 admin center > Copilot > Connectors.
We're making this change to simplify administration, provide a consistent connector management experience, and make it easier for users to discover and use available connectors across supported Microsoft 365 Copilot experiences.
Connector governance, security, compliance capabilities, and existing administrative controls are not changing as part of this update.
[Rollout schedule]
- General Availability (Worldwide): Beginning in early August 2026 and expected to complete by mid-August 2026
[Impact on your organization]
Who is affected
- Organizations using Microsoft 365 Copilot connectors
- Organizations using supported Copilot plugins
- Administrators who manage Microsoft 365 Copilot connector deployments
- Independent software vendors (ISVs) and developers publishing Microsoft 365 Copilot connectors or supported plugins
Platforms and services
- Microsoft 365 admin center
- Microsoft 365 Copilot
What will happen
- Administrators will manage connector types from a single location in Microsoft 365 admin center > Copilot > Connectors.
- Users will discover available connectors through a unified connector catalog across supported Microsoft 365 Copilot experiences.
- Available connectors will appear in the Sources menu in supported Microsoft 365 Copilot experiences.
- ISVs and developers will publish connectors using a unified connector manifest and publishing pipeline.
- Existing governance, security, compliance, and administrative controls will remain unchanged.
- Existing administrative policies will continue to apply.
[Action required and recommendations]
No action is required before rollout. No new administrator configuration or policy changes are required.
We recommend that administrators:
- Review internal documentation and training materials that reference current connector management locations.
- Inform connector administrators about the new Microsoft 365 admin center > Copilot > Connectors experience.
- Validate any operational procedures that reference connector management workflows after rollout is complete.
[Compliance considerations]
No compliance considerations identified. Review as appropriate for your organization.
Additional details from Microsoft
- Summary
- Microsoft 365 Copilot connector management will be unified in the Microsoft 365 admin center (Copilot > Connectors) starting early August 2026. This simplifies administration and discovery without changing governance, security, or compliance controls. No action is required before rollout; administrators should update documentation and inform teams.