This post is a part of the AB-620: Designing and Building Integrated AI Agent Solutions in Copilot Studio Exam Prep Hub.
This topic falls under these sections:
Integrate and extend agents in Copilot Studio (40–45%)
   --> Configure multi-agent collaboration from Copilot Studio
      --> Design multi-agent solutions in Copilot Studio

Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.

Learning Objectives

After completing this article, you should be able to:

• Understand what a multi-agent solution is.
• Explain why organizations use multiple AI agents.
• Identify the major components of a multi-agent architecture.
• Differentiate between parent agents, child agents, and connected agents.
• Design effective agent responsibilities.
• Select appropriate routing and orchestration strategies.
• Apply Microsoft-recommended design principles for enterprise AI solutions.

Introduction

As organizations adopt AI across multiple business functions, a single AI agent often becomes insufficient for handling every task. Large enterprises require AI systems capable of managing specialized workloads, integrating with diverse systems, and scaling independently.

Microsoft Copilot Studio addresses this challenge by enabling developers to create multi-agent solutions, where multiple specialized agents collaborate to solve complex business problems.

Rather than building one large, monolithic agent responsible for every interaction, developers can create multiple focused agents that communicate and cooperate while maintaining clear responsibilities.

This modular approach improves scalability, maintainability, security, and user experience.

What Is a Multi-Agent Solution?

A multi-agent solution consists of two or more AI agents working together toward a shared objective.

Each agent specializes in a particular domain or capability.

Example:

Instead of one agent handling everything, an organization creates:

• HR Agent
• IT Help Desk Agent
• Finance Agent
• Facilities Agent
• Sales Agent
• Customer Service Agent

Each agent focuses on its own area of expertise.

When necessary, agents collaborate to complete broader workflows.

Why Use Multiple Agents?

Multi-agent systems provide several advantages over a single large agent.

Benefits include:

Better Specialization

Each agent becomes an expert in a limited business domain.

Example:

Rather than one agent answering every possible company question,

Create:

• Benefits Agent
• Payroll Agent
• Recruiting Agent

Each delivers more accurate responses.

Easier Maintenance

Updating one specialized agent is easier than modifying a massive all-purpose agent.

Benefits include:

• fewer unintended side effects
• simpler testing
• faster deployments
• independent versioning

Improved Scalability

Different agents can scale independently.

For example:

Customer Support Agent

• thousands of daily requests

Finance Approval Agent

• dozens of daily requests

Each can be optimized separately.

Better Security

Different agents can have different permissions.

Example:

Payroll Agent

Access:

• salary information
• tax records

Sales Agent

Access:

• CRM data

The Sales Agent never needs payroll permissions.

Improved Reliability

If one specialized agent becomes unavailable,

Other agents continue operating.

This improves overall system resilience.

Multi-Agent Terminology

Understanding Microsoft’s terminology is essential for the AB-620 exam.

Core Components of a Multi-Agent Solution

Most enterprise architectures include several components.

User

Starts the conversation.

↓

Parent Agent

Receives the request.

↓

Decision Logic

Determines which specialized agent should handle the task.

↓

Specialized Agent

Executes the requested task.

↓

External Systems

• Databases
• APIs
• Microsoft 365
• Power Platform
• Azure AI Search
• ERP systems
• CRM systems

↓

Response Returned

Results flow back through the parent agent to the user.

Designing Specialized Agents

One of Microsoft’s primary recommendations is:

Design agents around business capabilities—not technologies.

Poor design:

One “Super Agent”

Responsibilities:

• HR
• Finance
• Sales
• IT
• Marketing
• Legal
• Procurement

Problems:

• difficult to maintain
• confusing prompts
• unnecessary permissions
• reduced accuracy

Better design:

HR Agent

Handles:

• benefits
• vacation
• onboarding

Finance Agent

Handles:

• invoices
• budgets
• expense reports

IT Agent

Handles:

• password resets
• devices
• software
• support tickets

Each agent remains focused.

Agent Responsibilities

Every agent should have clearly defined responsibilities.

Good responsibilities are:

• specific
• measurable
• independent
• reusable

Example

Travel Agent

Responsibilities:

✓ Book flights

✓ Reserve hotels

✓ Check travel policies

Not responsible for:

✗ Payroll

✗ IT tickets

✗ Customer support

Designing Agent Boundaries

One common exam objective is identifying proper agent boundaries.

Ask:

What business capability owns this task?

Not:

Which department requested it?

Example

Employee requests:

“I need a laptop.”

Poor routing:

HR Agent

Better routing:

IT Agent

Reason:

Hardware provisioning belongs to IT.

Parent Agents

The parent agent serves as the coordinator.

Responsibilities include:

• understanding requests
• selecting child agents
• maintaining conversation flow
• combining responses
• returning final answers

Think of the parent agent as a project manager.

Child Agents

Child agents perform specialized work delegated by the parent agent.

Examples include:

Benefits Agent

Inventory Agent

Legal Agent

Facilities Agent

Payroll Agent

Each performs work without needing knowledge of the broader conversation.

Connected Agents

Connected agents differ slightly from child agents.

Connected agents are:

• independently published
• reusable
• discoverable
• callable by other agents

This promotes reuse across multiple solutions.

Example

Company has:

Expense Agent

Multiple departments can connect to it:

• HR
• Sales
• Finance
• Operations

Rather than creating duplicate expense logic.

Choosing Between Child and Connected Agents

Orchestration

Orchestration is the process of coordinating multiple agents.

The parent agent determines:

• who performs work
• when work begins
• what data is shared
• how results are combined

Without orchestration:

Agents work independently.

With orchestration:

Agents collaborate toward one goal.

Collaboration Patterns

Several collaboration models are common.

Sequential Collaboration

Agent A

↓

Agent B

↓

Agent C

Example

Travel request

↓

Policy Agent

↓

Booking Agent

↓

Approval Agent

Parallel Collaboration

Multiple agents execute simultaneously.

          Parent
        /    |    \
      HR   IT   Finance
        \    |    /
         Combined Response

Advantages:

• faster responses
• independent execution

Hub-and-Spoke

Most common in Copilot Studio.

           Parent
        /   |   |   \
      HR   IT Finance Legal

Benefits:

• centralized coordination
• simple routing
• easy governance

Mesh Collaboration

Agents communicate directly.

Agent A ↔ Agent B
 ↕          ↕
Agent C ↔ Agent D

More flexible

More complex

Less common than hub-and-spoke in enterprise Copilot Studio solutions.

Routing Strategies

One of the parent agent’s primary responsibilities is routing requests.

Examples include:

Intent-Based Routing

Determine user intent.

Example:

“I forgot my password.”

↓

IT Agent

Keyword Routing

Specific words trigger agents.

“Payroll”

↓

Payroll Agent

Simple but less flexible than intent recognition.

Rule-Based Routing

Business rules determine routing.

Example:

If request concerns invoices

↓

Finance Agent

Else

↓

Customer Service Agent

AI-Based Routing

The LLM evaluates the request and selects the most appropriate agent based on semantic understanding.

Benefits:

• greater flexibility
• better handling of ambiguous language
• improved user experience

AI-based routing is increasingly preferred for enterprise conversational systems.

Enterprise Example

A user asks:

“I’m traveling to Seattle next week. Can you book my hotel, verify my travel policy, and submit the request for approval?”

Possible orchestration flow:

1. Parent Agent receives the request.
2. Policy Agent verifies travel rules.
3. Booking Agent searches for available hotels.
4. Approval Agent creates an approval request.
5. Parent Agent consolidates the results.
6. User receives a single, coherent response.

This illustrates how multiple specialized agents collaborate to complete a complex workflow while each remains focused on its own domain.

Best Practices

• Design agents around business capabilities rather than departments.
• Keep each agent focused on a well-defined responsibility.
• Minimize overlapping responsibilities between agents.
• Use parent agents to coordinate complex workflows.
• Reuse connected agents whenever practical.
• Prefer AI-based routing for complex conversational experiences.
• Apply the principle of least privilege so each agent has only the permissions it requires.
• Plan for scalability by allowing agents to evolve independently.

Common Design Mistakes

Avoid these common pitfalls:

• Creating one “super agent” responsible for every task.
• Giving multiple agents overlapping responsibilities.
• Granting excessive permissions to specialized agents.
• Routing requests solely by keywords when semantic routing is more appropriate.
• Tightly coupling agents that should be reusable.
• Failing to define clear ownership for business capabilities.

AB-620 Exam Tips

For the exam, remember these key concepts:

• A multi-agent solution consists of multiple specialized agents working together.
• Parent agents coordinate conversations and delegate work.
• Child agents perform specialized tasks within a solution.
• Connected agents are independently published and reusable across multiple solutions.
• Orchestration manages how agents collaborate to fulfill user requests.
• Design agents around business capabilities, not organizational departments.
• Use AI-based routing when requests are complex or ambiguous.
• Keep agents modular, secure, maintainable, and independently scalable.

Advanced Multi-Agent Design Patterns

Once you understand the fundamentals of multi-agent solutions, the next step is learning how to design enterprise-grade architectures. Microsoft expects AI Agent Builders to select appropriate collaboration patterns based on business requirements rather than attempting to solve every problem with a single architecture.

Pattern 1 – Hub-and-Spoke (Recommended)

This is the most common architecture used in Copilot Studio.

                  User
                   │
            Parent Agent
      ┌────────┼────────┐
      │        │        │
   HR Agent IT Agent Finance Agent
      │        │        │
      └────────┼────────┘
          Consolidated Response

Advantages

• Centralized orchestration
• Easy governance
• Simplified security
• Easy monitoring
• Scalable
• Easy to troubleshoot

Typical Uses

• Enterprise copilots
• Employee self-service
• Customer support
• IT service desks

Pattern 2 – Sequential Workflow

Each agent performs one step before passing work to the next.

Example

User
↓
Travel Agent
↓
Policy Agent
↓
Approval Agent
↓
Booking Agent
↓
User

Best for

• Approval workflows
• Procurement
• Employee onboarding
• Case management

Pattern 3 – Parallel Processing

Several agents work simultaneously.

               Parent Agent
             /      |      \
         Sales   Inventory  Shipping
             \      |      /
          Combined Response

Benefits

• Faster responses
• Independent processing
• Better user experience

Pattern 4 – Federated Agent Architecture

Different business units own their own agents.

Example

Sales Department

↓

Owns Sales Agent

Finance Department

↓

Owns Finance Agent

HR Department

↓

Owns HR Agent

A parent agent coordinates requests without requiring centralized ownership of every specialized agent.

Agent Communication Lifecycle

Most multi-agent conversations follow this sequence:

Step 1

User submits request.

↓

Step 2

Parent agent interprets intent.

↓

Step 3

Appropriate specialized agent is selected.

↓

Step 4

Context is transferred.

↓

Step 5

Specialized agent completes work.

↓

Step 6

Result returns to parent.

↓

Step 7

Parent formats final response.

Context Sharing

Context refers to the information needed for another agent to complete work.

Examples include:

• User identity
• Previous conversation
• Variables
• Business data
• Parameters
• Selected products
• Order numbers

Good context sharing reduces duplicate questions and improves user experience.

Example

Without context:

Parent Agent:

“What order number?”

↓

Inventory Agent:

“What order number?”

↓

Shipping Agent:

“What order number?”

Poor experience.

Better

Parent collects:

Order #14567

Passes it automatically to downstream agents.

State Management

State represents information preserved during a conversation.

Examples include:

• Customer ID
• Shopping cart
• Selected location
• Previous answers
• Authentication status

Good state management allows conversations to continue naturally.

Example

User:

“I’d like to change my reservation.”

Five minutes later:

“Can you move it to next Tuesday?”

The agent remembers the reservation discussed earlier.

Stateless vs. Stateful Design

Copilot Studio frequently combines both approaches depending on the scenario.

Security Considerations

Every agent should follow the principle of least privilege.

Example

Benefits Agent

Access

✓ Benefits database

✗ Payroll database

✗ Financial records

Finance Agent

Access

✓ Expense reports

✓ Budgets

✗ HR records

This reduces risk and improves compliance.

Authentication

Each specialized agent may authenticate independently.

Possible methods include:

• Microsoft Entra ID
• OAuth 2.0
• Managed identities
• API Keys (when appropriate)

The parent agent should not automatically inherit unrestricted access to every connected system.

Performance Considerations

Large organizations may operate dozens or even hundreds of specialized agents.

Performance can be improved by:

• Running independent agents in parallel
• Caching frequently accessed information
• Reusing connected agents
• Avoiding unnecessary delegations
• Limiting context passed between agents
• Reducing repeated API calls

Scalability

A good architecture should support future growth.

Instead of:

Parent
↓
One giant agent

Use:

Parent
↓
HR
Finance
Sales
Legal
IT
Marketing
Facilities
Travel
Procurement

New business capabilities can be added without redesigning the entire solution.

Monitoring Multi-Agent Solutions

Enterprise deployments should monitor:

• Conversation success rate
• Agent selection accuracy
• API failures
• Response times
• Authentication failures
• Delegation failures
• User satisfaction
• Tool execution success
• Token usage
• Error frequency

Monitoring enables continuous improvement and faster troubleshooting.

Troubleshooting Collaboration Issues

Common issues include:

Incorrect Routing

Symptoms

• Wrong agent selected
• Irrelevant responses

Solution

Improve routing logic or intent recognition.

Missing Context

Symptoms

• Users repeatedly answer the same questions.

Solution

Share required variables between agents.

Permission Errors

Symptoms

• Agent cannot access required resources.

Solution

Review security roles and connector permissions.

Delegation Loops

Symptoms

Agent A

↓

Agent B

↓

Agent A

↓

Agent B

Avoid circular delegation by defining clear ownership and termination conditions.

Slow Performance

Causes

• Too many API calls
• Excessive context transfer
• Sequential execution when parallel processing is possible

Single-Agent vs. Multi-Agent Architecture

Real-World Enterprise Scenario 1

A global manufacturing company deploys:

• HR Agent
• Payroll Agent
• IT Agent
• Procurement Agent
• Maintenance Agent

The Enterprise Copilot receives:

“Order a replacement laptop for my new employee.”

Possible workflow:

1. Parent Agent identifies onboarding request.
2. HR Agent confirms employee status.
3. Procurement Agent verifies available hardware.
4. IT Agent creates deployment ticket.
5. Parent Agent summarizes results.

No single specialized agent performs every task.

Real-World Enterprise Scenario 2

Customer asks:

“My shipment is late and I’d like a refund.”

Workflow:

Parent Agent

↓

Order Agent

↓

Shipping Agent

↓

Finance Agent

↓

Customer Support Agent

↓

Response returned

Each agent performs one specialized responsibility.

Design Decision Matrix

Summary

For the AB-620 exam, remember these key points:

• Multi-agent solutions improve scalability, maintainability, and specialization.
• Parent agents orchestrate work across specialized agents.
• Child agents perform delegated tasks within a solution.
• Connected agents are reusable across multiple solutions.
• Effective context sharing minimizes repeated user input.
• State management enables natural, continuous conversations.
• Security should follow the principle of least privilege.
• Parallel execution can improve performance.
• Monitoring and troubleshooting are essential for production deployments.
• Select an architecture that aligns with business requirements rather than forcing a single design pattern.

Practice Exam Questions

Question 1

A company wants a Copilot solution where HR, Finance, and IT each maintain their own specialized agents while a single enterprise assistant coordinates user requests. Which architecture is most appropriate?

A. Hub-and-spoke multi-agent architecture

B. Single-agent architecture

C. Stateless REST API architecture

D. Batch processing architecture

Answer: A

Explanation: A hub-and-spoke architecture uses a parent agent to coordinate specialized agents, making it ideal for enterprise scenarios where multiple business domains are involved.

Question 2

What is the primary responsibility of a parent agent in a multi-agent solution?

A. Store all enterprise data

B. Replace every specialized agent

C. Orchestrate conversations and delegate work

D. Authenticate every external API directly

Answer: C

Explanation: The parent agent coordinates conversations, selects the appropriate specialized agent, manages context, and returns a unified response.

Question 3

Which design principle helps reduce unnecessary security risks in multi-agent solutions?

A. Shared administrator permissions

B. Principle of least privilege

C. Universal read/write access

D. Anonymous authentication

Answer: B

Explanation: Granting each agent only the permissions it requires minimizes the attack surface and aligns with Microsoft’s security recommendations.

Question 4

A company wants multiple departments to reuse the same Expense Approval agent without duplicating its logic. Which type of agent is most appropriate?

A. Parent agent

B. Temporary agent

C. Stateless agent

D. Connected agent

Answer: D

Explanation: Connected agents are independently published and reusable across multiple solutions or departments.

Question 5

Why is context sharing important between collaborating agents?

A. It encrypts API traffic automatically.

B. It eliminates authentication requirements.

C. It prevents users from repeatedly providing the same information.

D. It replaces business rules.

Answer: C

Explanation: Sharing relevant context improves efficiency and provides a smoother conversational experience.

Question 6

Which collaboration pattern is generally the best choice when several independent tasks can be completed simultaneously?

A. Parallel processing

B. Sequential workflow

C. Single-agent routing

D. Manual delegation

Answer: A

Explanation: Parallel processing reduces overall response time by allowing multiple specialized agents to work concurrently.

Question 7

A conversation requires remembering a reservation number while multiple agents collaborate. Which capability is most important?

A. Stateless routing

B. Keyword matching

C. State management

D. Anonymous access

Answer: C

Explanation: State management preserves important conversation data across interactions and between collaborating agents.

Question 8

Which issue is most likely to occur if agent responsibilities overlap significantly?

A. Improved specialization

B. Easier maintenance

C. Lower API costs

D. Incorrect routing and duplicated functionality

Answer: D

Explanation: Overlapping responsibilities create ambiguity, increase maintenance complexity, and may cause requests to be routed incorrectly.

Question 9

What is the primary advantage of designing specialized agents around business capabilities instead of departments?

A. Reduced conversation quality

B. Clear ownership and easier long-term maintenance

C. Elimination of authentication

D. Guaranteed parallel execution

Answer: B

Explanation: Business capability–based design creates well-defined responsibilities, improving maintainability, scalability, and reuse.

Question 10

A global organization expects to add new AI capabilities every few months. Which architectural characteristic best supports future growth?

A. One large monolithic agent

B. Hard-coded routing rules only

C. Modular multi-agent architecture with independently scalable agents

D. Manual agent switching by users

Answer: C

Explanation: A modular multi-agent architecture allows organizations to add or update specialized agents independently without redesigning the entire solution, making it the preferred enterprise approach.

Go to the AB-620 Exam Prep Hub main page