MCP and A2A Channels for Copilot Studio Agents (Preview)
Publish a Copilot Studio agent so other AI tools and agents can call it, with every request signed in as a real user. Preview, early release environments only, and setup needs an Entra app registration.
Details
- The MCP client channel exposes the agent as a remote server that AI tools can discover and call as a tool
- The A2A client channel exposes it over the Agent2Agent protocol, an open standard for agents handing tasks to each other, so other agents can send it work and get answers back
- Clients sign in through Microsoft Entra ID on behalf of the user, and Copilot Studio checks that user's access to the agent before it responds
- Setup requires an app registration in Entra with delegated permissions. One registration can cover both channels, several clients, and several agents
- Only available in early release cycle environments. Calls consume Copilot Credits
Best for
Making one agent reusable from coding tools, other agent platforms, and orchestrators.
When to use it
A Copilot Studio agent already does a job well and tools or agents outside Studio need to call it.
Who benefits
IT and developer teams connecting agents across platforms.
Join the newsletter to get ahead with AI.
I share strategies, new modules, free guides, and tools to get you better at using AI in your work.
Leading a team? See team programs →