Summary
In this module, you learn how a custom, code-first agent moves from working in isolation to operating as part of a connected set of agents and applications. All of them reflect the same live business data. Using the equipment-provisioning scenario, you trace a supplied Microsoft Foundry agent as it reaches governed Dataverse data and connects to an existing Microsoft Copilot Studio agent. It then becomes something application code can consume directly.
What you learned
- Microsoft Power Platform Model Context Protocol (MCP) servers, including the Dataverse MCP server, give a code-first agent a standard, permission-scoped way to read and write Dataverse data. No custom integration code is needed for each data source.
- Work IQ is a broader, centrally governed intelligence layer with usage-based billing. It's worth evaluating when an agent needs to reason across Dataverse data and Microsoft 365 productivity data together, rather than Dataverse data alone.
- The Microsoft 365 Agents SDK agent connection (preview) attaches a code-first agent to an existing Copilot Studio agent as a callable child agent. That's distinct from the Agent2Agent (A2A) protocol, which fits a different category of natively A2A-enabled agents.
- The Copilot Studio client library, part of the Microsoft 365 Agents SDK, is the one supported mechanism for application code to consume a Copilot Studio agent directly. That application code might be the agent's own code or a separate web or native app.
By connecting these pieces, you can take a supplied custom agent and integrate it with live Power Platform data. You can also integrate it with the Copilot Studio agents and applications your organization already runs, instead of treating each as a separate, disconnected system.