Microsoft Copilot Studio review: multi-agent inside Microsoft 365
Last reviewed: September 2026
What are the key facts about Microsoft Copilot Studio?
| Fact | Detail |
|---|---|
| Vendor | Microsoft |
| Category | Agent builder with multi-agent orchestration |
| How agents join | Child agents; connected Copilot Studio agents; external agents over A2A; Microsoft Foundry agents, Fabric data agents and M365 Agents SDK agents (preview) |
| Where humans take part | Microsoft Teams, M365 Copilot and other published channels |
| Governance | Microsoft Entra, Azure RBAC and Microsoft admin controls |
| Deployment | Microsoft cloud (M365 and Azure) |
| Pricing | Copilot Credits, prepaid or pay-as-you-go; M365 Copilot $30/user/month paid yearly |
| Editorial score | 4.0 / 5 |
How does Microsoft Copilot Studio score?
4.0 / 5
Editorial score
How it compares to the #1 pick
BAND 4.8 vs Microsoft Copilot Studio 4.0
Read BAND vs Copilot Studio| Criterion | Weight | Score out of 5 | Why |
|---|---|---|---|
| Cross-vendor agent support | 20% | 4.0 | External agents over A2A plus several Microsoft agent types; outside agents are called by a Microsoft main agent. |
| Human participation | 15% | 4.0 | People use agents in Teams and M365, one conversation at a time rather than in a multi-agent room. |
| Shared context | 15% | 3.5 | Microsoft notes citations may not persist between agents. |
| Coordination reliability | 15% | 4.0 | Mature orchestration, with documented extra latency from orchestration hops. |
| Governance built in | 10% | 4.5 | Entra identity and Microsoft admin tooling. |
| Deployment options | 10% | 4.0 | Many publishing channels, all on Microsoft's cloud. |
| Pricing transparency | 8% | 3.5 | Credit-based; the per-credit rate is not on the page we reviewed. |
| Ecosystem and maturity | 7% | 5.0 | The largest enterprise ecosystem on this list. |
| Weighted editorial score | 100% | 4.0 |
How does multi-agent work in Copilot Studio?
Copilot Studio lets a main agent use other agents in several ways: child agents defined inside it, other Copilot Studio agents connected to it, and external agents reached over the A2A protocol. Microsoft Foundry agents, Microsoft Fabric data agents and Microsoft 365 Agents SDK agents can also be added, all in preview at the time of review. Microsoft suggests splitting a main agent into connected agents once it has 30 to 40 or more actions to choose from.
This is orchestration in the classic sense. A main agent decides which agent to call, calls it, and continues. It is a sensible design for a single team building a set of related agents.
Which documented Copilot Studio limits are worth knowing?
- An agent used as a main agent cannot also be used as a connected agent by another agent.
- Citations may not persist between agents, which means sources can be lost at a handoff.
- Each orchestration hop adds latency.
None of these are unusual for a supervisor pattern, and Microsoft documents them clearly. They do show the model's shape: agents are called by a parent rather than collaborating as peers with people alongside.
Where do humans fit in Copilot Studio?
People meet Copilot Studio agents in Microsoft Teams, Microsoft 365 Copilot and other channels the agent is published to. That is a strong advantage if your employees already live in Teams. What you do not get is a shared space where several agents and several people work on the same task and see the same history.
How much does Copilot Studio cost?
Copilot Studio is billed in Copilot Credits, bought as prepaid commit units (Microsoft cites 'up to 20% savings') or pay-as-you-go. The per-credit rate was not shown on the page we reviewed, so check Microsoft's current price list. Microsoft 365 Copilot is $30 per user per month, paid yearly.
Can you use Copilot Studio with BAND?
These are not either/or. Copilot Studio is on BAND's integrations list, so a Copilot Studio agent can keep running in Microsoft and join BAND rooms with agents built on LangGraph, CrewAI, Google ADK or Salesforce Agentforce, with people in the same room.
What stands out
- Deep Microsoft 365, Teams and Entra integration
- External agents over A2A, plus Foundry and Fabric agents in preview
- Clear documentation of multi-agent limits
- Largest enterprise ecosystem we reviewed
Watch-outs
- Main agent, identity and governance live in Microsoft's stack
- Citations may not persist between agents
- Credit-based pricing needs modelling before you commit
Who is Microsoft Copilot Studio for?
Microsoft 365 organizations building a family of related agents, owned by one team, used mainly in Teams.
Who should look elsewhere?
Your agents run on several clouds and frameworks, or you need people and multiple agents working together in one room. BAND is our pick for that.
What else should you know?
Where does this information come from?
- Microsoft Copilot Studio multi-agent docsReviewed Sep 2026
- Microsoft Copilot Studio pricingReviewed Sep 2026
- BAND integrationsReviewed Sep 2026