Copilot Studio Rolling out #122

Microsoft Copilot Studio: MCP-compliant tools in agent workflows

Agent workflows gain support for MCP-compliant tools

Microsoft Copilot Studio is adding MCP support to connect agent workflows with proprietary systems, dynamic knowledge sources, and custom actions. The stated targets are preview in May 2026 and general availability in June 2026; completion is not confirmed.

Key points

  • MCP support enables reuse of integrations across agents and workflows.
  • The integration is designed to preserve workflow reliability.
  • The listed platform is Web.
  • The listed cloud is Worldwide (Standard Multi-Tenant).

What to do

Identify proprietary systems, knowledge sources, and custom actions that could be reused across agent workflows. Check availability before planning adoption. Tell makers that MCP support is intended to reduce duplicate integrations. Confirm licensing and admin requirements before deployment; these are not specified.

Timeline

  1. May 2026 Preview (planned, not confirmed) Microsoft 365 Roadmap target: Preview target
  2. 15 May 2026 Published
  3. June 2026 General availability (planned, not confirmed) Microsoft 365 Roadmap target: General availability target
Speaker notes

This change brings MCP-compliant tools into agent workflows in Microsoft Copilot Studio. Explain it as a way to reuse connections to proprietary systems, dynamic knowledge sources, and custom actions across agents and workflows. Microsoft describes reduced duplication of integrations while preserving workflow reliability. The stated preview and general availability dates are targets, not confirmed completion dates. Web and Worldwide (Standard Multi-Tenant) are the listed deployment scope. Licensing requirements and admin controls are not specified.

Sources and links

Area, status, change type, licence and flags are indicative. Always open the source before you act on a card.