Power Automate for desktop (often shortened to PAD or called Power Automate Desktop) is Microsoft’s robotic process automation (RPA) application for Windows. It lets users build desktop flows that operate desktop applications, web browsers, files, spreadsheets and legacy systems by simulating the clicks, keystrokes and reads a person would perform.
In RPA terms, Power Automate for desktop is the robot authoring and execution component of the broader Power Automate platform. Cloud flows handle API-based automation between online services, while desktop flows reach the systems that have no usable API, such as older ERP clients, terminal emulators or internal Windows tools.
How Power Automate for desktop runs a desktop flow
A desktop flow is a sequence of actions assembled in the flow designer, a drag-and-drop editor with a library of several hundred prebuilt actions. Each action performs one step, such as launching an application, clicking a UI element, reading a cell from Excel, or running a script, and passes results forward as variables.
To interact with screens, the tool stores UI elements described by selectors, which identify a control by attributes such as window title, control type, name or automation ID. When the flow runs, the runtime locates the control through Windows UI Automation, browser extensions or other accessibility interfaces, and falls back to image or text recognition only when structured access is not available.
| Component | Purpose | Example |
|---|---|---|
| Actions | Individual automation steps | Click UI element, write to Excel |
| UI elements and selectors | Reliable references to screen controls | Save button in an invoicing client |
| Variables | Store data between steps | Invoice number read from a form |
| Subflows | Reusable groups of actions | Login routine called by many flows |
| Recorder | Captures user actions as draft steps | Recording a data entry sequence |
| Error handling | Retries and alternative paths | On block error, retry three times |
Attended and unattended execution modes
Power Automate for desktop supports both attended automation, where the flow runs on a signed-in user’s session while that person works alongside it, and unattended automation, where the flow runs on a machine without a person present. The mode decides how the flow is triggered, what licensing applies and how the machine must be prepared.
| Mode | Who is present | Typical trigger | Main requirement |
|---|---|---|---|
| Local manual run | The author or user | Started from the console | Desktop app installed |
| Attended from the cloud | A signed-in user | A cloud flow starts it | User session active |
| Unattended | Nobody | Schedule or cloud event | Registered machine, unattended license |
| Hosted machine or group | Nobody | Queued cloud requests | Cloud-provisioned virtual machines |
For cloud-triggered runs, the machine is registered with a Power Automate environment, and a cloud flow calls the desktop flow through the desktop flows connector. Machine groups let several machines share a queue, so runs are distributed and a single machine failure does not stop processing.
Power Automate for desktop compared with other RPA tools
Power Automate for desktop competes with dedicated RPA platforms such as UiPath, Automation Anywhere and Blue Prism. Its distinguishing feature is tight integration with the Microsoft ecosystem, including Windows, Microsoft 365, Dataverse and the cloud flow designer, which lowers the entry barrier for citizen developers.
| Aspect | Power Automate for desktop | Dedicated RPA platforms |
|---|---|---|
| Entry cost | Desktop app available for Windows users | Usually licensed from the start |
| Orchestration | Cloud flows, machine groups, work queues | Mature bot orchestrators |
| Ecosystem fit | Strongest with Microsoft 365 and Dataverse | Broad, vendor-neutral connectors |
| Target builders | Citizen developers and IT | Often specialized RPA developers |
| Governance | Environments and data loss prevention policies | Platform-specific control rooms |
The comparison is not about which tool is universally better. Organizations already standardized on Microsoft 365 often find PAD sufficient for departmental automation, while large automation programs with hundreds of robots may prefer a platform built around centralized orchestration from the outset.
Building reliable desktop flows
The reliability of a desktop flow depends mostly on selector quality and explicit waiting. A flow that clicks before a window has loaded, or relies on a selector containing a changing window title, works in testing and fails in production.
- Edit selectors to remove volatile attributes such as dates, session numbers or full window titles, and use wildcards where appropriate.
- Wait for elements to appear instead of inserting fixed delays, which are either too short on slow days or waste time on fast ones.
- Prefer structured actions, such as Excel or database actions, over clicking through a user interface when both are possible.
- Store credentials securely in Azure Key Vault or as sensitive variables rather than as plain text in the flow.
- Log each processed item so a failed run can resume without repeating completed records.
Limitations and common pitfalls
Like all UI-based RPA, Power Automate for desktop is fragile against interface changes. An application update that renames a button or changes a layout can break every flow that depends on it, so UI automation should be a bridge to systems without APIs rather than the default integration method.
| Symptom | Likely cause | Fix |
|---|---|---|
| Element not found | Volatile selector attribute | Simplify the selector, add wildcards |
| Flow fails only when unattended | Screen locked or resolution differs | Fix resolution, run in a dedicated session |
| Duplicate records after retry | No processed-item tracking | Check status before each write |
| Slow execution | Fixed waits and UI-heavy steps | Use waits on elements and direct actions |
Put simply
Many office jobs involve copying data from one program into another, again and again. Power Automate for desktop lets a Windows computer do that clicking and typing by itself, following steps that someone sets up once.
It is like teaching a very patient assistant exactly which buttons to press. The assistant is fast and never gets bored, but it gets confused if the screen changes, so the steps need care and testing.
In practice
An accounts payable team at a logistics company receives around 300 supplier invoices per week as PDF attachments, which staff manually type into an older Windows-based accounting client that has no API. Each invoice takes several minutes, and typing errors cause payment delays.
The team builds a desktop flow that reads extracted invoice fields from an Excel file, opens the accounting client, fills in the supplier, amount and due date, and records the generated document number back in the spreadsheet. The flow runs unattended overnight on a registered virtual machine. Manual entry now covers only exceptions, such as unknown suppliers, which the flow flags for a person to review the next morning.