MENU
A company requires an agent in Copilot Studio to answer questions using content stored in a third-party knowledge base system and reuse that content for knowledge grounding.
The agent must ground answers using indexed enterprise knowledge from a non-Microsoft system.
You need to choose the correct integration approach.
What should you use?
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A Copilot connector knowledge source is the appropriate integration for indexed enterprise content held in a non-Microsoft system. The connector brings authorized content into the Microsoft Graph search index and makes it available for knowledge grounding, while access controls determine which results a user may receive. Calling the third-party API from a topic on every question is a tool pattern and would require the agent to implement retrieval, ranking, and response handling itself. A Copilot Studio tool is also an executable capability, not automatically a knowledge source, so options B and C do not meet the indexed-grounding requirement. After the tenant administrator configures and synchronizes the connector, the builder adds the corresponding enterprise knowledge source to the agent, supplies clear metadata, and tests retrieval and citations. Content lifecycle, crawl status, schema mapping, and permission trimming must be monitored because a technically successful connection can still return stale, poorly ranked, or overexposed content. The design should avoid uploading a second copy that would drift from the connector-managed index. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources > Connect to Copilot connectors.
===============