Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This content is archived and is not being updated. For the latest documentation, go to What's new in Copilot Studio. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | - | 
Mar 17, 2025 |
Business value
Generative orchestration lets your makers focus on managing plugins and maintaining artifacts. Businesses can save time as makers don't need to build agents manually, and users get better responses as agents can more easily answer unanticipated questions from the user.
Feature details
With generative orchestration, your agent can choose the best actions, knowledge, and topics to answer user queries, or respond to event triggers (as opposed to classic orchestration where only one topic can be used to respond to a user, based on manually authored trigger phrases).
When you activate generative orchestration, it mainly relies on the descriptions of actions and topics to determine which elements to use in response to the last user input or event. When enabled, generative orchestration is responsible for orchestrating the conversations users have with your agent, which can help provide users with a more natural and fluid conversation.
The following table compares agent behavior between classic orchestration and generative orchestration.
| Behavior | Classic orchestration | Generative orchestration |
|---|---|---|
| Topics | Topics are selected based on matching a user query with trigger phrases. | Topics are selected based on the description of their purpose. |
| Actions | Actions can only be called explicitly from within a topic. | The agent can choose to call actions based on their name and description. |
| Knowledge | Knowledge can be used as a fallback when no topics match a user's query (or called explicitly from within a topic). | The agent can choose to proactively search knowledge to answer a user's query. |
| Use of multiple topics, actions, knowledge sources | Agent tries to select a single topic to respond to the user, falling back to knowledge if configured. | The agent can use a combination of topics, actions, and knowledge. |
| Asking users for input | You must use question nodes in topics to author messages prompting the user for any required information. | The agent can automatically generate questions to prompt users for any missing information required to fill inputs for topics and actions. |
| Responding to a user | You must use message nodes in topics to author messages responding to the user (or call an action from a topic). | The agent automatically generates a response, using the available information from topics, actions, and knowledge that it used. |
To turn on generative orchestration for your agent, do the following.
- Go to the Overview page for your agent.
- In the Details section, under Orchestration, turn on Use generative AI to determine how best to respond to users and events.
Geographic areas
This feature will be released into the following Microsoft Azure geographic areas:
- Germany
- Switzerland
- United Arab Emirates
- US GCC
- US GCC High
- United States
- Europe
- Asia Pacific
- United Kingdom
- Australia
- Brazil
- Canada
- India
- Japan
- France