Cloud flows vs agent flows vs Copilot Studio workflows: which one do you use, and who pays?

Let me tell you about Mark's expenses flow.

Mark works in Accounts Payable. In 2022 he built a cloud flow in Power Automate: receipt lands in a SharePoint folder, manager gets an approval card in Teams, approved claims go to the finance system, rejected ones go back with a polite note. It has run every working day since. Nobody thinks about it. That's the highest compliment an automation can receive.

This year, Mark's flow has been renamed twice, relicensed once, and very nearly rebuilt from scratch. Not because anything broke. Because Microsoft gave us three things called flows, and every one of them looked like the right answer for about a month. If you've felt the same confusion, you're in good company. Here's Mark's year, and what it teaches.

March: the demo

A consultant visits. On the screen is an "Expenses Agent". You describe a claim in plain English, it reads the receipt, checks the policy, and approves it or asks a question. The room is impressed. Someone from Finance says "can it do mileage?" and the consultant says "absolutely," which is consultant for "not yet."

Behind the agent is an agent flow. Same designer as Mark's cloud flow, same connectors, same boxes. The difference is where it lives (inside Copilot Studio, as a tool the agent calls) and how it's paid for. Cloud flows need a Power Automate licence. Agent flows are billed on consumption through Copilot credits, no per-user licence at all. The consultant mentions this as a benefit. Keep that word in mind.

April: the conversion

IT converts Mark's cloud flow into an agent flow. There's a setting for it; takes ten seconds. It works beautifully, and for two months the Expenses Agent is the most popular thing in the company since the new coffee machine.

Two things nobody read in the FAQ. First, agent flows can't be copied, shared or co-owned. Mark is now the sole owner of a business-critical process, and Mark has two weeks in Crete booked for August. Second, the conversion is one-way. There is no button that turns an agent flow back into a cloud flow. Microsoft is quite clear about this; it's just not the sort of thing that comes up in a demo.

The bit to remember: you can turn a cloud flow into an agent flow. You cannot turn it back. Convert the ones an agent genuinely needs. Leave the payroll one alone.
 

July: the invoice

Consumption billing is a taxi meter. It's lovely when the journey's short. The Expenses Agent has been so popular that other departments started using it, and then a contractor portal got wired in, and the credit report arrived on the finance director's desk with a number on it nobody had forecast.

Here's the wrinkle. Since late last year, the standard Microsoft 365 Copilot licence includes Copilot Studio for internal, licensed users, so the pilot really was close to free. External-facing use and anything at real volume still burn credits. "Free for the pilot, a line item in production" isn't a trap exactly, but it does reward the organisations that asked Finance how they feel about metered billing before switching it on.

August: the third flow

Just as Mark has made peace with all of this, someone forwards him a link to Copilot Studio Workflows. New canvas, horizontal if you like, built for orchestrating several agents with branching and hand-offs. Also credit-based, also lives inside an agent. In preview since May, and as of the preview, you can't convert an agent flow into one. You start again.

Mark does not start again. Mark has learnt.

What's actually changed this year

Underneath the renaming, something real has happened, and it's worth being clear about. Cloud flows can now call Copilot Studio actions mid-flow: classify this email, draft this reply, decide which queue it goes to. Copilot Studio can call desktop flows in return, so when an agent needs something done in the legacy system with the Windows front end from 2011, it hands off to RPA and gets a result back. Desktop flows have grown self-healing, which means a moved button no longer takes the whole thing down at three in the morning. And this month several multi-agent orchestration features moved out of preview, with evaluation APIs so you can measure whether the agent got it right rather than assume.

The line between "automation" and "agent" has quietly gone. Automation is what agents reach for when something needs to happen reliably. Agents are what automation reaches for when the next step needs judgement. Mark's expenses process now has both, which is exactly right. The confusion was only ever about names and invoices.

Mark's rules

He wrote these on a sticky note. They cover most cases.

1. Runs in the background, predictable volume, no AI in the loop? Cloud flow. You already pay for the licence. Leave it be.
2. An agent calls it, or it needs an AI step inside? Agent flow. Accept the credit billing, write down who owns it, and don't book Crete without a plan.
3. Several agents, branches, hand-offs? Workflow, once it's out of preview. Until then, pilot only.
4. Tempted to convert something that already works? Make a cup of tea first.

If anyone from Risk is reading

The hard part was never the canvas. It's knowing what's running and what it can touch. Two things landed in June that help: advanced connector policies are now GA, so admins can control which actions (and which MCP servers) inside a connector an agent may use; and Power Platform inventory now records which connectors every app, flow, agent flow and agent actually talks to. "What has access to the payments system?" becomes a report, not a fortnight of Teams messages.

Put agent flows in solutions, name them so a stranger can tell what they do, and give someone in the Centre of Excellence the job of reading the credit consumption report every month. A meter without a meter reader ends the way you'd expect.

Pin that to the wall. It'll save you a meeting.

Editor's insight

Mark's year would have been a lot shorter if the person building the flow, the person managing the environment and the person holding the budget had all understood the same three-column table in March. That shared vocabulary is the whole game, and it's teachable. Excelgoodies runs live, instructor-led Power Automate Courses, mostly employer-funded, covering cloud flows, agent flows and the Copilot Studio side together, for teams who'd rather learn which one to use before the first invoice explains it to them.
 

Power BI