Configure agent orchestration in Microsoft 365 Copilot

Agent orchestration lets admins configure Microsoft 365 Copilot to route specific user prompts to a selected agent. This helps users get authoritative answers and workflows for scenarios where a specialized agent is the best source of information, such as HR, workplace policy, or other organization specific topics.

When a user submits a prompt that matches an admin defined rule, Copilot routes that to an assigned agent in the same conversation. The response is shown as coming from the agent, and users can return to Copilot if they don't want to continue with the assigned agent.

Before you begin

Before you configure agent orchestration, make sure that:

• You're assigned the AI Administrator role in the Microsoft 365 admin center.
• The agent that you want to route users to is available in your organization.
• You have identified the prompts that should consistently route to an authoritative agent.

Important

Users are routed to an agent only if that agent is installed for them.

How agent orchestration works

With agent orchestration, you create rules that pair a user prompt with an assigned agent.

For each rule:

• You enter the exact prompt that should trigger orchestration.
• You select the agent that should handle that prompt.
• You set the rule status to Active or Disabled.

When a user's prompt matches an active rule, Microsoft 365 Copilot routes the user to the assigned agent. After orchestration:

• The agent responds in the same conversation.
• The experience indicates that the response came from the agent.
• The experience indicates that the orchestration happened because of admin configuration.
• The agent remains selected until the user exits the agent.
• If the user chooses to leave the agent experience, Copilot removes the agent from the conversation and returns the user to mainline Copilot.

Turn agent orchestration on or off

In the Microsoft 365 admin center, go to Copilot -> Settings -> Agent orchestration.

• Select the toggle next to Turn on agent orchestration for your organization to turn agent orchestration On or Off.
• Select Save.

If you turn the feature off, existing rules are retained but orchestration doesn't occur until you turn the feature back on.

Create an orchestration rule

In the Microsoft 365 admin center, go to Copilot -> Settings -> View all -> Agent orchestration.

• Make sure Agent orchestration is turned on.
• Select Add rule.
• In Enter a prompt that will invoke the agent, enter the full prompt you want to match.
• In Assign agent, select the agent that should receive the routed prompt.
• Under Status, choose one of the following:
  • Active to enable the rule immediately.
  • Disabled to save the rule without using it.
• Select Add and then Save.

After you save the rule, it appears in the rule list with its prompt, assigned agent, and status.

Edit an orchestration rule

• Go to Copilot -> Settings -> Agent orchestration.
• In the rule list, select the edit icon for the rule you want to update.
• Update the prompt, assigned agent, or status.
• Select Update and then Save.

If you leave the page without saving your changes, your changes are discarded.

Activate, disable, or delete multiple rules

You can select multiple rules and then apply a bulk action.

• Go to Copilot -> Settings -> Agent orchestration.
• Select one or more rules.
• Choose the action you want:
  • Activate
  • Disable
  • Delete
• Select Save.

Use bulk actions when you need to update several rules at the same time.

What users experience when a rule is triggered

When a user submits a prompt that matches an active rule:

• Copilot automatically routes the prompt to the assigned agent.
• The routed turn makes it clear that the response came from the agent rather than mainline Copilot.
• The routed turn indicates that the orchestration was based on admin configuration.
• The routed turn includes an option for the user to exit the experience.
• If the user continues the conversation, the agent remains selected for the next turn until the user removes it.
• If the user exits the agent experience, Copilot returns to mainline Copilot for that conversation. This action doesn't permanently suppress future orchestration. If the same rule still exists and the user later submits the same prompt again, Copilot can route the prompt again.

Feedback and reporting considerations

Agent orchestration is designed to support feedback collection on both the orchestration experience and the resulting agent response.

Depending on your implementation and reporting experience, admins can use this feedback to understand how well configured rules are working and whether users are staying with the agent or exiting back to mainline Copilot.

Examples of useful signals include:

• How often orchestration occurs
• Which agents receive routed prompts
• How often users exit the agent experience
• Satisfaction or dissatisfaction with orchestration
• Satisfaction or dissatisfaction with the agent response

Best practices for writing orchestration rules

Use these recommendations when planning your rules:

• Start with high confidence prompts that clearly map to a single authoritative agent.
• Use prompts for topics where accuracy, policy alignment, or workflow completion is especially important.
• Review rule performance regularly and disable rules that produce poor user outcomes.
• Coordinate with agent owners so routed prompts align with the agent's supported capabilities.
• Roll out a small set of targeted rules first, then expand over time.

Limitations

Keep the following in mind:

• Orchestration is based on defined prompts.
• Users must have the assigned agent installed to be routed.
• Agent orchestration routes users from mainline Copilot to an agent.
• Not every agent scenario or future extensibility capability is included in this release.
• Only 100 rules are supported in either active or disabled state.

Related content

• Overview of Microsoft 365 Copilot