Power Automate Desktop vs Cloud Flows - When to Use Each

The Power Automate naming is genuinely confusing. Microsoft has two products under the same brand that do completely different jobs, and the documentation often slides between them without making the distinction clear. Half the calls I take about Power Automate start with someone describing a problem in Cloud Flow terms but actually needing Desktop, or the other way around.

So let's sort this out properly. I'll cover what each one does, the real cost differences in Australian dollars, when each is the right call, when neither is, and how to combine them when you need both. This is written for buyers and project sponsors rather than developers - if you're trying to decide what to invest in, this should give you enough to make the call.

I run Team 400 and we've been building Power Automate solutions for Australian businesses for years. Most of what's below comes from things we've seen go right and wrong on real client engagements.

The Actual Difference

Cloud Flows automate processes that happen in cloud applications. They use APIs to move data and trigger actions between services. When an email arrives, save the attachment to SharePoint, post a Teams notification, and create a task in Planner. All of that happens in Microsoft's cloud. No desktop, no Windows machine, no human-style interaction. Cloud Flows talk directly to the underlying services.

Desktop Flows automate processes that happen on a Windows desktop. They control applications the same way a person would - clicking buttons, typing into forms, reading text from the screen. This is what most people mean when they say RPA. The classic use case is a legacy application that has no API, so the only way to automate it is to simulate what a human does. Open the program, log in, move through menus, enter data, click submit, capture the result.

The two products share the Power Automate brand and the same designer interface, but the mental model and the cost structure are different.

A Decision Framework You Can Actually Use

Here's the question I ask clients to start with.

Does the application or service you want to automate have an API or a Power Automate connector?

If yes, use Cloud Flows. Almost always. Cloud Flows are faster, more reliable, cheaper to run, and easier to maintain. The only time you'd choose Desktop over a working API is when the API is so limited or so badly designed that screen automation is genuinely simpler. That happens occasionally but not often.

If no - the application is a legacy desktop tool, an old web app with no API access, or a SaaS product that locks important features behind the UI - then Desktop Flow is your option.

If you don't know whether the application has an API, that's the first thing to find out. We've had clients invest months in Desktop automation for a system that turned out to have a perfectly good API the vendor hadn't advertised well.

Power Automate Licensing Costs in Australia

Licensing is where many Power Automate projects come unstuck. The headline price looks low, then someone discovers the premium connectors they need cost extra, or that Desktop Flows running unattended need a different licence.

Here's the current Australian pricing structure as of 2026, in AUD.

Cloud Flows - Standard connectors only. Included with most Microsoft 365 business plans. No extra cost. Covers SharePoint, Outlook, OneDrive, Teams, Planner, Excel Online, and a long list of others. If your automation only touches these, you might pay nothing beyond what you already do.

Cloud Flows - Premium connectors. Around $22-25 per user per month for the Per User plan, or around $150 per month for the Per Flow plan (which allows unlimited users to trigger the same flow). Premium connectors include SQL Server, Dynamics, Salesforce, custom HTTP, and many third-party SaaS tools.

Desktop Flows - Attended mode. Same licence as premium Cloud Flows. A user runs the bot on their own machine, signed in as themselves. The licence costs $22-25 per user per month.

Desktop Flows - Unattended mode. This is where costs jump. Unattended bots run on dedicated machines without a user signed in, often overnight or on a schedule. The Process licence is around $230-260 per bot per month, plus the underlying premium licence for any user who builds or owns the flow.

AI Builder and Process Mining credits. Sold separately. Most clients don't need these but if you do, budget another $750-1500 per month for meaningful usage.

For a typical mid-market client doing a mix of Cloud and Desktop automation, total Power Automate licensing lands between $1,200 and $6,000 per month. That's before consulting costs to build the flows.

When Cloud Flows Are the Right Call

Cloud Flows shine when the work is API-based, event-driven, and needs to run reliably without human babysitting. Some scenarios where we use them as a default:

Approval workflows. Invoice approvals, leave requests, purchase orders, document sign-offs. Cloud Flows handle these elegantly. They integrate with Teams for approvals, write back to SharePoint or Dynamics, and produce audit trails automatically. Most of our approval workflow builds sit here.

Notifications and alerts. When something happens in System A, tell System B and notify a person. Critical incidents from a monitoring tool feeding into Teams. New leads from a website form going to Dynamics and the sales team's inbox.

Document processing pipelines. New invoice lands in an email, extract the data with AI Builder, post it to Dynamics, archive the PDF in SharePoint. All API-based, all happening in the cloud.

Scheduled data sync. Pull data from one system every hour, transform it, push to another. Cloud Flows do this well as long as both endpoints have connectors.

Integration glue. When you have three or four cloud SaaS tools that need to talk to each other, Cloud Flows are often the cheapest and quickest way to wire them together.

If your problem fits one of these patterns and the systems involved have working APIs, you're in Cloud Flow territory. Don't overthink it.

When Desktop Flows Earn Their Keep

Desktop Flows have a reputation problem because lazy RPA vendors oversold them for years. But there are real scenarios where they're the right tool, not because they're elegant but because nothing else works.

Legacy line-of-business applications. The 1998 accounting system, the bespoke insurance underwriting tool, the manufacturing control software. These applications don't have APIs and the vendor won't build one. Desktop automation is the only way.

Web applications that hide functionality behind the UI. Some SaaS vendors restrict their APIs to expensive enterprise tiers while letting you do everything through the browser. Desktop Flow can automate the browser side. It's not pretty, but it works.

Bulk data entry into systems you can't change. A client recently had to enter 18,000 records into a government portal that had no API and no bulk upload. A Desktop Flow ran for three nights and did the job. The alternative was three months of contractor time.

Screen scraping and extraction from desktop reports. When data is locked inside a desktop report viewer and there's no export option. Slow, but reliable enough for many scenarios.

Coordinating multiple desktop applications. When your process involves jumping between an ERP, a CRM, and a spreadsheet, all of which live on the desktop. Desktop Flow can choreograph the dance.

The honest assessment is that Desktop Flows are slower, more fragile, and need more maintenance than Cloud Flows. UI changes break them. Slow network days break them. Pop-up dialogs break them. But they get the job done in scenarios where the alternative is permanent manual work.

A Comparison Table

Aspect	Cloud Flows	Desktop Flows
What they automate	Cloud services and APIs	Desktop and legacy applications
How they work	API calls between services	Simulated mouse, keyboard, screen reads
Where they run	Microsoft cloud	Windows machine (attended or unattended)
Trigger types	Events, schedules, HTTP, manual	Attended manual, called from cloud flow, schedule
Reliability	High	Medium - UI changes can break them
Speed	Milliseconds per step	Seconds per step
Maintenance burden	Low	Higher - especially with frequent UI changes
Typical licence cost	$0-25 per user per month	$22-260+ per user or bot per month
Audit trail quality	Excellent	Good but more manual
Suitable for high volume	Yes, scales naturally	Yes but each bot is a single thread

When You Need Both Together

The combinations are often where Power Automate gets really interesting for Australian businesses. A common pattern we build looks like this.

A Cloud Flow triggers when a new email arrives in a shared inbox. It checks the sender and subject, extracts the attachment, and decides whether the work needs to go into the legacy system. If yes, the Cloud Flow calls a Desktop Flow running on a dedicated unattended machine. The Desktop Flow opens the legacy app, logs in, enters the data, captures the resulting reference number, and returns it. The Cloud Flow takes the reference number, posts it to a SharePoint list, and sends a Teams notification to the team.

This hybrid pattern lets you take advantage of cloud reliability and audit trail for the orchestration, while still automating the parts that need RPA. Most of our serious process automation builds use this pattern.

The trick is to keep the Desktop Flow doing the absolute minimum - just the part that has to touch the legacy UI - and let the Cloud Flow handle everything else. We've inherited solutions from other vendors where Desktop Flows were doing 90% of the work including things that should have been API calls. Slow, fragile, expensive to maintain.

When Power Automate Isn't the Right Tool At All

Honest opinion time. Power Automate isn't always the right answer.

For complex, high-volume integrations, a proper integration platform like Azure Logic Apps or Azure Functions usually wins. Power Automate's flow designer is great for citizen developers but becomes painful when flows have hundreds of steps or need version control and CI/CD.

For data movement at scale, Microsoft Fabric or Data Factory is better. Power Automate is fine for shovelling small amounts of data but it isn't an ETL tool.

For AI-driven decision-making, Power Automate plus AI Builder can do a lot but it has ceilings. For anything sophisticated we'll often build a custom AI agent and trigger it from Power Automate rather than try to do everything inside the flow.

For genuinely complex RPA, dedicated RPA platforms like UiPath sometimes still beat Desktop Flow on advanced features. We don't recommend this often because the cost difference is significant, but it's a real consideration for some enterprises.

The point is, Power Automate isn't a hammer. It's one tool in a kit. Good consulting is about choosing the right tool, not pushing the one you happen to know.

Common Misconceptions That Waste Money

"We need Desktop Flows because that's what RPA is." Not necessarily. If your target systems have APIs, Cloud Flows are RPA in a more reliable form.

"Cloud Flows are simple and Desktop Flows are advanced." Wrong way round, usually. Building a reliable unattended Desktop Flow with proper error handling is harder than most Cloud Flow work.

"We'll start with Desktop because it's easier to record." Recording a flow takes ten minutes. Maintaining it for two years takes forever. The upfront ease is misleading.

"Power Automate is free with Office 365." Standard connectors are. Anything serious needs premium licensing and the numbers add up quickly.

"One bot can handle everything we need." A single unattended bot is a single thread. If your process needs to handle ten concurrent items, you need either parallelism in Cloud Flow or multiple bot licences.

How to Decide on Your Project

Walk through this set of questions.

What's the trigger? An event in a cloud system, an email, a schedule, or a manual click in a desktop app?

What systems are involved? Are they cloud SaaS with APIs, on-premise systems with connectors, or legacy desktop apps?

How often does it run? Once a week, hundreds of times a day, or always-on?

Who runs it? Does a person trigger it from their machine, or does it need to run unattended?

What's the budget envelope per month? Cloud Flow with standard connectors is essentially free. Multiple unattended Desktop bots can run several thousand dollars monthly.

What's the maintenance appetite? Cloud Flows are forgiving. Desktop Flows need someone watching them.

Answer those and you usually have a clear path. If you don't, that's worth a discovery conversation.

Getting Help

If you're sizing a Power Automate investment and want a clear picture of what fits your situation, we offer scoping sessions for Australian businesses considering Power Automate or any of the related Microsoft AI tooling. Two hours, fixed fee, you walk out with a recommendation that may or may not include us building it for you.

We've shipped Power Automate solutions across financial services, insurance, logistics, and professional services. Some are pure Cloud Flow. Some are hybrid. A few are heavy Desktop Flow because the client's environment demanded it.

Reach out if you want to talk through your situation. We'll tell you honestly whether Power Automate is the right call, and if it isn't, what is.