Policy questions → Delegate to a knowledge-focused agent; Metric requirements → Delegate to a data-access agent; Transaction requirements → Delegate to a tools-first agent.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The architecture should separate responsibilities according to the kind of work each specialist performs. Policy and procedure questions depend on retrieval from curated, indexed content and therefore belong with a knowledge-focused agent. Operational measures such as backlog, SLA exposure, and parts shortages require governed, current business data; a data-access specialist, represented in this case by the Fabric Data Agent, is the correct destination. Creating a parts request or changing a service-case status is different from answering a question: it is an authenticated transaction and should be delegated to a tools-first agent that can invoke approved MCP operations. Putting all three responsibilities into one agent would increase the number of competing tools and knowledge sources, weaken routing precision, and duplicate logic already owned by specialist teams. The selected pattern also matches Fabrikam ' s requirement that capabilities evolve independently. Clear names, descriptions, inputs, and outputs remain essential because generative orchestration uses that metadata to decide which connected agent to invoke. This division gives the primary agent a coordination role while each specialist retains its own knowledge, privileges, release lifecycle, and audit boundary. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Design multi-agent solutions in Copilot Studio.

===============

Trace each answer to its source → Instruct the agent to cite sources in knowledge settings; Retrieve from the centralized index → Configure Azure AI Search as the grounding data source; Use an enterprise-approved foundation model → Select a model from the Foundry model catalog.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Each requirement is controlled by a different configuration layer. Source traceability is a presentation and grounding requirement, so citations must be enabled or explicitly required for knowledge-based responses. That allows users to inspect the material used to support a policy answer; it is not achieved merely by choosing a model. Centralized retrieval is provided by connecting the existing Azure AI Search vector index as the knowledge source. This preserves the curated index, semantic or vector retrieval behavior, and enterprise management of the policy corpus instead of copying documents into the agent. Model governance is handled in the prompt configuration by selecting the approved model from the Microsoft Foundry model catalog. Publishing does not automatically replace an unapproved model, and Azure AI Search does not enforce the foundation-model selection. Together, the three settings form a complete RAG path: Azure AI Search retrieves authoritative passages, the governed model produces the response, and citation settings expose provenance. The configuration should then be tested with representative policy questions to confirm that the response is grounded and that the cited source actually supports the answer. Study Guide alignment: Integrate and extend agents in Copilot Studio > Integrate agents with Azure > Configure generative answers by using Azure AI Search with Foundry; Configure custom prompts to use the Foundry model catalog.

===============

Callable external summarization agent → Add an external agent of type Microsoft Foundry; Correct Foundry project and agent → Enter the Foundry project endpoint URL to create the connection.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The existing specialist should be connected as a Microsoft Foundry agent, not converted into indexed knowledge. A connected agent remains callable and can execute its own summarization and classification behavior when Operations Concierge delegates a matching request. During connection creation, Copilot Studio uses the Microsoft Foundry project endpoint URL to identify the project context and make the relevant agent available for selection. This is distinct from a model endpoint used directly by a custom prompt and from a knowledge-source connection used only for retrieval. Publishing the Copilot Studio agent is part of making a completed design available to users, but it is not the action that establishes the Foundry connection. Adding the Foundry output to an index would turn prior output into retrievable content and would not invoke the specialist on demand. The connected agent should receive a precise description covering long-form transcript summarization and classification, and the integration should be tested with representative inputs to confirm that delegation occurs, the correct Foundry agent runs, and the returned result is incorporated into the main conversation. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Integrate a Foundry agent.

===============

Authenticated governed access → Select service-principal authentication; Required curated vector index → Enter the Azure AI Search index name; Correct Azure AI Search service instance → Provide the Azure AI Search endpoint URL.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: An Azure AI Search connection needs three distinct pieces of configuration. The endpoint identifies the search-service instance that hosts Fabrikam ' s indexed documents. The index name then selects the specific vector index containing the curated policies and procedures. Authentication determines how Copilot Studio is authorized to query that service. Because the scenario requires governed application access rather than a maker ' s personal identity, the service-principal option is the appropriate selection from the choices provided. Enabling citations is useful after retrieval is configured, but it does not establish the service connection or select an index. Microsoft recommends creating Azure AI Search through the supported data-source connection experience rather than manually assembling an unsupported endpoint/key combination. Administrators should grant the service principal only the permissions needed for query operations, protect its credentials, and maintain separate configuration per environment. Testing should confirm that the intended index—not another index in the same service—is queried, that unauthorized content is excluded, and that policy responses cite material that actually supports the generated guidance. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources > Connect to Azure AI Search.

===============

Prevent most builders from modifying shared assets → Share the component collection while controlling edit access; Reuse components without copying → Create a component collection and move the shared components into it; Limit use to the intended primary agent → Restrict the component collection to the primary agent.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A component collection is the correct reusable unit for the escalation topics, MCP definitions, and safety disclaimer. Moving those assets into one collection creates a maintained source that multiple agents can consume without copying and later diverging. Sharing the collection with teammates while controlling edit access separates use permission from modification permission, allowing agent authors to reference the assets while reserving changes for platform engineering. If a sensitive or tightly coupled collection must be usable only by one designated primary agent, the collection can be restricted accordingly. Exporting the primary agent and copying its components would recreate the duplication problem that Fabrikam is trying to eliminate, while restricting every collection to the primary agent would prevent the required cross-agent reuse. The collection should be versioned and tested after changes because a shared update can affect several consumers. Ownership, review, and release responsibilities should also be documented so that reuse does not become an uncontrolled dependency. This design provides consistency, centralized governance, and a smaller maintenance surface across the three agents. Study Guide alignment: Plan and configure agent solutions > Plan an agent solution > Plan reusable agent components.

===============

Requirement

Correct configuration

Make connector actions available for the agent to invoke.

Add the connector as a tool in the agent.

Handle authentication at the service level, not per user.

Create or reuse a connection for the connector.

Pass conversation context into the connector when called.

Map topic variables to the tool inputs.

Surface the connector’s returned data to the user.

Parse the JSON response and assign it to a topic variable.

Comprehensive and Detailed Explanation From [Microsoft AB-620 Study Guide]

Adding the approved connector as an agent tool exposes its defined REST operations to Copilot Studio. The tool can then be called explicitly from a topic or selected dynamically by generative orchestration, depending on its configuration.

A connector connection stores the authentication configuration required to call the underlying service. Among the provided choices, creating or reusing that connection is the correct service-authentication action. For strict service-level authentication, the tool must additionally be configured under Credentials to use with Maker-provided credentials . Creating a connection alone does not guarantee this behavior if the tool remains configured to use end-user credentials.

Topic variables containing conversation context—such as a customer identifier, ticket number, or requested operation—are mapped to the connector tool’s input parameters. This ensures the REST request receives values collected earlier in the conversation.

When the connector returns structured JSON, the relevant values must be parsed and stored in a topic variable. That variable can then be referenced in a message, adaptive card, or subsequent topic node to present the returned information to the user.

Relevant study-guide area: Integrate and extend agents in Copilot Studio → Add tools to agents → Add a tool by using an existing custom connector . See Use connectors in Copilot Studio agents and Add tools to custom agents .

Controlled trigger → Execute the evaluation on demand; Acceptance criteria → Compare responses against defined expectations; Consistent repeated inputs → Use a curated prompt list as the interaction source.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: An on-demand evaluation gives the team explicit control over when the test is executed, which is appropriate before widening access or immediately after a meaningful change. Defined expectations convert the business acceptance criteria into measurable pass/fail or score-based judgments instead of relying on informal review. A curated prompt list supplies the same input cases for each run, eliminating variation that would arise from live user conversations. Scheduling an evaluation is useful for continuous monitoring but would not meet the stated requirement that the team trigger it directly. Live conversations are valuable for discovering new cases, yet they are not a stable regression set because their content and distribution change over time. The curated set should cover knowledge retrieval, tool use, safety boundaries, authentication-dependent behavior, and common failure paths. Expected answers and expected resources should be specific enough to identify regressions without penalizing valid paraphrases. Once the evaluation is run, the team should inspect both aggregate scores and individual activity details before deciding whether the agent is ready for broader use. Study Guide alignment: Test and manage agents > Evaluate agent performance > Create a test set; Choose an evaluation method.

===============

Current Dataverse balance → Connect to a Power Platform connector; Real-time Dynamics 365 shipping status → Connect to a Power Platform connector; Static PDF policy content → Upload the file to the agent ' s knowledge; Welcome message independent of enterprise data → Create a manual response in the topic.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The retrieval pattern should match the volatility and purpose of each source. Customer balances and shipping status are operational values that can change during the day, so the agent should query the systems through Power Platform connectors at runtime rather than rely on a static copy. The connector connection also preserves the applicable authentication and source-system controls. A fixed PDF policy is unstructured reference material; uploading it as agent knowledge allows generative retrieval over its contents without building a transactional integration. The welcome message is deterministic presentation text and does not require any enterprise lookup, so a manual message in the topic is simpler and more reliable than a generative call. A generative answer without enterprise data would be inappropriate for balances or shipping status because it has no authoritative current value. This separation limits latency and security exposure, keeps dynamic information live, and uses knowledge grounding only where retrieval is actually needed. Each connector should be described precisely and tested under the intended user identity to ensure the returned records respect access permissions. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources; Add tools to agents.

===============

HTTP action → Endpoint and authentication; Data action → Table relationships and keys.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: An HTTP action must know where to send the request and how the destination authenticates it. The endpoint, method, headers, and authentication or connection details therefore belong to the HTTP action ' s configuration. A data action operates against structured records, so table relationships and key fields determine which entity and row are read or changed and how related data is resolved. Input mapping is important for both action types but does not replace these defining settings. Timeout and retry policy control resilience after an action has been configured; they do not identify the endpoint or the record relationship. The flow designer should also validate schemas, map outputs into clearly typed variables, and provide failure paths for authorization, not-found, timeout, and malformed-response conditions. Keys should be stable identifiers rather than display names, and connection permissions should follow least privilege. Testing with both valid and invalid records confirms that the data action targets the intended row and that the HTTP action cannot silently call an incorrect or unauthenticated endpoint. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Configure actions and connectors.

===============

Use the user ' s message → Select Activity.Text as the input; Query only designated data → Turn on Search only selected sources and choose the approved sources; Restrict to enterprise data → Turn off Allow the AI to use its own general knowledge.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Activity.Text is the system variable containing the current user ' s utterance, so it is the appropriate query input for the generative answers node. Search only selected sources changes the node from the default broad agent-level search to an explicit source set for that topic. Turning off the option that permits the model to use its own general knowledge closes the ungrounded fallback path and ensures the response depends on approved enterprise content. Generative orchestration at the agent level does not itself guarantee that this particular node searches only designated sources. The selected sources replace, rather than supplement, the agent-level list for the node, and there is no automatic fallback to other knowledge if they return no answer. That behavior is desirable for strict policy boundaries but should be reflected in a clear no-answer or escalation response. Testing should inspect source use, verify authorization trimming under different users, and include questions for which the approved source contains no relevant material to ensure the agent does not invent an answer. Study Guide alignment: Plan and configure agent solutions > Configure topics > Configure generative answers node.

===============