What If Your Employees Only Needed One Agent? Multi-Agent Orchestration in Copilot Studio
Multi-agent orchestration in Copilot Studio lets one main agent route each question to the right specialist agent. Here is how to build one, step by step.
MICROSOFT COPILOT STUDIOAI AGENTSMULTI-AGENT
6/13/20255 min read
Why Multi-Agent Orchestration Matters for Your Business
Once a company starts building agents, they multiply quickly. One answers IT questions, another handles HR benefits, a third books time off. Each one is useful on its own, but employees now have to know which agent to ask, and when two of them overlap, they guess. That is agent sprawl, and it puts the work of choosing on the people the agents were supposed to help.
Multi-agent orchestration fixes that by treating agents like a team of subject matter experts. Each agent stays focused on what it knows best, and one main agent sits in front of them all. Employees ask the main agent anything, and it decides which specialist should answer. Nobody needs to remember which agent does what.
This post walks through how it works in Microsoft Copilot Studio and builds one main agent that replaces three.
Watch the Full Walkthrough First
The video explains the concepts with a few slides, then builds the main agent from scratch and tests it in Copilot Studio and Teams. It is worth watching first to see the routing happen live.
How Multi-Agent Orchestration Works
In Copilot Studio, an agent can now call other agents the same way it calls its own tools and knowledge. The main agent reads each request, picks the agent best suited to it, passes the conversation along, and returns the answer. There are two ways to add agents to a main agent:
Child agents: lightweight agents built inside the main agent. They share its settings and are managed with it
Connected agents: separate, full agents that the main agent calls. They keep their own settings, sign-in connections, and publishing, so they can still be used on their own
Connected agents can be other Copilot Studio agents in the same environment, or agents built elsewhere and reached through the open agent-to-agent (A2A) protocol. Connections to Microsoft Foundry agents, Microsoft Fabric data agents, and agents built with the Microsoft 365 Agents SDK are available in preview. When the video was recorded in June 2025, the whole feature was in preview. Connecting Copilot Studio agents is now part of the standard product.
Child Agents or Connected Agents?
Microsoft's guidance comes down to who owns the agents and whether they need to stand alone.
Use child agents when one person or a small team owns the whole solution, the pieces do not need their own settings or sign-in, and nobody needs to use them separately
Use connected agents when different teams own different agents, each needs its own settings (such as the model it uses), or the same agent should serve more than one main agent
Consider splitting into connected agents when one agent starts choosing the wrong tool. Microsoft's rule of thumb is that this can begin once an agent has more than 30 to 40 tools, topics, and agents to choose from
You can mix both. The build below uses connected agents, because each specialist already exists and is used on its own.
The Example: One Agent in Front of Three
The demo starts with three agents that each do one job:
A Teams technical helper that answers questions from the Teams admin guide, such as Teams Phone licensing or call queues
An HR benefits helper that answers from benefits documents in a SharePoint site, such as medical coverage, vacation policy, and 401(k)
A vacation agent connected to ServiceNow that checks balances and books time off
Each works well, and each is one more thing for employees to keep track of. The goal is a single main agent that knows about all three and picks the right one every time.
How to Build the Main Agent
Create the agent
In Copilot Studio, select Create, then New agent, and go straight to the full configuration
Give it a name and an icon. The video calls it Master Agent
Add a short description, such as "This agent knows about three other agents." The description helps people understand the agent. The instructions are what control it
Connect the specialist agents
Open the Agents section and choose to add an agent. You can create a child agent here, but for this build, connect an existing agent and choose Copilot Studio
Select the first agent. Its details and description fill in automatically, and the conversation history is passed along by default
Add it, then repeat for the other two
Write the instructions
The video keeps them deliberately simple: "You are aware of three other agents, and based on the input you receive, you decide which agent to engage."
If routing needs help, type a slash in the instructions to reference a specific agent, for example "Use this agent when you get questions about time off," followed by the vacation agent
Test in Copilot Studio
Ask one question per specialist and watch which agent the main agent engages
The first time an agent with a connection runs, such as the ServiceNow one, you are asked to sign in. Complete the connection and ask again
Publish and share it in Teams
Publish the agent, then add the Teams and Microsoft 365 channel
Update the display details and icon, then copy the link from Availability options and share it. Anyone who opens it can add the agent in Teams
Save often along the way. Copilot Studio autosaves, but saving yourself avoids losing a change.
What Happened in Testing
With only those two sentences of instructions, the main agent routed every question correctly:
A question about the license Teams Phone requires went to the Teams technical helper
A question about 401(k) benefits went to the HR benefits helper, which searched its SharePoint documents and answered from the right one
A question about a colleague's vacation balance went to the vacation agent, which looked it up in ServiceNow
In Teams, a request to book 20 hours of vacation went through the vacation agent, and the ServiceNow record updated a moment later
With the main agent working, the three separate agents could be removed from Teams. Employees keep one agent, and the specialists keep doing their jobs behind it.
Plan Before You Connect Everything
Routing like this works because each specialist has a clear job. A few things decide whether it stays that way as you add more agents:
Write clear, distinct names and descriptions. The main agent chooses based on them, so two agents with similar descriptions will confuse it
Expect a little extra wait. Each handoff adds a step, because the connected agent runs its own reasoning before answering
Plan for one level. An agent that already has connected agents cannot itself be connected to another main agent, though a simple agent can serve several main agents
Keep each agent's permissions in place. A connected agent uses its own connections and respects its own access, which is one reason to keep sensitive work, like HR or payroll, in its own agent
Test routing as you grow. Keep a short list of sample questions for each specialist and rerun it whenever you add or change an agent
This is where most of the real work sits for a business: deciding which agents should exist, who owns each one, and how they hand off. The build itself is the easy part.
Where to Take It Next
Start with the agents people already use, put one main agent in front of them, and retire the rest from your users' view. Once that works, new specialists can join the team without anyone learning a new agent. For an example of a specialist agent built for one job, see our HR automation agent in Copilot Studio. Which of your agents would make the first team?
Have a question or an idea for a future video? Leave a comment on the full video walkthrough on the Collaboration Simplified YouTube channel.
Contact Us
Questions? Reach out anytime.
Phone
© 2020–Present Collaboration Simplified. All rights reserved.
Collaboration Simplified® is a registered trademark of Shervin Shaffie.