Microsoft Power Automate Desktop Licensing: RPA, Attended vs Unattended Automation, and the Enterprise Cost Reality

The Free-to-Expensive RPA Licensing Trap

Power Automate Desktop is included free with Windows 10 and Windows 11. That statement is technically accurate and commercially misleading in equal measure. The free inclusion covers the desktop flow builder and the ability to run attended automations on a licensed Windows device — which is useful for individual productivity automation. The moment an organisation wants to run flows without a human present (unattended), scale automation across multiple machines, use cloud connectors that require premium licences, or apply AI Builder capabilities, the free tier ends and a complex paid structure begins.

Understanding exactly where the free tier ends and the paid tier begins — and what the paid tier actually costs — is the prerequisite for any enterprise RPA programme that expects to remain in budget. This guide covers the full Power Automate Desktop licensing architecture, the attended vs unattended distinction, hosted machine groups, Process Mining, AI Builder in desktop flows, and how to structure an EA negotiation for an enterprise automation deployment.

Power Automate Desktop: What's Actually Free

The free Windows 11/10 inclusion provides:

The desktop flow designer: The full Power Automate Desktop application for building and testing desktop flows. No licence key required — it installs from the Microsoft Store or directly from the Power Automate portal.

Local attended execution: Running desktop flows that are triggered manually by a user on their own machine. The user must be present and signed in. The flow runs in the user's session.

Standard actions library: The core action library including UI automation, browser automation, Excel, Word, file/folder operations, text manipulation, and basic system actions.

What the free tier does not provide: cloud-triggered flows, premium connector access, unattended execution, machine group management, run queues, monitoring dashboards beyond the local run history, or AI Builder actions. All of these require paid licences.

The Licensing Architecture: Three Paths

Enterprise Power Automate Desktop deployment sits across three licensing paths, each with different scope and cost:

The critical architectural point: the Power Automate Process licence covers the unattended bot — the machine and execution slot — but it does not give the underlying flow access to premium connectors unless there is also a per-user or per-flow licence associated with the flow. This double-licence requirement is a consistent source of EA under-budgeting. An unattended flow that connects to Dataverse, SharePoint, or SQL Server via premium connectors needs both the Process licence (for the bot) and a per-user or per-flow licence (for the connector access).

Attended vs Unattended: The Core Distinction

The attended/unattended distinction in RPA licensing is the most commercially important concept in Power Automate Desktop:

Attended Automation

Attended automation runs in a user's active Windows session. The user typically triggers the flow (manually or via a keyboard shortcut) and may interact with it during execution. The automation assists the user — it does not replace them. Attended automation is appropriate for tasks that require human judgment at specific points, that involve applications that do not permit background access, or that are part of a hybrid human-in-the-loop process. The per-user plan includes attended automation via cloud trigger for flows that also run desktop flow actions.

Unattended Automation

Unattended automation runs without a user present, typically on a dedicated machine or virtual machine. It is triggered automatically (by a schedule, another flow, or an external event) and runs to completion without human interaction. Unattended automation is appropriate for batch processing, overnight data migration, report generation, and other tasks that run at scale without human involvement. This is where the material cost difference between attended and unattended RPA manifests — and where most enterprise RPA programmes underestimate their licence requirements at the outset.

Hosted Machine Groups

Hosted Machine Groups is Microsoft's managed virtual machine service for Power Automate unattended RPA. Rather than managing dedicated RPA machines on-premises or in Azure, organisations can use Microsoft-hosted cloud VMs that are provisioned on demand for bot execution. The commercial mechanics:

Hosted Machine Groups require a Process licence per concurrent session — the same £115–£135/bot/month as on-premises unattended. The hosting infrastructure (the VM itself) is provisioned by Microsoft and billed via Azure consumption (compute + storage). This is not included in the Process licence price.

The total cost for hosted unattended RPA is therefore: Process licence (~£125/bot/month at EA) + Azure compute (~£40–£120/bot/month depending on VM size and usage pattern) = £165–£245/bot/month total. This is more expensive per bot than self-managed infrastructure for organisations with strong Azure/DevOps skills, but less expensive once infrastructure management overhead is factored in. For organisations without a dedicated RPA platform team, hosted machine groups typically deliver better TCO than self-managed at medium scale (5–30 bots).

Process Mining Add-On

Process Mining is a separate Power Automate add-on that uses event log data to visualise how business processes actually execute — identifying bottlenecks, deviations, and automation opportunities. It is not included in any Power Automate per-user plan or Process licence. Pricing is approximately:

Power Automate Process Mining add-on: approximately £1,200–£1,500/tenant/month at EA pricing for a limited data ingestion tier, with additional costs for higher data volumes. This is a significant incremental cost relative to the core automation licences and should be evaluated on a standalone ROI basis before inclusion in an enterprise Power Automate deployment budget.

For organisations using Celonis, UiPath Process Mining, or other third-party process mining tools, the Power Automate Process Mining add-on creates an overlapping capability that should be evaluated for consolidation rather than automatically added to the EA as a supplementary tool. The Microsoft integration advantage is real but not always worth the full price of a parallel capability.

AI Builder in Desktop Flows

AI Builder capabilities — including document processing (form recognition, invoice extraction), image classification, text analytics, and prediction models — can be embedded in Power Automate desktop flows. AI Builder is not included in the Power Automate per-user or Process licences. It is sold on a capacity model (~£400/tenant/month for 1 million AI Builder credits, with additional capacity at additional cost).

The most common AI Builder use case in desktop flows is intelligent document processing: extracting structured data from PDFs, invoices, or forms as part of a larger automation. The commercial trap is that the document processing action looks like a standard desktop flow action in the designer — the licence requirement only becomes apparent at deployment review. Organisations building automation pipelines that include AI Builder document extraction must include AI Builder capacity in their licence budget from the design phase, not as a post-deployment discovery.

Power Automate Desktop vs Competitors

Enterprise RPA evaluation should include the full commercial picture. The competitive comparison for enterprise unattended RPA:

At the Process licence price, Power Automate Desktop is significantly cheaper per unattended bot than dedicated RPA platforms. However, the total cost comparison must include the per-user or per-flow licences required for premium connector access, AI Builder capacity for intelligent document processing use cases, and the operational maturity of the Power Automate Desktop platform relative to enterprise-grade UiPath or Automation Anywhere deployments. For organisations whose automation requirements are primarily M365-integrated processes with moderate complexity, the price advantage is decisive. For complex enterprise-wide automation programmes with cross-system integration, the mature RPA platforms often justify their premium through reduced implementation cost and exception handling capability.

EA Negotiation Strategy for Power Automate RPA

Power Automate Desktop sits within the broader Power Platform licensing negotiation. The EA negotiation positions that create real value for automation programmes:

Model the three-year bot count before negotiating. Unattended RPA programmes typically grow — pilot bots become production bots, successful automations generate demand for adjacent processes. Building a three-year bot count projection before the EA is signed allows you to negotiate a committed volume at a discounted rate rather than adding bots at list price mid-term. The per-bot discount for Process licences at volume (20+ bots) is typically 15–25% versus standard EA pricing.

Separate per-user and Process licence negotiations. Per-user plans for attended automation and Process licences for unattended are different products with different pricing dynamics. In negotiation, Microsoft may try to bundle these — separate them, benchmark each independently, and negotiate the per-user plan as part of the broader M365/Power Platform negotiation rather than as a standalone line item.

Use UiPath or Automation Anywhere pricing as competitive leverage. Even if you have no intention of deploying an alternative RPA platform, having a documented cost comparison creates negotiating leverage. A well-prepared alternative analysis — showing that UiPath at £800/bot/month is unacceptable but that the Microsoft Process licence at £130/bot/month is only acceptable at scale if properly supported — creates the commercial context for a meaningful volume discount discussion.

Challenge AI Builder capacity pricing separately. AI Builder credits are priced independently of the automation licences. For automation programmes with significant document processing requirements, negotiating AI Builder capacity as a committed volume add-on (rather than purchasing standard capacity at list price) typically achieves 15–20% better pricing.

For the full Power Platform licensing framework and negotiation context, see our Power Platform licensing complete guide, Power Automate licensing guide, and Dataverse capacity licensing guide.

FAQ

Can we run unattended automations using only the free Windows 11 inclusion?

No. The free Windows 11 inclusion of Power Automate Desktop supports attended automation only — a user must be present and the flow must run in their active session. Unattended execution (background, without a signed-in user) requires a Power Automate per-user with RPA plan or Power Automate Process licence. Running unattended flows without the appropriate licence is a compliance violation, not just a feature limitation.

Does the Power Automate Process licence include cloud flow licences?

No. The Process licence covers the unattended bot (the machine execution slot). If the unattended flow connects to premium connectors (Dataverse, SQL Server, SharePoint via Power Automate connector with premium actions), those connections require a per-user or per-flow plan licence. The specific requirement depends on whether the flow is running as the process bot identity or a delegated user identity — get confirmation from Microsoft on the specific connector licensing requirement for your architecture before finalising the licence model.

What's the difference between Power Automate Desktop and the full Power Automate cloud product?

Power Automate Desktop handles desktop and UI automation — controlling Windows applications, browsers, and legacy systems that don't have APIs. Power Automate cloud flows handle API-based, connector-based, and event-driven automation. In practice, most enterprise automation combines both: a cloud flow handles the trigger and integration logic, and desktop flows handle the UI-based steps within the process. Both are part of the Power Automate product family, but licensed separately — desktop automation capability is not automatically included in cloud Power Automate licences at the unattended level.