Answered

Approach for exposing a Copilot Studio agent as an inbound A2A peer

(0) Share

Report

Posted on by CU22071116-1

Hi,

I'm looking to expose a Copilot Studio agent so that external A2A-compliant agents can discover and call into it as a peer.

From what I can tell, Copilot Studio's current A2A support is outbound-only therefore it can act as an A2A client, connecting to and orchestrating external agents via .well-known agent cards. However, I haven't found native support for the reverse direction i.e., Copilot Studio publishing itself as an A2A server with a discoverable agent card and inbound task endpoints.

If my understanding is correct, could you please share the recommended approach for exposing a Copilot Studio agent inbound over A2A? Any pointers, patterns, or samples would be much appreciated.

Thanks in advance for any guidance.

Categories:

Autonomous agents

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

Sayali-MSFT Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hello CU22071116-1,

Yes, that understanding looks correct. Current Copilot Studio A2A support appears to be focused on outbound connectivity, where Copilot Studio connects to and orchestrates external A2A-compliant agents through their endpoint and agent card. I have not seen native support yet for publishing a Copilot Studio agent itself as an A2A server with a discoverable .well-known agent card and inbound task endpoints.
The practical workaround is to place a small bridge/proxy service in front of the Copilot Studio agent. That service exposes the A2A server contract, publishes the agent card, receives inbound A2A tasks, then forwards the request to the Copilot Studio agent using a supported channel such as Direct Line, Bot Framework, or the Copilot Studio SDK/API pattern, and returns the response back in A2A format. There are community samples following this bridge pattern, for example exposing a Copilot Studio agent as an A2A server using Microsoft Agent Framework and translating A2A JSON-RPC calls into Copilot Studio calls.
1.bradrlaw/copilot-studio-a2a: Expose Microsoft Copilot Studio agents as A2A (Agent-to-Agent) protocol servers
2.copilot-studio-a2a/README.md at main · bradrlaw/copilot-studio-a2a
So, at this point, I would not treat inbound A2A hosting as a native Copilot Studio feature. The supported pattern is either outbound A2A from Copilot Studio to external agents, or a custom A2A bridge if external agents need to discover and call a Copilot Studio agent as a peer.

Was this reply helpful? Yes No
CU22071116-1 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks so much for confirming this and for the pointer to that repo, it's very helpful.

One follow-up, if you're able to share: is native inbound A2A support (Copilot Studio publishing itself as an A2A server) something on the roadmap? Trying to gauge whether it's worth investing in a custom bridge now, or whether it's worth waiting given how quickly the A2A/agent interop space is moving.

Appreciate any insight you can share.

Was this reply helpful? Yes No