Almanac
Microsoft/power-automatePower Platform

Consultant KB for Microsoft Power Automate end to end: cloud flows, desktop flows and RPA, connectors and integration, AI and agent flows, process and task mining, approvals and human-in-the-loop, ALM and solutions, governance and security, licensing and capacity, monitoring and troubleshooting, plus cross-cutting decision guides. Implementation notes, configuration decisions and the gotchas that bite on real projects. Populated by the daily author agent from the Power Automate release plans, docs repo and product blog, plus the author's own consultant notes.

power-automate/02-desktop-flows-rpa/feature-power-automate-for-desktop.md
feature-power-automate-for-desktop.mdv1 · history
CurrentApplies to Desktop flowsUpdated last monthSource Microsoft Learn ↗

What it does

The Windows application where desktop flows get built and run. It gives you a console for your flow list, a designer with a drag-and-drop action library, a recorder, and a UI elements repository. Everything else in the RPA story — machines, unattended runs, work queues — hangs off flows authored here.

Key facts

  • Two surfaces ship together: the flow designer for authoring, and the Power Automate machine runtime app that registers the machine with a Power Platform environment. The machine-runtime component is an install-time checkbox, easy to miss.
  • You sign in with a Microsoft account, a work or school account, or an organisation premium account. Capability differs sharply between them — cloud-flow triggering, sharing, machine management and work queues are premium RPA features tied to the Power Automate Premium user licence.
  • The action library covers files and folders, Excel, UI automation, browser automation, HTTP and web services, scripting (PowerShell, Python, VBScript, JavaScript), Active Directory, terminal emulation and more, plus custom actions built as .NET assemblies (premium).
  • Flows are structured as a Main flow plus optional subflows, with input and output variables that make the flow callable from a cloud flow.
  • Version control and version comparison for desktop flows reached general availability on 13 May 2026 (2026 wave 1), so you finally get a real history rather than "save over the top and hope".
  • Unattended execution needs the Power Automate Process licence; the Premium user licence covers attended RPA and the authoring/management experience.

When to use / skip

Reach for it when the target system has no API, no connector and no realistic prospect of getting one — legacy ERPs, thick clients, green-screen terminals, ancient web apps. If a supported connector exists, use the connector and a cloud flow instead; UI automation is always the more fragile option and you'll pay for that fragility in maintenance every time the vendor ships a UI change.

Configuration decisions

  • Which sign-in account type the makers use, because that decides what they can build and whether flows are shareable.
  • Whether desktop flows live in a solution from day one — retrofitting ALM onto a pile of My-flows desktop flows is miserable.
  • MSI versus Microsoft Store install, which changes paths and how you script things like Task Scheduler invocation.
  • Whether makers author on their own machines or on a shared/hosted build machine that matches the runtime environment.
  • How you'll pin or manage the Power Automate for desktop version across a fleet, since behaviour does change between versions.

Gotchas

  • Authoring on a maker's laptop and running unattended on a server is the single biggest source of "works on my machine". Screen resolution, installed apps, app versions and Windows policies all differ.
  • The machine-runtime install option is skippable during setup, and without it the machine never appears in the portal. People then spend an hour wondering where their machine went.
  • The free/Microsoft-account experience looks almost identical in the designer, so makers happily build things they can't then trigger or share. Check licensing before the enablement session, not after.
  • Recorded flows are a first draft. Conditionals, loops and error handling can't be recorded and redundant actions always creep in.

Consultant notes

  • Position desktop flows as the fallback tier in an automation strategy, not the default. Clients who lead with RPA end up with a maintenance estate nobody wants to own.
  • Get naming, subflow structure and error-handling conventions agreed before the first sprint. Desktop flows sprawl faster than cloud flows.
  • Warn the client that RPA carries an ongoing maintenance budget tied to third-party UI changes they don't control. Put a number on it early.
  • Environment strategy matters here: a machine can only run cloud-triggered desktop flows in one environment at a time, which constrains how you split dev/test/prod.

Worth a look after each major Power Automate for desktop release, or whenever the client's licensing mix shifts

Was this accurate?
Related
Cloud flow vs desktop flow11-decision-guidesDesktop flow triggers and scheduling02-desktop-flows-rpaPower Automate licensing overview09-licensing-and-capacityProcess and Hosted Process licences09-licensing-and-capacityPower Automate licensing decision guide11-decision-guidesPower Automate vs Azure Logic Apps11-decision-guides