Two kinds of automation under one Workflows page
Copilot Studio started with agent flows. Since the arrival of harnesses, there is a second kind called workflows. Both appear on the Workflows page, which is why the terms get mixed up. As of November 2026:
| Agent flows | Workflows | |
|---|---|---|
| Runs on | Standard harness | Microsoft Copilot harness |
| Behaviour | Deterministic: same input, same steps | Steps can reason and act, with human-in-the-loop controls |
| Building | Trigger plus actions: AI capabilities, human in the loop, built-in tools, connectors | Redesigned canvas |
| Testing | Test runs, no capacity used | Testing per node |
| Start | Workflows > More create options > Build with standard orchestration > Agent flows | Workflows > New workflow |
| Credit view | Power Platform admin center | Credit usage (last 30 days) column; classic workflows show N/A |
Use an agent flow when the steps must happen the same way every time: write a record, send an approval, call an API. Use a workflow when a step needs judgment, such as reading a document and deciding what to do with it.
How an agent uses a flow
An agent flow that an agent should call starts with the trigger When an agent calls the flow. The agent can then run it in two ways, which are billed differently:
- From a topic: the maker places the flow in a topic. Billed as 1 classic answer plus the flow’s actions.
- Through generative orchestration: the agent decides itself to call the flow. Billed as 1 autonomous action plus the flow’s actions.
Every action in the flow consumes Copilot Studio capacity. Runs under a user with a Microsoft 365 Copilot license are not affected when credits run out, but autonomous runs are charged and are blocked without credits. Credit prices are on How does Copilot Studio pricing work?.
Bringing an existing Power Automate flow over
Many teams already have Power Automate flows. You can convert one into an agent flow:
- Make sure the flow is inside a solution.
- Change its plan to Copilot Studio.
- Know that this is one-way: the flow can’t go back, and it can’t be converted into the new workflow format.
After conversion it is an agent flow like any other, so each action consumes Copilot Studio capacity.
The common mistake: “the agent will figure out the process”
With generative orchestration it is tempting to describe a process in the instructions and let the agent improvise each step. For anything with consequences, such as a refund, a contract or a record in the ERP, that makes the outcome depend on the model’s reading of the moment. The point of agent flows is the opposite: the agent decides when to act, the flow fixes how. Workflows on the Microsoft Copilot harness sit in between and add testing per node, so you can check the reasoning steps before they run on real data.
What this means for a team
- List the processes an agent should trigger and mark which ones must be deterministic.
- Build those as agent flows, and convert existing Power Automate flows only if you accept that conversion is one-way.
- Use workflows for steps that need reading and judgment, and test them node by node.
- Watch the credit column monthly; autonomous runs are the ones that stop when credits run out.
What a flow does is fixed by its design. What it knows about your team, such as which customer gets which exception, still has to come from somewhere. More on agents in general is in What are Copilot agents?.
Where Bombos fits
Flows make actions repeatable; the knowledge behind the decisions still lives in people’s heads, mail and documents. Bombos is a plugin that gives Copilot, your Studio agents and the other AI tools your team uses (Claude, ChatGPT, Codex, Cursor, your own agents) one shared memory of team knowledge, learned rules, mail and documents, traceable, in the cloud or on your own server. One person can try it first with their own agents.
Related questions
Can I turn a Power Automate flow into an agent flow?
Yes, if the flow is in a solution: change its plan to Copilot Studio. The conversion is one-way, and it can't convert into the new workflow format.
Does testing an agent flow use credits?
No. Microsoft states that testing doesn't consume capacity. Production runs do: each action counts against Copilot Studio capacity.
What happens when the tenant runs out of credits?
Agent flow runs are blocked. Runs under a user with a Microsoft 365 Copilot license are not affected, but autonomous runs are charged and stop.
Where do I see how many credits workflows use?
The Workflows page in Copilot Studio has a Credit usage (last 30 days) column. For agent flows, the Power Platform admin center shows usage under Licensing, Copilot Studio, Agent flow actions.
