AB-620 · LESSON 2
Integrate and extend agents in Copilot Studio40–45% · 4 topics
Learn to connect enterprise knowledge, add tools, configure multi-agent collaboration and integrate with Azure.
2.1Connect to enterprise knowledge sources
Concept
Knowledge is the information an agent uses to ground its answers. You can connect SharePoint, OneDrive, public websites, uploaded files, Dataverse, Azure AI Search and Microsoft Graph connectors (such as ServiceNow). Sources such as SharePoint are searched based on the user's permissions.
How it works / steps
- Identify where the information needed for answers lives
- Add SharePoint sites and websites as knowledge
- Connect an Azure AI Search index for large or custom document sets
- Connect data from other systems with Graph connectors or connectors
- Write knowledge descriptions and verify answer quality with evaluation
Workplace example
An IT help agent uses SharePoint procedures and ServiceNow knowledge articles (via a Graph connector) as knowledge, answering only with information the user is allowed to view.
Common confusions and exam tips
- Knowledge (search and answer) and tools (perform actions) have different roles
- Mistakes in SharePoint permissions directly affect answers
- Public website knowledge can mix outside information into answers
Mini quiz
Q1. You want to bring knowledge articles stored in ServiceNow into Microsoft 365 and use them for the agent’s search and grounding. Which is most suitable?
- Computer use
- Power Platform connector
- HTTP request node
- Copilot connector
Show answer and explanation
Answer: D Copilot connector
Copilot connectors are suited to ingesting external content for reference. [Other options] Power Platform connectors and HTTP requests call actions on the spot; they do not ingest and index articles in Microsoft 365. Computer use automates UI operations.
Q2. You want the sales agent to register order data in SAP. Which option appropriately implements the register (write) operation?
- Add the Power Platform connector for SAP (or an existing custom connector) as a tool
- Ingest SAP order data into Microsoft 365 with a Copilot connector and have a generative answers node confirm the registration
- Add the SAP order screen manual to knowledge and have the agent guide users through input steps
- Save the order in a Dataverse table and have staff transfer it to SAP in a batch at night
Show answer and explanation
Answer: A Add the Power Platform connector for SAP (or an existing custom connector) as a tool
Operations such as writes are done with tools (connectors). Knowledge is for reference and cannot register data. [Other options] Copilot connectors ingest for search and cannot write. Manual transfer or step guidance does not mean the agent registered the order.
Reference links
2.2Add tools to agents
Concept
Tools are how an agent performs actions in external systems. You can add Power Platform connectors (prebuilt and custom), agent flows, REST APIs (OpenAPI), MCP servers, prompts (AI actions) and computer use (UI automation).
How it works / steps
- Identify the actions needed (look up, register, send)
- Use a prebuilt connector if one exists; otherwise use a custom connector, OpenAPI or MCP
- Write tool names, descriptions and input descriptions so the model can choose them easily
- Decide authentication (the user's credentials or the maker's credentials)
- Consider computer use for legacy systems without an API
Workplace example
Use an ERP custom connector for inventory lookup, an MCP server for knowledge base search, and computer use to operate an old ordering screen that has no API.
Common confusions and exam tips
- Connecting an MCP server makes that server's tools and resources available together
- When an API exists, prefer it over computer use
- Vague tool descriptions lead to the wrong tool being chosen
Mini quiz
Q1. You want to enter data through the UI of an old internal business app that has no API. Which capability is appropriate?
- Custom connector
- HTTP request node
- Copilot connector
- Computer use
Show answer and explanation
Answer: D Computer use
When there is no API, computer use, which automates UI operations, is an option. [Other options] Custom connectors and HTTP requests require an API. Copilot connectors ingest data for search and cannot operate a UI.
Q2. You want the agent to use the tools of an MCP server that is already published internally. What is the appropriate action?
- Register the MCP server as a connected agent and delegate work with A2A
- Add the MCP server’s tool definitions to knowledge and reference them with a generative answers node
- Connect to the MCP server in Copilot Studio and add the tools it provides to the agent
- Create a topic for each tool that calls it individually with an HTTP request node
Show answer and explanation
Answer: C Connect to the MCP server in Copilot Studio and add the tools it provides to the agent
Connecting the MCP server lets you use the tools defined on the server as they are. [Other options] Reimplementing with HTTP requests is unnecessary effort. A2A is for agent-to-agent collaboration, not for connecting MCP servers. Tools cannot be called from knowledge.
Reference links
2.3Configure multi-agent collaboration from Copilot Studio
Concept
In a multi-agent setup, the main agent delegates work to child agents (components inside the same agent) or connected agents (separately published Copilot Studio agents, Foundry agents, Fabric data agents, A2A agents and more). Separating roles makes maintenance and reuse easier.
How it works / steps
- Split the business by role and define each agent's responsibilities
- Use child agents for small, tightly coupled parts and connected agents for parts managed and reused independently
- Write each agent's description so the main agent can call it appropriately
- Configure how much conversation history to pass
- Verify the call path in testing
Workplace example
An employee front-desk agent delegates HR questions to the HR department's published agent and data aggregation to a Fabric data agent.
Common confusions and exam tips
- Child agents are managed inside the main agent; connected agents are published and managed separately
- Overlapping roles make it unpredictable which agent is called
- Check the permissions and authentication of connected agents
Mini quiz
Q1. Which statement correctly describes the difference between MCP and the A2A (Agent2Agent) protocol?
- MCP is only for integration between Microsoft products, and A2A is only for integration with agents in other clouds
- MCP is for agents to connect to tools and data; A2A is for agents to collaborate with each other
- MCP is for agents to collaborate with each other; A2A is for agents to connect to tools and data
- MCP is a standard for knowledge search, and A2A is a standard for delegating agent authentication and permissions
Show answer and explanation
Answer: B MCP is for agents to connect to tools and data; A2A is for agents to collaborate with each other
Their roles differ: tool connection is MCP, and collaboration between agents is A2A. [Other options] The third option reverses the roles. Neither MCP nor A2A is limited to a particular vendor. A2A is not a standard for delegating authentication.
Q2. You want to connect a quote creation agent with a credit check agent. Which multi-agent design is appropriate?
- Combine both agents’ instructions and operate them as a single agent
- Have users ask the same question to the quote agent and the credit agent in turn
- Have a parent agent delegate work to specialist agents according to their roles
- Regularly ingest the quote agent’s answers into the credit agent’s knowledge
Show answer and explanation
Answer: C Have a parent agent delegate work to specialist agents according to their roles
Splitting roles and delegating from a parent agent is better for maintainability and quality. [Other options] Combining them makes role-specific maintenance and evaluation hard. Knowledge cannot connect them in real time, and asking users to enter things twice is not integration.
Reference links
2.4Integrate agents with Azure
Concept
Copilot Studio agents can be extended with Azure capabilities. Use Azure AI Search as knowledge, Foundry models (custom or fine-tuned) in prompts, Foundry agents as connected agents, and Azure Functions or API Management as the foundation for tools.
How it works / steps
- Identify requirements Copilot Studio alone cannot meet (custom models, large-scale search, complex processing)
- Connect an Azure AI Search index as knowledge
- Use models deployed in Foundry
- Call Foundry Agent Service agents as connected agents
- Turn Azure Functions APIs into tools with OpenAPI or custom connectors
Workplace example
Ingest millions of technical documents into Azure AI Search and connect it as knowledge, and perform specialized classification with a fine-tuned model in Foundry.
Common confusions and exam tips
- There is no need to build in Azure what low-code can already handle
- Check Azure-side authentication (managed identities, connections) and networking
- Cost management is split between Copilot Studio and Azure
Mini quiz
Q1. Tens of thousands of internal manuals are already indexed in Azure AI Search. What is the quickest configuration to ground answers in them?
- Fetch Azure AI Search results with an HTTP request node every time and format them
- Connect Azure AI Search as a knowledge source
- Upload the manuals to Copilot Studio as files
- Move the manuals to SharePoint and add the site as knowledge
Show answer and explanation
Answer: B Connect Azure AI Search as a knowledge source
Using the existing index avoids re-ingestion and enables features such as vector search. [Other options] Migrating or re-uploading wastes the existing index. Building it yourself with HTTP requests is not the quickest.
Q2. You want a Copilot Studio agent to use an advanced document analysis agent already built in Microsoft Foundry. Which method is appropriate?
- Integrate the Foundry agent into Copilot Studio and call it as a connected agent
- Port the Foundry agent’s instructions and tool definitions to the Copilot Studio agent
- Select the model used in Foundry in a Copilot Studio custom prompt as a substitute
- Save the Foundry agent’s analysis results to SharePoint and reference them as knowledge
Show answer and explanation
Answer: A Integrate the Foundry agent into Copilot Studio and call it as a connected agent
You can integrate and call Foundry agents from Copilot Studio. Duplicating it means managing two copies. [Other options] Porting or selecting the model alone cannot reproduce the tools and processing on the Foundry side. Referencing saved results is not calling the agent.
Reference links
Lessons are written by this site based on public information and do not guarantee exam content. Product specifications change, so check the latest information at the reference links.
Notes (unofficial, original questions, no pass guarantee)
- The questions on this site are original practice questions written by this site based on publicly available skills outlines and exam guides. They are not actual exam questions.
- Microsoft, Azure, Copilot, Microsoft 365, Dynamics 365 and Power Platform are trademarks of the Microsoft group of companies. This site is not affiliated with or endorsed by Microsoft.
- This content is a study aid and does not guarantee a pass. Exam content, format and prerequisites may change without notice; always check the latest information on the official page before taking the exam.
- Your accuracy on the mock exam cannot be converted to the official (scaled) score and does not predict a pass or fail.
- Progress is saved only in this browser (localStorage) unless you sign in with Google to sync it. You can delete it from the Cookie & storage settings page (Japanese).