501585 – Microsoft Copilot (Microsoft 365): Admins can create and deploy custom Model Context Protocol (MCP) connectors across Microsoft 365.

Product:

Copilot, Microsoft 365 Copilot

Platform:

Web, World tenant

Status:

In development

Change type:

Links:

Details:

Admins can create custom Model Context Protocol (MCP) connectors in the Microsoft 365 Admin Centre and deploy them across Microsoft 365. This will allow admins to surface their organization's custom data in Microsoft 365 Copilot via these MCP-based connectors.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:
Preview

Created:
2025-09-20

updated:
2025-09-20

Docu to Check

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Deployment of Custom MCP Connectors
Without proper preparation, the deployment of custom MCP connectors may lead to data inconsistencies and integration issues, causing disruptions in user workflows and access to critical information.
   - roles: IT Admin, End User
   - references: https://techcommunity.microsoft.com/t5/microsoft-365-copilot-blog/introducing-microsoft-365-copilot/ba-p/3701230, https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/16/introducing-microsoft-365-copilot/ " target="_blank" rel="nofollow noopener noreferrer">https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/16/introducing-microsoft-365-copilot/

User Experience with Microsoft 365 Copilot
If the custom MCP connectors are not thoroughly tested before deployment, users may experience errors or delays in retrieving data, leading to frustration and decreased productivity.
   - roles: End User, Support Staff
   - references: https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/16/introducing-microsoft-365-copilot/, https://techcommunity.microsoft.com/t5/microsoft-365-copilot-blog/what-is-microsoft-365-copilot/ba-p/3701230

Configutation Options**

XXXXXXX ... paid membership only

explanation for non-techies**

Imagine you have a toolbox, and each tool is designed for a specific task. Now, think of Microsoft 365 as a giant toolbox that helps you with various tasks in your office, like writing documents, sending emails, or scheduling meetings. Microsoft Copilot is like a smart assistant that helps you use these tools more effectively by understanding your needs and providing helpful suggestions.

Now, let's say you have some unique tools that aren't in the standard toolbox, but they are crucial for your specific work. In the world of Microsoft 365, these unique tools are like your organization's custom data. To make sure Microsoft Copilot can use these unique tools, admins can create special connectors, known as Model Context Protocol (MCP) connectors.

These MCP connectors act like bridges, allowing Microsoft Copilot to access and use your organization's custom data just like it uses the standard tools in the toolbox. By creating and deploying these connectors, admins ensure that Copilot can provide more tailored and relevant assistance based on the specific needs and data of your organization.

In simple terms, think of it as giving your smart assistant access to all the special tools you have, so it can help you even better. This way, Microsoft Copilot becomes more than just a generic assistant; it becomes a personalized helper that understands and utilizes the unique aspects of your organization's data.