Skip to content

Automation

Power Automate Desktop: when RPA pays off — and when it doesn't

A software robot clicking through screens on your behalf sounds appealing, but RPA should be your second choice after API integration. Here is when Power Automate Desktop makes sense, typical use cases and the pitfalls to avoid.

Published updated November 22, 2026 4 min read

Illustration: an automated approval workflow

What RPA is — and how it differs from integration

Robotic Process Automation (RPA) mimics a person working through a user interface: opening an application, filling in fields, clicking buttons, copying values into Excel. In the Microsoft ecosystem this is the job of Power Automate Desktop, which ships with Windows 10 and 11.

Cloud flows in Power Automate work differently. They talk to systems through connectors and APIs, exchanging data directly instead of clicking. That makes them faster, more reliable and easier to maintain.

Hence a simple rule of thumb: if an API or connector exists, use it. Reach for RPA only when there is no other way in.

When RPA makes sense

  • Legacy systems without interfaces — a desktop accounting package, a terminal-based system or an internal tool nobody will ever build an API for.
  • Third-party web portals — downloading statements from a supplier or government portal that offers no export interface.
  • Interim solutions — the system is due to be replaced within a year and a full integration would never pay back.
  • Desktop document work — bulk file manipulation, format conversions, older Office versions.

When RPA does not pay off

  • The system has an API. API integration will be more robust and cheaper to run.
  • The user interface changes often. Every screen change can break a bot. On websites that change monthly, maintenance costs escalate quickly.
  • The process is full of exceptions. Bots excel at repeating rules, not at judgement. If every third case needs a human decision, the benefit shrinks.
  • The volume is low. A task that takes ten minutes a week is rarely worth automating.

Attended or unattended?

Power Automate Desktop supports two modes:

  • Attended: the bot runs on a signed-in user's machine, triggered by or alongside that user. Ideal for assistance — a user clicks a button and the bot fills in the same form across three systems.
  • Unattended: the bot runs on its own on a dedicated machine or virtual machine, typically overnight or on a schedule. Ideal for high-volume batch processing.

Licensing differs between the two. Running Power Automate Desktop manually on your own PC is available at no extra cost, whereas triggering desktop flows from the cloud and running unattended bots require paid plans. Always confirm current terms in Microsoft's licensing guide.

Building bots that last

  1. Use stable selectors. Bots should locate elements by identifiers, not by screen coordinates.
  2. Handle errors explicitly. What if the application fails to open, sign-in fails or a file is missing? The bot must catch the error, log it and alert someone.
  3. Separate configuration. Paths, URLs and credentials belong in variables and secure storage, not hard-coded in the flow.
  4. Combine with the cloud. Ideally a cloud flow orchestrates the process — receiving the email, routing the approval, recording the result — while the desktop bot performs only the step that cannot be done any other way.
  5. Monitor. Someone needs to see that the bot is running and how many items it processed.

A typical scenario

An illustrative example without real data.

Every morning a company needs to download orders from a large customer's portal that has no API. At 6 a.m. a cloud flow triggers a desktop bot on a virtual machine. The bot signs in to the portal, downloads a CSV file and saves it to SharePoint. The cloud flow then processes the data through connectors and writes the orders into the ERP system. If the download fails, an alert is posted to Teams. RPA handles just one step; the rest runs on more reliable integrations.

Bottom line

Power Automate Desktop is a valuable tool for systems without interfaces, but it is not a substitute for integration. It pays off for frequent, rule-based and stable tasks, and works best when cloud flows orchestrate the end-to-end process. Factor in licensing and maintenance before you commit.

If you are weighing a bot against an integration for your process, explore our Power Automate process automation services — we help you choose the approach that pays off long term.

Is your company ready for Power Platform?

Take a short checklist and find out where to start and what to watch out for.

Illustration: an automated approval workflow

Automation

How to calculate the ROI of process automation

Automation is worth it when it saves more than it costs. Here is a simple way to calculate payback, the factors most estimates miss, and how to choose the right process to start with.

· 4 min read

Illustration: a data architecture from sources to reports

Microsoft Fabric

What is Microsoft Fabric — and when does it make sense?

Microsoft Fabric promises everything data-related in one place: integration, warehousing, analytics and Power BI. Here is what it consists of, how capacity licensing works, and which organisations benefit most.

· 4 min read