Microsoft 365 Message Center Archive

MC1169071 - Microsoft 365 Copilot: MCP-based agents now available in Copilot and Microsoft 365 admin center

Message ID

MC1169071

View in Message Center

Service

Microsoft 365 Copilot Chat

Published

Oct 9, 2025

Tag

New feature
User impact
Admin impact

Summary

Microsoft 365 Copilot now supports MCP-based agents, allowing developers to build and admins to manage these agents via the Copilot Agent Store and admin center. The rollout starts late October 2025, is on by default, and requires no immediate action but recommends reviewing agent catalogs and updating documentation.

More information

We’re introducing support for Model Context Protocol (MCP)-based agents in Microsoft 365 Copilot and the Microsoft 365 admin center. This update enables developers to build Copilot agents using MCP servers and allows users and admins to interact with these agents using familiar experiences. This change supports extensibility and improves agent management capabilities for organizations.

When this will happen:

Rollout will begin in late October 2025 and is expected to complete by mid-November 2025.

How this affects your organization:

Who is affected:

  • Admins managing Microsoft 365 Copilot
  • Users accessing Copilot agents

What will happen:

  • MCP-based agents will appear in the Copilot Agent Store
  • Users can install MCP-based agents directly from the store
  • Admins can deploy MCP-based agents to users via the store or custom packages
  • Admins will see MCP agent details, including server information, in the Microsoft 365 admin center under Copilot > Agents
  • Existing extensibility controls and lifecycle management policies for Copilot agents will apply to MCP-based agents
  • The feature will be ON by default for all tenants

Screenshot 1 - Admin view:

 user settings

Screenshot 2 - User view:

 user settings

What you can do to prepare:

  • No action is required at this time
  • Review the MCP-based agent catalog to ensure agents align with your organization’s policies
  • Update internal documentation if you track agent types or deployment methods
  • Communicate this change to helpdesk or support teams as needed
Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.