Summary
- Microsoft Copilot Studio now supports MCP-compliant tools in agent workflows, enabling agents to call standardized external tools and services.
- The change is mainly relevant to Copilot Studio makers and admins building agentic workflows that integrate proprietary systems, dynamic knowledge sources, or custom actions.
- Existing workflow governance, monitoring, and lifecycle management still apply to MCP tools.
- No admin action is required for this awareness-only announcement.
Microsoft 365 Message Center ID: MC1471573
Primary Service: Power Platform
Admin Impact: Low
User Impact: Low
Release Start: 15 Jul 2026
Release End: 15 Jul 2026
Last Modified: September 14, 2026
Category: Message Center
Tags: New feature
Status: Launched
Products & Platforms: Microsoft Copilot (Power Platform)
History
9/14/2026 Item Added to Message Center
Microsoft Message
We are announcing the ability to use MCP (model context protocol) – compliant tools in agent workflows in Microsoft Copilot Studio. This feature reached general availability on July 15, 2026.
How does this affect me?
This feature allows users to integrate proprietary systems, dynamic knowledge sources, and custom actions into agentic workflows with MCP support. Agent workflows can pass structured inputs to MCP-compliant tools and consume structured outputs downstream, enabling deterministic orchestration around agent-extensible capabilities. This functionality allows usage of the same MCP server across multiple agents and workflows, avoiding bespoke connector development for every system.
MCP tools execute under existing workflow governance, monitoring, and lifecycle management.
What action do I need to take?
This message is for awareness, and no action is required.