Power Automate cloud vs desktop flows: choose the execution route
Compare Power Automate cloud and desktop flows by execution route, machine needs, licensing, retries and failure ownership.
In this guide
Choose around the system interface, not the product name
Microsoft’s flow overview describes cloud flows triggered automatically, instantly or on a schedule, and desktop flows for web or desktop tasks. A connector-driven workflow and an automation interacting with a machine’s application interface have different operating requirements.
Start with the input, required action and receiving system. If a task can be completed through an appropriate supported connector, evaluate that route. If the necessary work exists only in a desktop application, assess the machine-based route and who will maintain it.
The workflow may combine both routes
Microsoft documents triggering desktop flows from cloud flows, including input and output variables. This supports a combined design, but it adds a boundary to monitor: a cloud trigger succeeding is different from the desktop task completing correctly.
Imagine a fictional operations team receiving an approved request in a cloud application and entering it into a legacy desktop system. Write down the request identifier, permitted input and completion response. Decide how the cloud side knows whether the receiving system accepted the record.
A desktop run needs an operating environment
Microsoft’s desktop prerequisites distinguish supported environments and capabilities. Check the actual Windows edition, machine availability, account, connection and entitlement for the intended attended or unattended route.
Do not infer unattended rights from being able to build a local desktop flow. In the project brief, name the person responsible for machine updates, application changes, credentials and failed runs. A working demonstration on an employee’s laptop is not yet an agreed operating service.
Design a failure case before rollout
| Boundary | Question | Acceptance check |
|---|---|---|
| Trigger | Which request is approved to run? | One synthetic eligible request starts once |
| Machine | Where does the desktop task execute? | Required application and connection available |
| Destination | How is completion recognised? | Receiving record matches the request |
| Retry | What prevents duplicate entry? | Repeated request handled by agreed rule |
| Failure | Who sees an incomplete run? | Owner receives actionable status |
These are proposed tests. Leave outcomes unrecorded until an authorised pilot observes them. Treat a retry as a new risk of duplicate work, especially when a destination accepts the record but the acknowledgement is lost.
Price and maintain the complete automation
Collect the connector, execution, machine and support requirements in one quote. Keep the development tool, a demonstration allowance and the retained production arrangement distinct. Include monitoring and exception work rather than measuring value only from the time saved on a perfect run.
Use the Power Automate profile and automation category to frame the shortlist. For any candidate, test the same input, duplicate and failure. The right route is the one your team can run, observe and recover under the actual operating conditions.
Frequently asked questions
What is the difference between Power Automate cloud and desktop flows?
Cloud flows support automated, instant or scheduled cloud workflows. Desktop flows automate work involving web or desktop interfaces on a supported machine.
Can a Power Automate cloud flow start a desktop flow?
Microsoft documents a combined route using the desktop-flow action. Confirm the required connection, machine, account and licence for the intended execution mode.
Does creating a local desktop flow prove I can run it unattended?
No. Check the separate unattended execution requirements and retained entitlement before planning production operation.
Put the guide into practice
Explore workflow automation tools, then compare your shortlist.
Explore the category →