Microsoft Designing and Building Integrated AI Agent Solutions in Copilot Studio - AB-620 FREE EXAM DUMPS QUESTIONS & ANSWERS
A company is building an agent in Copilot Studio.
The agent must meet the following requirements:
- Responses must be grounded in approved internal content.
- The agent must be able to retrieve information from configured data
sources in a topic.
You need to configure the agent so that topic responses are grounded from custom data sources.
What should you configure?
The agent must meet the following requirements:
- Responses must be grounded in approved internal content.
- The agent must be able to retrieve information from configured data
sources in a topic.
You need to configure the agent so that topic responses are grounded from custom data sources.
What should you configure?
Correct Answer: C
Vote an answer
Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A company is configuring an agent in Copilot Studio that uses a generative answers node inside multiple topics.
The company requires responses to meet the following requirements:
- Must use an executive summary format.
- Must apply only within a specific topic.
- Must continue using configured knowledge sources.
- Must comply with connector security controls.
You need to configure a custom prompt to meet the formatting requirements.
Solution: Add instructions in the custom prompt tool to restrict connector access during runtime.
Does the solution meet the goal?
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A company is configuring an agent in Copilot Studio that uses a generative answers node inside multiple topics.
The company requires responses to meet the following requirements:
- Must use an executive summary format.
- Must apply only within a specific topic.
- Must continue using configured knowledge sources.
- Must comply with connector security controls.
You need to configure a custom prompt to meet the formatting requirements.
Solution: Add instructions in the custom prompt tool to restrict connector access during runtime.
Does the solution meet the goal?
Correct Answer: A
Vote an answer
Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).
Case Study 2 - Fabrikam Inc.
Background
Fabrikam Inc. is a Canada-based manufacturer with a growing service organization that supports field technicians and internal operations teams. Fabrikam Inc. plans to launch a new internal agent solution named Operations Concierge to reduce time spent searching policy content, retrieving operational metrics, and executing routine transactions.
The agent will be used by three groups:
- Service coordinators who triage incoming service requests
- Field technicians who need guided procedures and parts availability
- Operations managers who monitor KPIs and exceptions
The agent solution must work in real-world operational conditions. Users often ask questions mid- call with a customer or while coordinating parts shipments. The agents require quick, reliable outcomes. As a result, Fabrikam Inc. requires the solution to:
- Provide grounded answers with traceability when it provides guidance.
- Retrieve real-time metrics when users ask for operational status.
- Execute authenticated updates when users initiate a flow (such as creating a parts request).
Fabrikam Inc. also expects the solution to be maintained by multiple makers and developers across the year. The company has experienced duplicated logic and inconsistent behavior across different agents. This project emphasizes reuse, governance, and maintainability across teams.
Current environment
Fabrikam Inc. runs three Microsoft Power Platform environments for agent development and release: Dev, Test, and Prod.
The team plans to build the agent and validate it in Dev and Test, then promote to Prod by using a controlled release process that supports repeatable deployments.
Fabrikam Inc. already has two assets the team wants to reuse:
- A partially completed Copilot Studio agent named Service Desk Agent, used by IT to create internal tickets and route requests
- A Microsoft Foundry agent created by a central AI team that performs specialized summarization and classification for long-form text (for example, summarizing call transcripts into an incident narrative) Fabrikam Inc. also has operational and knowledge data sources:
- A curated policy library (internal SOPs, service warranty rules, escalation criteria, and standard operating procedures)
- A set of indexed documents and procedures in an Azure AI Search service that supports vector search for the policy library
- A Microsoft Fabric workspace that includes a semantic model used by operations leadership for reporting Business requirements Fabrikam Inc. requires Operations Concierge to meet the following business requirements:
- Traceability requirement: When the agent provides policy guidance or procedural recommendations, users must be able to see where the answer came from.
- Metrics requirement: When users ask about service performance (backlog, SLA risk, parts shortages, dispatch delays), the solution must return up-to-date metrics in a structured format that operations managers can use in weekly reviews.
- Transaction requirement: The solution must support authenticated updates initiated during conversations, including creating a parts request and updating a service case status.
In addition, Fabrikam Inc. wants to avoid duplicating common assets across agents:
- The team must reuse the same set of escalation topics, MCP tool definitions, and a standard safety disclaimer across three different agents.
- Only the platform engineering group as allowed to edit shared assets. However, all agent authors must be able to use them.
Technical requirements
The Fabrikam Inc. solution architecture uses a multi-agent approach so that specialist responsibilities are isolated and can evolve independently.
The Operations Concierge (primary agent) must coordinate the following specialist capabilities:
- Policy and procedure Q&A: Use an enterprise knowledge source that supports indexed retrieval across the curated policy library and service procedures.
- Operational metrics: Delegate metric queries to a Fabric Data Agent that reads governed business data through the Fabric semantic model.
- Authenticated updates: Use tools exposed by an existing internal Model Context Protocol (MCP) server that provides transactional operations for the service organization.
- Specialized processing: Delegate summarization and classification requests to an existing Microsoft Foundry agent.
Fabrikam Inc. will onboard two MCP servers as tools:
- PartsOps MCP server: exposes tools for parts availability checks and parts request creation.
The server requires per-user authentication because actions must be traceable to the requesting user.
- WarrantyRules MCP server: exposes a read-only tool for validating warranty coverage. The server uses an API key shared by the agent team.
Fabrikam Inc. has also defined a collaboration requirement with the existing Service Desk Agent:
- The primary agent must delegate IT-specific requests to the existing Service Desk Agent rather than reimplement ticket creation logic.
Finally, Fabrikarn Inc. plans to support a partner integration:
- For shipment tracking inquiries, Fabrikam Inc. will delegate to a partner-provided agent that is only available through a standardized agent-to-agent endpoint.
Issues and constraints
During early testing, Fabrikam Inc. found three recurring problems:
- Makers are copying and modifying the same components across agents, resulting in inconsistent disclaimers and duplicated tools.
- Users can obtain a correct answer, but the response is not consistently traceable to a source when the agent uses knowledge.
- The primary agent can route some requests, but specialist capabilities are not consistently delegated (for example, some metric questions are answered generatively instead of being routed to the Fabric Data Agent).
You are part of the engineering team responsible for correcting the design and configuration to meet the preceding requirements and constraints.
Drag and Drop Question
You need to plan how Fabrikam Inc. will reuse shared components across multiple agents while limiting who can change the shared components.
Which approach should you use for each requirement? To answer, move the appropriate components to the correct requirements. You may use each component 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.
Background
Fabrikam Inc. is a Canada-based manufacturer with a growing service organization that supports field technicians and internal operations teams. Fabrikam Inc. plans to launch a new internal agent solution named Operations Concierge to reduce time spent searching policy content, retrieving operational metrics, and executing routine transactions.
The agent will be used by three groups:
- Service coordinators who triage incoming service requests
- Field technicians who need guided procedures and parts availability
- Operations managers who monitor KPIs and exceptions
The agent solution must work in real-world operational conditions. Users often ask questions mid- call with a customer or while coordinating parts shipments. The agents require quick, reliable outcomes. As a result, Fabrikam Inc. requires the solution to:
- Provide grounded answers with traceability when it provides guidance.
- Retrieve real-time metrics when users ask for operational status.
- Execute authenticated updates when users initiate a flow (such as creating a parts request).
Fabrikam Inc. also expects the solution to be maintained by multiple makers and developers across the year. The company has experienced duplicated logic and inconsistent behavior across different agents. This project emphasizes reuse, governance, and maintainability across teams.
Current environment
Fabrikam Inc. runs three Microsoft Power Platform environments for agent development and release: Dev, Test, and Prod.
The team plans to build the agent and validate it in Dev and Test, then promote to Prod by using a controlled release process that supports repeatable deployments.
Fabrikam Inc. already has two assets the team wants to reuse:
- A partially completed Copilot Studio agent named Service Desk Agent, used by IT to create internal tickets and route requests
- A Microsoft Foundry agent created by a central AI team that performs specialized summarization and classification for long-form text (for example, summarizing call transcripts into an incident narrative) Fabrikam Inc. also has operational and knowledge data sources:
- A curated policy library (internal SOPs, service warranty rules, escalation criteria, and standard operating procedures)
- A set of indexed documents and procedures in an Azure AI Search service that supports vector search for the policy library
- A Microsoft Fabric workspace that includes a semantic model used by operations leadership for reporting Business requirements Fabrikam Inc. requires Operations Concierge to meet the following business requirements:
- Traceability requirement: When the agent provides policy guidance or procedural recommendations, users must be able to see where the answer came from.
- Metrics requirement: When users ask about service performance (backlog, SLA risk, parts shortages, dispatch delays), the solution must return up-to-date metrics in a structured format that operations managers can use in weekly reviews.
- Transaction requirement: The solution must support authenticated updates initiated during conversations, including creating a parts request and updating a service case status.
In addition, Fabrikam Inc. wants to avoid duplicating common assets across agents:
- The team must reuse the same set of escalation topics, MCP tool definitions, and a standard safety disclaimer across three different agents.
- Only the platform engineering group as allowed to edit shared assets. However, all agent authors must be able to use them.
Technical requirements
The Fabrikam Inc. solution architecture uses a multi-agent approach so that specialist responsibilities are isolated and can evolve independently.
The Operations Concierge (primary agent) must coordinate the following specialist capabilities:
- Policy and procedure Q&A: Use an enterprise knowledge source that supports indexed retrieval across the curated policy library and service procedures.
- Operational metrics: Delegate metric queries to a Fabric Data Agent that reads governed business data through the Fabric semantic model.
- Authenticated updates: Use tools exposed by an existing internal Model Context Protocol (MCP) server that provides transactional operations for the service organization.
- Specialized processing: Delegate summarization and classification requests to an existing Microsoft Foundry agent.
Fabrikam Inc. will onboard two MCP servers as tools:
- PartsOps MCP server: exposes tools for parts availability checks and parts request creation.
The server requires per-user authentication because actions must be traceable to the requesting user.
- WarrantyRules MCP server: exposes a read-only tool for validating warranty coverage. The server uses an API key shared by the agent team.
Fabrikam Inc. has also defined a collaboration requirement with the existing Service Desk Agent:
- The primary agent must delegate IT-specific requests to the existing Service Desk Agent rather than reimplement ticket creation logic.
Finally, Fabrikarn Inc. plans to support a partner integration:
- For shipment tracking inquiries, Fabrikam Inc. will delegate to a partner-provided agent that is only available through a standardized agent-to-agent endpoint.
Issues and constraints
During early testing, Fabrikam Inc. found three recurring problems:
- Makers are copying and modifying the same components across agents, resulting in inconsistent disclaimers and duplicated tools.
- Users can obtain a correct answer, but the response is not consistently traceable to a source when the agent uses knowledge.
- The primary agent can route some requests, but specialist capabilities are not consistently delegated (for example, some metric questions are answered generatively instead of being routed to the Fabric Data Agent).
You are part of the engineering team responsible for correcting the design and configuration to meet the preceding requirements and constraints.
Drag and Drop Question
You need to plan how Fabrikam Inc. will reuse shared components across multiple agents while limiting who can change the shared components.
Which approach should you use for each requirement? To answer, move the appropriate components to the correct requirements. You may use each component 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.
Correct Answer:
Explanation:
Box 1: Share the component collection with teammates while controlling edit access.
Prevent shared assets from being modified by most builders.
The best action to take is to share the component collection with teammates while controlling edit access.
In Microsoft Copilot Studio, component collections are designed specifically to centralize and reuse assets (like topics, knowledge sources, and actions) across multiple separate agents.
When configuring a component collection, administrators or collection owners can utilize built-in sharing permissions to explicitly assign roles to individual makers or groups:
Box 2: Create a component collection and move shared components into it Reuse the same set of components across multiple agents without copying.
The best action to take is to create a component collection and move shared components into it.
In Microsoft Copilot Studio, Component Collections provide a central container to package and share topics, knowledge bases, actions, and entities across multiple agents without duplicating the assets. Once a collection is created, you can establish governance controls (such as managing it within a managed solution) so that makers on other agents can utilize the shared resources but cannot modify them.
Box 3: Restrict component collection to the primary agent
Limits a shared set of components so it can be used only be its intended primary agent.
The best action to take is to restrict component collection to the primary agent. In Microsoft Copilot Studio, you can restrict a shared set of components so that it can be used only by its intended agent. This feature helps teams modularize large or sensitive agents and prevents unauthorized reuse.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-export-import-copilot-components
Case Study 2 - Fabrikam Inc.
Background
Fabrikam Inc. is a Canada-based manufacturer with a growing service organization that supports field technicians and internal operations teams. Fabrikam Inc. plans to launch a new internal agent solution named Operations Concierge to reduce time spent searching policy content, retrieving operational metrics, and executing routine transactions.
The agent will be used by three groups:
- Service coordinators who triage incoming service requests
- Field technicians who need guided procedures and parts availability
- Operations managers who monitor KPIs and exceptions
The agent solution must work in real-world operational conditions. Users often ask questions mid- call with a customer or while coordinating parts shipments. The agents require quick, reliable outcomes. As a result, Fabrikam Inc. requires the solution to:
- Provide grounded answers with traceability when it provides guidance.
- Retrieve real-time metrics when users ask for operational status.
- Execute authenticated updates when users initiate a flow (such as creating a parts request).
Fabrikam Inc. also expects the solution to be maintained by multiple makers and developers across the year. The company has experienced duplicated logic and inconsistent behavior across different agents. This project emphasizes reuse, governance, and maintainability across teams.
Current environment
Fabrikam Inc. runs three Microsoft Power Platform environments for agent development and release: Dev, Test, and Prod.
The team plans to build the agent and validate it in Dev and Test, then promote to Prod by using a controlled release process that supports repeatable deployments.
Fabrikam Inc. already has two assets the team wants to reuse:
- A partially completed Copilot Studio agent named Service Desk Agent, used by IT to create internal tickets and route requests
- A Microsoft Foundry agent created by a central AI team that performs specialized summarization and classification for long-form text (for example, summarizing call transcripts into an incident narrative) Fabrikam Inc. also has operational and knowledge data sources:
- A curated policy library (internal SOPs, service warranty rules, escalation criteria, and standard operating procedures)
- A set of indexed documents and procedures in an Azure AI Search service that supports vector search for the policy library
- A Microsoft Fabric workspace that includes a semantic model used by operations leadership for reporting Business requirements Fabrikam Inc. requires Operations Concierge to meet the following business requirements:
- Traceability requirement: When the agent provides policy guidance or procedural recommendations, users must be able to see where the answer came from.
- Metrics requirement: When users ask about service performance (backlog, SLA risk, parts shortages, dispatch delays), the solution must return up-to-date metrics in a structured format that operations managers can use in weekly reviews.
- Transaction requirement: The solution must support authenticated updates initiated during conversations, including creating a parts request and updating a service case status.
In addition, Fabrikam Inc. wants to avoid duplicating common assets across agents:
- The team must reuse the same set of escalation topics, MCP tool definitions, and a standard safety disclaimer across three different agents.
- Only the platform engineering group as allowed to edit shared assets. However, all agent authors must be able to use them.
Technical requirements
The Fabrikam Inc. solution architecture uses a multi-agent approach so that specialist responsibilities are isolated and can evolve independently.
The Operations Concierge (primary agent) must coordinate the following specialist capabilities:
- Policy and procedure Q&A: Use an enterprise knowledge source that supports indexed retrieval across the curated policy library and service procedures.
- Operational metrics: Delegate metric queries to a Fabric Data Agent that reads governed business data through the Fabric semantic model.
- Authenticated updates: Use tools exposed by an existing internal Model Context Protocol (MCP) server that provides transactional operations for the service organization.
- Specialized processing: Delegate summarization and classification requests to an existing Microsoft Foundry agent.
Fabrikam Inc. will onboard two MCP servers as tools:
- PartsOps MCP server: exposes tools for parts availability checks and parts request creation.
The server requires per-user authentication because actions must be traceable to the requesting user.
- WarrantyRules MCP server: exposes a read-only tool for validating warranty coverage. The server uses an API key shared by the agent team.
Fabrikam Inc. has also defined a collaboration requirement with the existing Service Desk Agent:
- The primary agent must delegate IT-specific requests to the existing Service Desk Agent rather than reimplement ticket creation logic.
Finally, Fabrikarn Inc. plans to support a partner integration:
- For shipment tracking inquiries, Fabrikam Inc. will delegate to a partner-provided agent that is only available through a standardized agent-to-agent endpoint.
Issues and constraints
During early testing, Fabrikam Inc. found three recurring problems:
- Makers are copying and modifying the same components across agents, resulting in inconsistent disclaimers and duplicated tools.
- Users can obtain a correct answer, but the response is not consistently traceable to a source when the agent uses knowledge.
- The primary agent can route some requests, but specialist capabilities are not consistently delegated (for example, some metric questions are answered generatively instead of being routed to the Fabric Data Agent).
You are part of the engineering team responsible for correcting the design and configuration to meet the preceding requirements and constraints.
You need to enable Operations Concierge to delegate shipment tracking inquiries according to Fabrikam Inc.'s defined architecture and technical requirements.
Which integration approach should you use?
Background
Fabrikam Inc. is a Canada-based manufacturer with a growing service organization that supports field technicians and internal operations teams. Fabrikam Inc. plans to launch a new internal agent solution named Operations Concierge to reduce time spent searching policy content, retrieving operational metrics, and executing routine transactions.
The agent will be used by three groups:
- Service coordinators who triage incoming service requests
- Field technicians who need guided procedures and parts availability
- Operations managers who monitor KPIs and exceptions
The agent solution must work in real-world operational conditions. Users often ask questions mid- call with a customer or while coordinating parts shipments. The agents require quick, reliable outcomes. As a result, Fabrikam Inc. requires the solution to:
- Provide grounded answers with traceability when it provides guidance.
- Retrieve real-time metrics when users ask for operational status.
- Execute authenticated updates when users initiate a flow (such as creating a parts request).
Fabrikam Inc. also expects the solution to be maintained by multiple makers and developers across the year. The company has experienced duplicated logic and inconsistent behavior across different agents. This project emphasizes reuse, governance, and maintainability across teams.
Current environment
Fabrikam Inc. runs three Microsoft Power Platform environments for agent development and release: Dev, Test, and Prod.
The team plans to build the agent and validate it in Dev and Test, then promote to Prod by using a controlled release process that supports repeatable deployments.
Fabrikam Inc. already has two assets the team wants to reuse:
- A partially completed Copilot Studio agent named Service Desk Agent, used by IT to create internal tickets and route requests
- A Microsoft Foundry agent created by a central AI team that performs specialized summarization and classification for long-form text (for example, summarizing call transcripts into an incident narrative) Fabrikam Inc. also has operational and knowledge data sources:
- A curated policy library (internal SOPs, service warranty rules, escalation criteria, and standard operating procedures)
- A set of indexed documents and procedures in an Azure AI Search service that supports vector search for the policy library
- A Microsoft Fabric workspace that includes a semantic model used by operations leadership for reporting Business requirements Fabrikam Inc. requires Operations Concierge to meet the following business requirements:
- Traceability requirement: When the agent provides policy guidance or procedural recommendations, users must be able to see where the answer came from.
- Metrics requirement: When users ask about service performance (backlog, SLA risk, parts shortages, dispatch delays), the solution must return up-to-date metrics in a structured format that operations managers can use in weekly reviews.
- Transaction requirement: The solution must support authenticated updates initiated during conversations, including creating a parts request and updating a service case status.
In addition, Fabrikam Inc. wants to avoid duplicating common assets across agents:
- The team must reuse the same set of escalation topics, MCP tool definitions, and a standard safety disclaimer across three different agents.
- Only the platform engineering group as allowed to edit shared assets. However, all agent authors must be able to use them.
Technical requirements
The Fabrikam Inc. solution architecture uses a multi-agent approach so that specialist responsibilities are isolated and can evolve independently.
The Operations Concierge (primary agent) must coordinate the following specialist capabilities:
- Policy and procedure Q&A: Use an enterprise knowledge source that supports indexed retrieval across the curated policy library and service procedures.
- Operational metrics: Delegate metric queries to a Fabric Data Agent that reads governed business data through the Fabric semantic model.
- Authenticated updates: Use tools exposed by an existing internal Model Context Protocol (MCP) server that provides transactional operations for the service organization.
- Specialized processing: Delegate summarization and classification requests to an existing Microsoft Foundry agent.
Fabrikam Inc. will onboard two MCP servers as tools:
- PartsOps MCP server: exposes tools for parts availability checks and parts request creation.
The server requires per-user authentication because actions must be traceable to the requesting user.
- WarrantyRules MCP server: exposes a read-only tool for validating warranty coverage. The server uses an API key shared by the agent team.
Fabrikam Inc. has also defined a collaboration requirement with the existing Service Desk Agent:
- The primary agent must delegate IT-specific requests to the existing Service Desk Agent rather than reimplement ticket creation logic.
Finally, Fabrikarn Inc. plans to support a partner integration:
- For shipment tracking inquiries, Fabrikam Inc. will delegate to a partner-provided agent that is only available through a standardized agent-to-agent endpoint.
Issues and constraints
During early testing, Fabrikam Inc. found three recurring problems:
- Makers are copying and modifying the same components across agents, resulting in inconsistent disclaimers and duplicated tools.
- Users can obtain a correct answer, but the response is not consistently traceable to a source when the agent uses knowledge.
- The primary agent can route some requests, but specialist capabilities are not consistently delegated (for example, some metric questions are answered generatively instead of being routed to the Fabric Data Agent).
You are part of the engineering team responsible for correcting the design and configuration to meet the preceding requirements and constraints.
You need to enable Operations Concierge to delegate shipment tracking inquiries according to Fabrikam Inc.'s defined architecture and technical requirements.
Which integration approach should you use?
Correct Answer: A
Vote an answer
Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).
Drag and Drop Question
You run the same fixed test set three times in Copilot Studio.
During evaluation, you observe the following:
- The same interaction fails in all three runs.
- Score values range from 0.58 to 0.61.
- The reasoning states that the response partially matches the expected answer.
- The knowledge source that is used is internal documentation.
- No tools are invoked.
You need to determine which conclusions are supported based on the evaluation results.
Which conclusions should you make? To answer, move the appropriate conclusions to the correct evaluation results. You may use each conclusion 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.
You run the same fixed test set three times in Copilot Studio.
During evaluation, you observe the following:
- The same interaction fails in all three runs.
- Score values range from 0.58 to 0.61.
- The reasoning states that the response partially matches the expected answer.
- The knowledge source that is used is internal documentation.
- No tools are invoked.
You need to determine which conclusions are supported based on the evaluation results.
Which conclusions should you make? To answer, move the appropriate conclusions to the correct evaluation results. You may use each conclusion 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.
Correct Answer:
Explanation:
Box 1: A pattern failure across repeated runs.
The correct conclusion concerning evidence of a recurring issue is a) a pattern failure across repeated runs.
When the exact same interaction fails across three repeated runs, it establishes a systemic, predictable pattern rather than an isolated, one-time anomaly.
Box 2: The response partially matches the expected answer.
Based on the evaluation criteria in Microsoft Copilot Studio, the most definitive and direct conclusion that can be made concerning response quality is that the response partially matches the expected answer.
Direct Evidence: The evaluation results explicitly state in the reasoning that the "response partially matches the expected answer." This directly provides a qualitative conclusion regarding the quality of the generated response.
Score Alignment: The semantic similarity or quality score values ranging from 0.58 to 0.61 align with a partial match. In AI evaluation metrics, a perfect match is represented by 1.0, while values in the 0.6x range indicate that the core context was captured but lacked full completeness or exactness.
Box 3: Use of a connected knowledge source during the interaction
Because generative AI outputs are non-deterministic, running the same test set across a dynamic environment can yield varying scores. In Microsoft Copilot Studio, observing scores consistently between 0.58 and 0.61 points to a fundamental limitation with the underlying knowledge source.
The evaluation points to option use of a connected knowledge source during the interaction.
Because no tools are invoked, the agent heavily relies on generative search (retrieval-augmented generation) over internal documentation. The score range and reasoning indicate that the agent successfully retrieves a document but relies on a probabilistic model to paraphrase or assemble the response, which results in a "partial match" rather than an exact extraction.
Incorrect:
In contrast, specific underlying causes require explicit tool invocations or system error logs to diagnose, which are not present here.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-agent-evaluation-results
Drag and Drop Question
A company is extending agents in Copilot Studio with both external capabilities and enterprise content access. Some user requests require grounded answers, while other requests require executing actions.
To meet the business needs, the agent must meet the following requirements:
- Ground answers using results from enterprise data.
- Invoke callable functions exposed through a standardized tool
interface.
- Write an update to a system by using an authenticated action during
the conversation.
You need to integrate the correct approach to meet the requirements.
What should you integrate for each requirement? To answer, move the appropriate integrations to the correct requirements. You may use each integration 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.
A company is extending agents in Copilot Studio with both external capabilities and enterprise content access. Some user requests require grounded answers, while other requests require executing actions.
To meet the business needs, the agent must meet the following requirements:
- Ground answers using results from enterprise data.
- Invoke callable functions exposed through a standardized tool
interface.
- Write an update to a system by using an authenticated action during
the conversation.
You need to integrate the correct approach to meet the requirements.
What should you integrate for each requirement? To answer, move the appropriate integrations to the correct requirements. You may use each integration 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.
Correct Answer:
Explanation:
Box 1: Add a Copilot connector knowledge source for index content
To extend a Copilot Studio agent to provide grounded answers using enterprise data (such as ERP, CRM, or document stores), the correct integration action is to add a Copilot connector knowledge source for index content.
Copilot connectors crawl your enterprise content and index it into the search index. This allows the agent's generative answers to quickly retrieve and ground responses in trusted business data.
Box 2: Connect to an MCP server and add its tools to the agent
Standardized Tool Interface: The Model Context Protocol (MCP) is a universal, open standard interface specifically built to let large language models securely interact with external tools and callable functions.
Executing Actions: When you link an MCP server to your Copilot Studio agent, any executable capabilities or functions exposed by that server automatically become functional tools that your agent can invoke.
Box 3: Add a Power Platform connector tool and call it from a topic
For extending a Copilot Studio agent to execute authenticated, real-time updates to an external system, the correct action to take is to add a Power Platform connector tool and call it from a topic.
Executing Actions & Writing Data: Power Platform connectors (prebuilt or custom) are explicitly designed to perform actions like creating, reading, updating, or deleting records (CRUD operations) in backend systems.
Authentication: Connectors natively support security configurations, allowing you to easily map credentials so the agent executes the update using either maker-provided or specific end-user Microsoft Entra ID authentication. You can also control access at the topic level to ensure triggers execute precisely when required.
Reference:
https://learn.microsoft.com/en-us/microsoft-copilot-studio/copilot-connectors-in-copilot-studio
https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-tools-custom-agent