Where Power Automate Desktop fits — and where it doesn't
Power Automate Desktop (PAD) is the right tool when a process involves a Windows application that cannot be reached any other way. The most common scenarios: an ERP or accounting system from the 1990s or 2000s that has no API and no plans for one; a government portal or regulatory reporting tool that only accepts keyboard navigation; a legacy CRM that was built before REST existed; a local application that exports data only to the Windows clipboard or a local file. PAD also handles multi-application tasks — copy from System A, process in Excel, paste into System B — that would require API access to two or more systems simultaneously. If a system has a usable API, Azure Logic Apps or Power Automate cloud flows are a better choice: more reliable, easier to monitor, and cloud-native. PAD is the right answer specifically when there is no API.
The technology works by recording or scripting a sequence of UI interactions — open application, click button, read text from field, enter value in form, press tab, confirm. The recording mode captures mouse clicks and keystrokes directly; the scripting mode provides a library of pre-built actions (read from Excel, navigate browser, extract table from PDF, interact with Windows controls) that can be assembled without recording. The resulting flow runs unattended on a machine where it is deployed — either a physical desktop or a virtual machine — and can be triggered from Power Automate cloud, a schedule, or a manual button.
Recording a desktop flow — what to expect
Recording mode in PAD works similarly to a macro recorder but produces a structured, editable flow rather than a fixed keystroke sequence. Start the recorder, perform the task manually — open the application, navigate to the right screen, enter the data, confirm, close — and stop the recorder. PAD captures each interaction as a named action with the target application window, control name, and value. The recorded flow can then be parameterised: instead of hardcoded values, it reads from an Excel file or SharePoint list and repeats for each row. Error handling can be added: if a field is not found (because the screen state was unexpected), pause and notify rather than silently failing.
The first recording session for a simple, consistent task — 5–10 steps, one application, predictable data format — typically produces a working flow in 2–4 hours. Parameterisation and error handling add half a day. More complex tasks — multiple applications, conditional routing, data validation — take 1–3 days depending on the number of variations that need handling. The limiting factor is not the tooling but the task variability: a process that always follows the same sequence in the same application can be automated faster than one where the path through the system depends on the data.
The processes that benefit most from desktop automation
The highest-value targets for Power Automate Desktop are processes that are high-frequency, low-variation, and time-consuming. Monthly payroll journal entry into a legacy accounting system: the process follows the same sequence every time, takes 45 minutes, and involves no judgment — PAD can do it in under 5 minutes, unattended. Daily report extraction from an application that only supports copy-paste output: PAD opens the application, navigates to the report, copies the output, and writes it to a SharePoint file before the team arrives in the morning. Government portal submissions that require filling the same form fields from internal data: PAD reads from the source system, fills the portal form, submits, and captures the reference number — a task that would take an employee an hour takes PAD 3 minutes.
The economic case is straightforward: if a task takes 25 minutes per execution and runs daily, that is over 100 hours per year for a single process. PAD completes the same task in 2–3 minutes. The investment to build and test the automation is typically 1–3 days, paid back within the first month. Since PAD is free with Windows 11, the only cost is build time — making it viable for smaller savings that would not justify a paid RPA licence.