> For the complete documentation index, see [llms.txt](https://dyns.ntd.asia/power-dynamics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dyns.ntd.asia/power-dynamics/artificial-intelligence/study-copilot-studio/multi-agent-orchestration.md).

# Multi-Agent Orchestration

Group 6 - delegating to another agent instead of building one that does everything: child agents, connected agents, Foundry, MCP-connected tools, A2A, and Fabric data agents.

Every group so far made one agent smarter - better topics, better grounding, better tools, better autonomy. This group asks a different question: when does a second agent, not a smarter first one, become the right answer?

Five sessions: the design patterns and prompting disciplines that keep a multi-agent build from talking over itself (6.1), building the Northwind Billing/Product-Support split those patterns designed (6.2), integrating a Microsoft Foundry agent (6.3), reaching across platforms with the Agent2Agent protocol and Fabric data agents (6.4), and a closing review that wires the group's mechanisms into one working handoff (6.5).