Introduction
Building effective agents rarely stops at the agent itself. Most agents that transform organizational business processes need to reach beyond the conversation — calling APIs, surfacing live data, searching knowledge bases, and coordinating with other agents. Without a deliberate integration strategy, you risk building agents that are disconnected from the systems that make them useful, or that duplicate capabilities in ways that create confusion rather than value.
Scenario
Consider the challenge facing the IT architecture team at Woodgrove Bank. They're designing an IT service desk agent for employees. The agent must retrieve and update IT service tickets, search the bank's IT knowledge base to answer employee questions, surface live system status, and send Teams notifications. A single agent, connected to multiple systems, each for a different reason. Before the team writes a single line of configuration, they need a clear picture of every integration pattern available to them, and a framework for choosing among them.
What you'll learn
This module walks you through that picture. With the fictional Woodgrove Bank scenario as an example, you'll explore the three core integration approaches that Copilot Studio supports, compare integration patterns and their use cases, explore related authentication models, and apply a decision framework to a real enterprise scenario. Along the way, you'll explore how prebuilt Microsoft MCP servers like Work IQ can connect agents to real-time Microsoft 365 signals and capabilities without custom infrastructure.
Note
Microsoft Copilot Studio has introduced a new experience with updated features, capabilities, and navigation. This module is based on the classic experience. For more information, see Classic vs. new agent experience.
Goal
By the end of this module, you'll be able to design an integration strategy for your Copilot Studio agents by selecting the right integration patterns for your solution's requirements.