All Insights
#AgenticAI
May 2026

Sunday Coffee & Code: Part 1 - Can Copilot Studio Agents Talk to Google Agent Studio Agents over A2A?

I have seen a video or two on this and it seemed possible but the details were thin on the ground so I thought I'd give it a shot today. The rest of this weekโ€™s experiment was a proper learning curve - it seemed simple, except in practice, not so much.

By Steve Harris

I have seen a video or two on this and it seemed possible but the details were thin on the ground so I thought Iโ€™d give it a shot today. The rest of this weekโ€™s experiment was a proper learning curve - it seemed simple, except in practice, not so much.

To start I built a BC Driving Assistant Agent in Google Agent Platform Studio and after a lot of fiddling got it deployed and accessible over A2A.

But, as usual, the interesting pieces came from the bits that did not quite work.

๐—” ๐—ณ๐—ฒ๐˜„ ๐˜๐—ต๐—ถ๐—ป๐—ด๐˜€ ๐—œ ๐—ฟ๐—ฎ๐—ป ๐—ถ๐—ป๐˜๐—ผ:

  • Copilot Studio had trouble finding the Agent Card, even though I could see the Agent Card directly in a browser, and I could see calls from Copilot going to the same URL. That was odd.
  • I then manually configured the Google agent inside Copilot Studio. At that point, I could see the Google agent being called, but Copilot started complaining about an API key. Even though I had no authentication configured. (๐˜ˆ๐˜ฏ๐˜ฅ ๐˜บ๐˜ฆ๐˜ด, ๐˜ฃ๐˜ฆ๐˜ง๐˜ฐ๐˜ณ๐˜ฆ ๐˜ข๐˜ฏ๐˜บ๐˜ฐ๐˜ฏ๐˜ฆ ๐˜ด๐˜ข๐˜บ๐˜ด ๐˜ช๐˜ต, ๐˜ต๐˜ฉ๐˜ฆ ๐˜ถ๐˜ฏ๐˜ข๐˜ถ๐˜ต๐˜ฉ๐˜ฆ๐˜ฏ๐˜ต๐˜ช๐˜ค๐˜ข๐˜ต๐˜ฆ๐˜ฅ ๐˜ต๐˜ฆ๐˜ด๐˜ต ๐˜ด๐˜ฆ๐˜ต๐˜ถ๐˜ฑ ๐˜ฉ๐˜ข๐˜ด ๐˜ฏ๐˜ฐ๐˜ธ ๐˜ฃ๐˜ฆ๐˜ฆ๐˜ฏ ๐˜ต๐˜ข๐˜ฌ๐˜ฆ๐˜ฏ ๐˜ฅ๐˜ฐ๐˜ธ๐˜ฏ.)
  • Itโ€™s not clear whether a Google AI Agent Studio can be directly deployed with an A2A bridge in front of it, referenced only via the Agent ID, or whether the Agent has to be built and deployed via ADK.

๐—” ๐—ณ๐—ฒ๐˜„ ๐—ผ๐—ฏ๐˜€๐—ฒ๐—ฟ๐˜ƒ๐—ฎ๐˜๐—ถ๐—ผ๐—ป๐˜€ ๐—ณ๐—ฟ๐—ผ๐—บ ๐˜๐—ต๐—ฒ ๐—ฝ๐—ฟ๐—ผ๐—ฐ๐—ฒ๐˜€๐˜€:

  • One slightly painful detour was Gemini sending me looking for a slider or button to โ€œenable A2Aโ€ on the agent I had built - which doesnโ€™t look like it exists.
  • I really liked being able to work at the command line with gcloud shell and the cloud shell editor - this suited my working style much better. I could get to the underlying code and configuration files, make changes, rerun the service, tail logs, and troubleshoot much more directly.

The pattern is now making sense though - itโ€™s clear that purpose-specific agents, running in the environments where they work best, connected through A2A, is a very interesting direction (even across completely different vendors).

Part 1 got me to a partially working bridge and a much better understanding of the moving parts. Part 2, next week, will be about getting the handoff working cleanly, understanding the authentication model properly, and seeing whether this can become a practical cross-platform agent pattern rather than just a Sunday morning science project.

Definitely more to learn - but that was the point.

Want to Discuss This Topic?

Steve is always happy to have a direct conversation.