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.
Note
The harness used to build this agent uses usage-based billing. Using, building, testing, and evaluating agents might consume Copilot Credits. Learn more in Overview of usage-based billing.
This article answers common questions about the automation experience in Microsoft Copilot Studio for workflows powered by the GitHub Copilot harness.
What is the workflows experience?
Workflows are the automation experience built in Copilot Studio and powered by the GitHub Copilot harness at production runtime (or during a pre-production test in a controlled environment). You build workflows on a visual canvas, with triggers, connectors, and AI-driven actions such as an agent node, a Copilot node, classify and extract nodes, and more AI-powered nodes. Learn more in Workflows overview.
What's different in the workflow designer compared to agent flows created using the classic experience?
You can perform the following operations in the workflows designer:
- Test a single action or the entire workflow without leaving the designer by using the node-level testing feature.
- Add native AI actions such as the following nodes:
- Agent node: Calls an existing agent or a new agent that you define inline.
- Copilot node: Calls Microsoft Copilot, Cowork and agents like Researcher and Analyst.
- Classify node: Routes free-form text to a branch based on its meaning.
Learn more in Edit and manage your workflow in the designer.
How do agents and workflows work together?
- Your workflow can call an agent: A workflow can hand off a step to an agent through an agent node either by calling an existing published agent, or by defining a new agent inline in the node.
- Your agent can call a workflow: You can add a workflow as a tool to an agent if the workflow has the When an agent calls the flow trigger and a Respond to the agent action.
Learn more in Add a workflow as a tool to an agent.
What happened to agent flows powered by the standard harness? Are they still available?
Agent flows powered by the standard harness remain available. You continue to create and manage them in the classic experience. Learn more in Agent flows overview and FAQ for agent flows.
Can I convert an existing agent flow to the new workflow format?
There's currently no supported way to convert an agent flow powered by the standard harness to a workflow powered by the GitHub Copilot harness. You can convert a Power Automate cloud flow to a Copilot Studio agent flow, but you can't convert a Power Automate cloud flow to a Copilot Studio workflow. Learn more in Convert a Power Automate flow to an agent flow.
How is a workflow powered by the GitHub Copilot harness different from a Power Automate cloud flow?
Workflows in Copilot Studio combine deterministic automation with AI-driven actions, such as agent handoffs and native AI nodes, alongside your agents. Workflows use Copilot Studio capacity and don't need a separate Power Automate license.