Create a multi-agent solution by using A2A protocol
Unlock the complete study guide + 1,040 practice questions across 16 full exams.
Bundled into the existing Designing and Building Integrated AI Agent Solutions in Copilot Studio premium course — no separate purchase.
14-day money-back guarantee — no questions asked.
Included in this chapter:
- What you are actually delegating over A2A
- Choosing A2A over MCP, a REST tool, or Activity Protocol
- Filling in the Agent2Agent form
- The agent card, and the filename the docs dispute
- The description is your routing control
- Authentication: None, API key, or OAuth 2.0
- Why the connection is reusable, and how far it reaches
- What crosses the boundary on every delegated turn
- Testing the delegation and reading the round trip
- Taking an A2A pilot to production
- How these choices show up in questions
Choosing among the three ways an agent reaches something external
| Consideration | A2A connection | MCP server tool | REST API tool or custom connector |
|---|---|---|---|
| What is on the far side | An agent with its own model, tools and orchestration | A server that publishes a collection of model-callable tools and resources | One API's operations, described by an OpenAPI specification |
| What crosses on a call | A task, plus contextId, message IDs, locale, content parts and the full chat history | Typed inputs for one tool call, and that call's typed output | An HTTP request and its response |
| Who decides how the work gets done | The external agent, using its own reasoning; its tools are opaque to your orchestrator | Your orchestrator selects which tools to invoke and synthesizes the final output | You do, when you author the call |
| Multiturn support | Full, because contextId allows context management across agents | Limited, because context management stays with the orchestrator | Single request and response |
| How the far side is discovered | An agent card, fetched from the well-known path under the endpoint you entered | Server-owned metadata, listed from the server itself | The OpenAPI specification you import |
| Where it lands in the product | The Agents page, added with Add an agent | The Tools page | The Tools page |
| Microsoft's one-line rule | Delegate tasks to another agent, not just call APIs | Use MCP tools or resources with MCP servers | Connect to APIs or basic HTTP services with custom connectors or HTTP tools |
Decision tree
Cheat sheet
Unlock with Premium — includes all practice exams and the complete study guide.
Also tested in
References
- Connect to an agent over the Agent2Agent (A2A) protocol
- Understand the Agent2Agent (A2A) protocol - Microsoft Learn training
- Connect a Copilot Studio agent to an A2A-enabled agent - Microsoft Learn training
- Add other agents overview
- Connect to an A2A agent endpoint from Foundry Agent Service
- Orchestrate agent behavior with generative AI
- Test and validate an A2A agent connection - Microsoft Learn training