Integrate Existing Copilot Agent with A2A Protocol
DRAG DROP
A company uses a primary agent in Copilot Studio to handle user intake.
For some requests, the company wants the primary agent to delegate work to another Copilot Studio agent that already exists.
To meet the business needs, the solution must allow agents to perform the following on the connected agent:
Must allow calls from other agents.
Must allow agents to use the connected agent for collaboration.
Must allow agents to invoke the connected agent in conversations.
You need to integrate the existing Copilot Studio agent with the connected agent.
Which setting should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Community Insight
The question tests the distinction between publishing an agent, adding it as a component, and configuring connections; the common trap is confusing 'Add' with 'Configure connections'.
Learn how to integrate an existing Copilot Studio agent into a multi-agent solution using the Agent-to-Agent (A2A) protocol. This page explains the specific configurations required to enable calls, collaboration, and conversation invocation.
Learners often confuse 'Add the connected agent' with 'Configure connections', failing to recognize that 'Add' registers the agent for collaboration while 'Configure connections' enables direct invocation in conversations.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To meet the business needs, you must map each requirement to its specific configuration step in Copilot Studio. First, to allow calls from other agents, the target agent must be Published; unpublished agents are not discoverable or callable by external entities. Second, to allow agents to use the connected agent for collaboration, you must Add the connected agent to the primary agent's design surface or flow components, making it available for orchestration. Third, to allow agents to invoke the connected agent in conversations, you must Configure connections to the connected agent, which establishes the necessary API endpoints and authentication for runtime interaction.Why Other Candidate Answers Are Wrong
Other potential mappings fail because they misalign the technical action with the functional outcome. For instance, simply adding the agent without publishing it prevents any external calls. Conversely, configuring connections without adding the agent means there is no component in the primary agent's logic to actually trigger those connections during collaboration workflows.Community Comment Notes
Community consensus strongly supports this mapping, with multiple users confirming that publishing is prerequisite for calls, adding is for collaboration structure, and configuring connections is for conversational invocation. As one user noted, "Must allow calls... Publish... Must allow collaboration... Add... Must allow invoke... Configure connections" accurately reflects the exam's expected answer.Exam Strategy
Focus on understanding the lifecycle of an agent: Publishing makes it live, Adding makes it a tool/component in another agent, and Connecting enables the actual data exchange mechanism. Memorize these three distinct states to avoid confusion in drag-and-drop questions.
Frequently Asked Questions
Why does the agent need to be published to allow calls?
Publishing exposes the agent's API endpoint and metadata, making it discoverable and callable by other agents or external systems.
What is the difference between adding and configuring connections?
Adding registers the agent as a reusable component within the primary agent's design, while configuring connections sets up the specific communication channels for runtime invocation.