Power Platform Community Forum Thread Details

Hi all,

Has anyone tested Copilot Studio A2A across different environments and confirmed whether:

The conversation context/transcript carries over to the second agent, and
Live agent handoff still works after that A2A transfer?

Our scenario is:

Agent A in one environment Agent B in another environment
Agent A invokes Agent B through A2A
Agent B may then create a case or hand off to a human agent
The main question is whether the downstream agent (and possibly the human agent) receives the prior conversation context, or whether the interaction effectively restarts.

Any tested guidance, limitations, or implementation notes would be appreciated.

Categories:

General topics

Hi @CT-20042235-0,

Found confirmed answers to both questions from Microsoft docs.

1. Conversation context across A2A:

Microsoft docs confirm: "Copilot Studio passes along the conversation history by default when one agent calls another, so the connected agent understands the previous context of the conversation."

For A2A specifically, the chat history is passed in the A2A payload metadata under the key `copilotstudio.microsoft.com/a2a/chathistory` as a structured array of messages. Agent B receives this metadata and can use it for routing and context. This works across environments.

2. Live agent handoff after A2A transfer:

This is where it gets more complex. Microsoft docs confirm: "Once the end user triggers a handoff, Copilot Studio initiates the handoff with full chat context."

However, this applies to handoff initiated from the agent that is serving the conversation. When Agent B (in environment 2) triggers handoff, the handoff goes to Agent B's configured engagement hub (Omnichannel, ServiceNow, etc.) with the context Agent B has received.

The key limitation: if Agent A initiates the A2A call to Agent B, and Agent B triggers handoff, the human agent receives the context Agent B has but Agent B must be properly configured with an engagement hub in its own environment. The handoff doesn't route back through Agent A's engagement hub.

So your architecture needs Agent B to have its own engagement hub configuration if live agent handoff from Agent B is required.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-agent-agent-to-agent

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/multi-agent-patterns

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube