Understand agent harnesses
Three parts shape how a Copilot Studio agent works: the agent, the model, and the harness. The agent defines the job, the model reasons over information and generates responses, and the harness coordinates the work.
Distinguish the agent, model, and harness
The agent is the solution you design. Its purpose, instructions, knowledge, tools, and boundaries define what it should accomplish. People interact with the agent to ask questions or request work.
The model generates language and reasons over the information it receives. Models differ in speed, cost, and ability to complete complex work. The model doesn't define the agent's business role or connect itself to organizational systems.
The harness coordinates how the agent uses the model and its available features. It determines:
- When to call the model.
- Which instructions and information to provide.
- How to interpret a model response.
- Which knowledge, tools, and other features the agent can use.
- What the agent should do next.
The model generates a response or decision. The harness manages the larger process around it. As a result, agents that use similar models can behave differently when they use different harnesses.
Understand orchestration
Consider an expense-review agent. It might retrieve a policy, inspect a receipt, compare an amount with a limit, and request approval. Orchestration is how the agent decides which step to take next.
The orchestration options depend on the harness:
- Classic orchestration is available in the standard harness. It matches a request to a topic by using trigger phrases that you define.
- Generative orchestration is also available in the standard harness. It can select topics, tools, knowledge, and other agents based on their descriptions.
- The enhanced orchestration model is used by the Microsoft Copilot harness. It can reason through a multistep goal, plan its work, use available features, and adjust its approach based on results.
In the standard harness, you can choose classic or generative orchestration, subject to your environment's policies. New agents use generative orchestration by default unless their prebuilt configuration or administrator settings specify otherwise. The Microsoft Copilot harness uses the enhanced orchestration model for every agent.
For example, an equipment-return conversation might use classic orchestration to ask the same questions each time. An invoice-review process might use the enhanced orchestration model to compare records, call several tools, and route an exception based on what it finds.
For more information about the standard-harness options, see Orchestrate agent behavior with generative AI.
Treat harness choice as an architecture decision
Your harness choice determines:
- Behavior: How the agent combines defined paths, orchestration, and reasoning to complete its work.
- Task complexity: The length and type of work the agent can complete.
- Features: Whether the agent can use skills, memory, and built-in file operations.
- Authoring: How you configure instructions, features, topics, and branches for the selected harness.
- Publishing: Where the completed agent can be made available.
Define your requirements before you create the agent. Harnesses differ in capabilities, configuration, and billing, so moving to another harness can require you to rebuild or reconfigure parts of the solution and validate its behavior.
Note
A preview upgrade feature creates a Microsoft Copilot harness copy of an existing standard-harness agent rather than changing the original agent in place. Not all configuration carries over, and this preview isn't intended for production use.
For more information, see Choose a harness.
Note
We recognize that different people like to learn in different ways. You can choose to complete this module in video-based format or you can read the content as text and images. The text contains greater detail than the videos, so in some cases you might want to refer to it as supplemental material to the video presentation.