Ground answers from enterprise data → Add a Copilot connector knowledge source for indexed content; Invoke standardized callable functions → Connect to an MCP server and add its tools; Write an authenticated update → Add a Power Platform connector tool and call it from a topic.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: These requirements represent three different integration contracts. Indexed enterprise content is a retrieval problem, so a Copilot connector knowledge source should ground the generated answer in Microsoft Graph-indexed information while honoring the user ' s permissions. Callable functions published through the standardized Model Context Protocol belong behind an MCP server connection; once added, the agent can discover and invoke the server ' s tools. A write operation during a conversation is a transactional tool call. A Power Platform connector action invoked from the topic supplies the authenticated operation and exposes defined inputs and outputs. Dataverse tables can be used as knowledge, but that choice does not satisfy the broader indexed-enterprise requirement stated here. Likewise, using MCP for every requirement would blur read-only grounding and system updates, increasing the security and orchestration surface. Separating knowledge from actions also improves observability: retrieval sources can be evaluated for grounding quality, while tool calls can be audited for inputs, identity, outcome, and errors. Descriptions and parameter metadata should make each capability ' s scope unambiguous to the orchestrator. Study Guide alignment: Integrate and extend agents in Copilot Studio > Connect to enterprise knowledge sources; Add tools to agents.

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