Citizen Developer
  • All of Microsoft
  • My Role
    • All in My Role
    • Citizen Developer
  • Focus
    • All in Focus
    • Generative Pages and Apps
    • Microsoft Copilot Studio
    • Copilot Studio - Agent Step-by-Step
    • What's Hot
    • M365 Release
Timespan
explore our new search
Copilot Studio harnesses: choose the right agent runtime
Microsoft Copilot Studio

Copilot Studio harnesses: choose the right agent runtime

by HubSite 365 about Andrew Hess - MySPQuestions

Currently I am sharing my knowledge with the Power Platform, with PowerApps and Power Automate. With over 8 years of experience, I have been learning SharePoint and SharePoint Online

Copilot Studio’s harnesses shape how an agent handles work, from fixed topic paths to multi-step reasoning and customer conversations.

Key insights

  • Standard uses topics and branches for structured, repeatable conversations.
  • Microsoft Copilot is suited to agents that work toward a goal through multi-step reasoning.
  • Copilot chat agents can use skills, knowledge, web search, and attachments.
  • Customer Conversation is designed for customer-facing voice and chat interactions.
  • Standard and Copilot chat use Microsoft 365 Copilot licensing; Microsoft Copilot is consumption-based.

Microsoft Copilot Studio harnesses define how an agent uses context, tools, and instructions to respond or complete work. They matter to makers choosing between predictable, topic-led interactions, tailored Copilot chat, customer-facing voice and chat, or more adaptive multi-step tasks. Andrew Hess - MySPQuestions demonstrates the four harness types with examples and a restaurant analogy.

What's new

A harness is the operating setup around an agent and its model: it helps coordinate how reasoning is put to work. The model does not determine the whole experience on its own. The harness affects how the agent works with instructions, tools, knowledge, and the user’s request.

The four types covered here are Standard, Copilot chat, Microsoft Copilot, and Customer Conversation. Microsoft Copilot was previously called the GitHub Copilot harness. The names can be confusing because Microsoft’s consolidated harness documentation groups the current set as Microsoft Copilot, Customer Conversation, and Standard; Copilot chat is treated separately in earlier product framing.

Think of the harness as a restaurant’s operating setup, rather than its chef. The model provides reasoning, while the harness shapes the context and how work is coordinated. Skills are reusable guidance for particular tasks, used when needed rather than as a substitute for the entire agent setup.

Who it is for and what you need

Copilot Studio makers can choose a harness based on the work the agent must perform. Standard fits conversations where topics, branches, and repeatable steps matter. Microsoft Copilot is aimed at work where the agent needs to pursue a goal and decide how to get there.

Copilot chat is useful for a tailored agent experience grounded in organizational knowledge, such as SharePoint documents. In the demonstration, agents can be created from the Agents area in Microsoft 365 Copilot, in the app or browser. The available capabilities shown include skills, knowledge, web search, and attachments.

Customer Conversation is aimed at customer-facing interactions through voice and chat. It is distinct from an internal, structured topic flow. The demonstration shows a simple restaurant-hours agent responding to a caller; the research describes the harness as public preview. Standard and Copilot chat use Microsoft 365 Copilot licensing, while the Microsoft Copilot harness is consumption-based, so a Copilot license does not remove its consumption costs.

How it works

Use the task, rather than the model, as the starting point for choosing. For a tightly controlled process that should follow the same route each time, Standard’s topic-and-branch approach is a natural fit. For a customer who may speak or chat and need service, consider Customer Conversation. For an agent with a tailored Copilot chat experience, use Copilot chat.

  1. Define the expected outcome. Decide whether the agent should follow a specific sequence or find its own path to a goal.
  2. Choose Standard for predictable paths. Topics route a conversation through defined branches. The demonstration cites HR and legal-style scenarios where a consistent response or process is important.
  3. Choose Microsoft Copilot for adaptive work. Give the agent a goal and instructions about what to do and avoid. It can reason through the task, use tools such as workflows, and continue toward the requested outcome. The example creates an infographic without prescribing every research step.
  4. Choose Copilot chat for a grounded chat agent. Start in Microsoft 365 Copilot’s Agents area, select New agent, and configure the available skills, knowledge, web search, or attachments for the experience.
  5. Choose Customer Conversation for customer interactions. Build an agent for voice or chat service. The example answers opening-hours questions in a spoken conversation.

Existing Standard agents can also be upgraded from the Copilot Studio home page. The upgrade process can review the agent and connected agents, then suggest how to handle topics in the new Microsoft Copilot harness. A topic might be rebuilt as a skill or workflow, so the migration is not necessarily a one-to-one conversion.

Limitations and alternatives

The harnesses are not interchangeable labels for identical behavior. Standard favors defined topics and branches, while Microsoft Copilot lets an agent reason toward a goal. Copilot chat offers a different set of capabilities, and Customer Conversation is aimed at external service interactions. Choose based on the controls and interaction model the task needs.

Migration from Standard requires review because topics may need to become skills or workflows. Check the suggested conversion and test the result rather than assuming the new agent will behave exactly like the original. The demonstration notes that workflows in this harness are not the same as agent flows or Power Automate, even though they have similarities.

Plan for consumption costs when using the Microsoft Copilot harness; the demonstrated infographic task incurred a reported cost of about 50 cents. For Customer Conversation, the short restaurant example establishes a voice interaction but does not demonstrate every customer-service capability. Keep the scenario and any required escalation or authentication behavior in scope when evaluating an agent.

Sources

Frequently asked questions

What is the Standard harness in Copilot Studio?

Standard uses topics and branches to guide structured, repeatable conversations. It is suited to processes where the agent should follow a defined path.

Which Copilot Studio harness supports multi-step reasoning?

The Microsoft Copilot harness is designed for agents that work toward a goal through reasoning and tools. It is consumption-based, including for users who have a Copilot license.

How do I migrate a Standard agent to the Microsoft Copilot harness?

From the Copilot Studio home page, you can ask to upgrade an agent. The process may recommend rebuilding topics as skills or workflows, so the result is not necessarily a one-to-one migration.

What is the Customer Conversation harness for?

It is designed for customer-facing interactions through voice and chat. It is described as public preview.