A8gent
A8gent
·
Licensing

Power Automate Desktop License Cost: Free vs Paid

Windows licences include attended desktop flow execution locally with no orchestration. Unattended needs a $150 Process licence and a machine registered by a Premium user. The $40 figure is retired.

Power Automate Desktop License Cost: Free vs Paid visual
AI Agent Starter Kit cover

Free download

AI Agent Starter Kit

Workflow picker, ROI worksheet, 40-prompt pack, and the first-agent rollout playbook. The 1-hour version of the entire A8gent system.

Workflow picker
ROI worksheet
Prompt checklist
Team rollout plan
Open it now

No spam. Worksheet + prompt checklist + rollout plan delivered instantly.

Contents
  1. Fast answer
  2. Quick facts
  3. What this covers
  4. Why it matters
  5. Where to go next
  6. Outcomes
  7. Step by step
  8. What a Windows licence actually entitles you to
  9. Attended RPA and where the bot is borne
  10. Unattended RPA and the registration prerequisite
  11. Hosted Process and the superset that is not live yet
  12. Pay-as-you-go for desktop flows, and the fifty-run line
  13. At a glance
  14. Mistakes to avoid
  15. FAQ
  16. Related guides
TL;DRAnswer-first

Fast answer

Power Automate for desktop is free to author and run locally, and that is where free stops. Microsoft Learn's seeded licence table lists Windows licences as including attended RPA with the footnoted limitation that it only includes local execution of desktop flow with no orchestration, and as including no standard connectors, no premium connectors, no unattended RPA and no daily action allowance. The Power Automate Free user licence similarly covers authoring and running desktop flows locally in attended mode with standard connectors only. Orchestrated attended RPA, meaning registering a machine, sharing desktop flows, using premium actions and triggering runs from cloud flows, comes with the attended bot borne by a Power Automate Premium user licence at $15.00 per user a month paid yearly. Unattended RPA is a Power Automate Process licence at $150.00 per bot a month, one bot per parallel run, and the machine must still have been registered by a Premium user. Hosted Process, at $215.00 per bot a month, adds the Microsoft-hosted machine.

Facts last verified 2026-09

Quick facts

Windows licence entitlement
Attended RPA, local execution of desktop flow only, no orchestration
Power Automate Free
Desktop flows authored and run locally, attended, standard connectors, no sharing
Power Automate Premium
$15.00 user/month paid yearly, one attended bot (read 2026-09-01)
Power Automate Process
$150.00 bot/month paid yearly, one unattended bot
Power Automate Hosted Process
$215.00 bot/month paid yearly, one hosted bot
Unattended parallelism
One Process licence per simultaneous unattended run
Machine ceiling
Bots per machine limited by concurrent Windows sessions
Registration prerequisite
Machine must be registered by a Power Automate Premium user
PAYG attended desktop run
$0.60 per run
PAYG unattended desktop run
$3.00 per run
Bot vs meter break-even
50 unattended runs a month
Hosted Process as Process
Superset behaviour documented but not yet available

On this page

What this page covers

A comparison visitor should understand the tradeoff, the best-fit scenario, and the next diagnostic tool to confirm the choice.

  1. 01What Windows actually entitles you to
  2. 02Attended RPA and where it is borne
  3. 03Unattended RPA and the registration prerequisite
  4. 04Hosted Process and the superset that is not live
  5. 05Pay-as-you-go for desktop flows

Why does this matter now?

The pages currently ranking for what a Power Automate desktop licence costs are dated 2024 and quote a $40 per user figure for a SKU that no longer exists at that price. The current published answer is $15.00 per user a month for Premium and $150.00 per bot a month for Process, and the distinction that decides which one you need is attended versus unattended. Get that wrong and you either overbuy bots for work a person is sitting in front of, or you build an overnight process on a licence that is not entitled to run it.

Internal path

Where to go next from this page

These links are part of the A8gent learning and conversion path. Use them to move from concept, to diagnosis, to workflow build, to course.

Start with readiness

What you should be able to do after this

  • Tell attended and unattended apart on the licence sheet
  • See why the Windows entitlement stops short of orchestration
  • Price an unattended bot correctly
  • Compare a bot against pay-as-you-go runs

How do you do it, step by step?

1. Establish whether a human is present

Attended means a person is signed in and supervising, and the run happens on the machine they are already using. Unattended means the bot signs into the machine on the user's behalf, executes, and signs out. That single question determines the SKU, and it is a question about the process rather than about the software. Write down for each automation whether anyone is in the room when it runs.

2. Check what you already have from Windows

Microsoft Learn's seeded licence table lists Windows licences under machine scope, with attended RPA included with limitations and everything else - standard connectors, premium connectors, custom connectors, unattended RPA, hosted RPA, business process flows, on-premises gateways, process mining, AI Builder credits, Dataverse storage - not included. The footnote is the whole story: local execution of desktop flow only, no orchestration. That is genuinely useful for one person automating their own desktop and useless for a managed estate.

3. Buy Premium for the attended bot and the management surface

The Premium user licence at $15.00 a month bears one attended bot and carries the attended RPA entitlement, which Microsoft describes as what you need to register a machine, access the RPA management portal pages, add premium and custom actions, share desktop flows, create desktop flows in non-default environments and trigger attended runs including picture-in-picture mode. Microsoft also notes that several monitoring pages, including the work queue, machine list and desktop flow list, display only to Premium users.

4. Buy one Process licence per parallel unattended run

Each Process licence allocated to a machine becomes one unattended bot, and each unattended bot entitles the machine to carry one unattended desktop flow run at a time. To run several unattended flows simultaneously you buy that many Process licences. A machine's ceiling is the number of concurrent Windows sessions its operating system supports. Machines can auto-allocate bots when a run requires one, and any allocation persists until manually removed, so leaving auto-allocation on can quietly consume capacity.

5. Remember the Premium prerequisite for unattended

This is the trap. Microsoft states that allocating a Process licence to a machine still requires that the machine was registered by a Power Automate Premium user, and that to trigger attended or unattended desktop flow runs from cloud flows operating under a Process licence, the user whose connection runs the desktop flow needs a Premium licence or another user licence with desktop flow entitlement. An unattended-only budget of pure Process licences does not work.

6. Price pay-as-you-go against the bot

Microsoft publishes $3.00 per unattended desktop flow run and $0.60 per attended desktop flow run, effective 19 July 2022 and billed through Azure. A $150 Process bot equals fifty unattended runs a month. Below fifty runs a month, metering is cheaper and needs no capacity planning. Above it, the bot wins and keeps winning, because the bot has no per-run cost at all.

What a Windows licence actually entitles you to

The question behind most searches here is whether Power Automate for desktop is free, and Microsoft answers it in a footnote on a table rather than in a headline. In the seeded licence comparison on Microsoft Learn, Windows licences appear as a column with machine scope rather than user scope. Attended RPA is marked as included with limitations, and the footnote says the limitation precisely: it only includes local execution of desktop flow, with no orchestration.

Everything else in that column is Not included, and the list is long. No daily action allowance. No standard connectors, no premium connectors, no custom connectors. No unattended RPA, no hosted RPA. No business process flows, no on-premises gateways, no process mining, no process mining data storage, no AI Builder credits, no Dataverse database or file storage. The Windows entitlement is a desktop automation runtime and nothing else.

The Power Automate Free user licence sits alongside it and covers slightly different ground: creating and running cloud flows with standard connectors at 6,000 actions a day, plus authoring and running desktop flows locally in attended mode. Its practical ceiling is stated bluntly by Microsoft in a note of its own, which is that you cannot share flows when you use the Free licence. For one person automating their own machine, that combination is genuinely free and genuinely useful.

Orchestration is the word that separates free from paid, and it is worth defining in operational terms. Registering a machine so the platform knows about it. Triggering a desktop flow from a cloud flow. Scheduling. Sharing a desktop flow with a colleague. Seeing runs in a management portal. Using a work queue. None of that is in the free tier, and all of it is what turns a personal script into a departmental process.

Attended RPA and where the bot is borne

Microsoft's model puts execution capacity in an object called a bot, and each licence bears a specific number of them. The Power Automate Premium user licence bears one attended bot, as does the 90-day Trial licence. When an attended run is triggered, Microsoft describes the attended bot as securely accessing the machine already in use by the user and executing the desktop flow actions on the target applications. The user is present, signed in, and working.

The attended RPA entitlement itself is broader than execution, and this is the part that decides whether you need Premium. Microsoft states it is needed to register a machine, access the RPA management portal pages, add premium and custom actions to desktop flows, share desktop flows, create desktop flows in non-default environments, and trigger desktop flows in attended mode. Picture-in-picture attended mode, where the automation runs in a virtual window replicating the user's desktop so the person can keep working, sits inside the same entitlement.

There is a visibility dimension too that catches out teams trying to run a lean licence footprint. Microsoft notes that multiple monitoring pages in the Power Automate portal, including the work queue page, the machine list page and the desktop flow list page, are displayed only to Power Automate Premium users. So the person who runs the RPA estate needs a Premium licence even if they personally never execute a flow, because otherwise they cannot see it.

At $15.00 per user a month paid yearly, Premium is therefore best understood on the desktop side as the price of one attended bot plus the entire management surface. That is a reasonable deal for an RPA developer and an unnecessary one for a person who simply runs a local script on their own machine, which is precisely the division the Windows entitlement is drawn along.

Unattended RPA and the registration prerequisite

Unattended is a different licence and a different economic model. Microsoft describes the unattended run mode as execution without human supervision, materialised by unattended bots: the Trial user licence and the Process licence bear one unattended bot each. When an unattended run is triggered, the bot securely signs into the machine on the user's behalf, executes the desktop flow actions, and then signs out of the device.

The unit economics are one bot per parallel run. Each Process licence allocated to a machine becomes one unattended bot, and each unattended bot entitles the machine to carry one unattended desktop flow run at a time. Microsoft's guidance for parallelism is direct: to run multiple unattended desktop flows in parallel, purchase Process licences for the maximum number of runs needed to execute in parallel, and allocate Process capacity to the related machines. At $150.00 per bot a month, four simultaneous overnight processes is $600 a month.

There is a machine-level ceiling as well. Microsoft notes that depending on its operating system, each machine can support a maximum number of unattended bots, equal to the maximum number of Windows sessions the machine can concurrently open. Scaling unattended automation is therefore a licensing question and a Windows session question at the same time, and the second one is easy to forget when planning.

Now the prerequisite that breaks unattended-only budgets. Microsoft states that allocation of a Process licence to a machine still requires that the machine was registered by a Power Automate Premium user, and separately that to trigger attended or unattended desktop flow runs from cloud flows operating under the Process licence, the user whose connection is being used to run the desktop flow needs a Power Automate Premium licence or another user licence with desktop flows entitlement. There is no configuration of Process licences alone that runs an unattended estate.

One operational trap is worth naming. Machines can be manually allocated unattended bots or set to auto-allocate themselves when a run requires one, and Microsoft states that any allocation, manual or automatic, remains until a manual de-allocation occurs. Auto-allocation left on across a fleet will therefore accumulate allocated capacity that nobody consciously assigned. Disabling the auto-allocation setting on machines that should not consume capacity is the documented control.

Hosted Process and the superset that is not live yet

Power Automate Hosted Process at $215.00 per bot a month buys the same unattended capability plus a Microsoft-hosted virtual machine on Azure, so there is no physical Windows machine for you to procure, patch or keep awake. Each Hosted Process licence supports one hosted bot, which enables one Microsoft-hosted machine. The $65 a month difference against a Process licence is the whole of the infrastructure cost, which for many organisations is straightforwardly cheaper than running the equivalent VM themselves.

The interesting structure is hosted machine groups. A group auto-scales the number of turned-on hosted machines against the desktop flow workload, pulling a hosted bot from the available hosted pool each time it scales up and releasing it back when it scales down. Two settings govern it: max bots, the ceiling it can auto-allocate to, and committed bots, the guaranteed number it can immediately allocate when required. Multiple groups sharing one pool gives load balancing, which Microsoft frames as improving hosted bot utilisation.

Then there is the caveat that matters for anyone doing licence arithmetic. Microsoft documents Hosted Process as a superset of Power Automate Process, meaning it can provide the same entitlements and act as one when allocated to a cloud flow or a standard machine. But a footnote on both the types page and the deep dive states that this superset behaviour, and the associated Allow hosted capacity to be used as Process capacity setting in the admin centre, are not yet available.

Microsoft's interim guidance is unusually candid: an organisation with Process overage that could be covered by its Hosted Process licences should ignore the Process overage. Practically, this means you should buy Hosted Process because you want Microsoft to run the machine, and you should not buy it expecting it to double as spare Process capacity today. Plan the two capacity pools separately until the setting ships.

Pay-as-you-go for desktop flows, and the fifty-run line

Microsoft publishes metered pricing for desktop flow runs and it is absent from essentially every comparison page ranking on this topic. The rates, effective 19 July 2022 with billing from 1 August 2022 and billed through an Azure subscription: $0.60 per desktop flow run in attended mode, and $3.00 per desktop flow run in unattended mode. The stated intent is that organisations pay only for the flow runs they execute in a month rather than relying on per-user licences.

The break-even against a bot is a single division and it is a useful number to carry around. $150.00 for a Process licence divided by $3.00 per unattended run is exactly fifty runs. Below fifty unattended desktop flow runs a month, the meter is cheaper than the bot. Above fifty, the bot is cheaper and stays cheaper, because a bot has no marginal cost per run at all. On the attended side, $15.00 for a Premium seat divided by $0.60 is 25 runs, though the seat also buys the entire management surface, so that comparison is less clean.

Fifty runs a month is roughly two a day, which is low enough to dismiss and high enough to matter. A weekly batch job is four runs a month, or $12 metered against $150 licensed. A daily overnight reconciliation is about 22 runs, or $66 against $150. A process that fires several times an hour crosses the line before lunchtime on the second day. The point is that the low-frequency end of an RPA portfolio is genuinely mispriced by licensing, and nobody checks.

The trade-offs are the usual metered ones and they are real. There is no ceiling, so a misbehaving flow that retries becomes a bill rather than a throttle. It requires an Azure subscription, which in many organisations is a different budget and a different approval path from Microsoft 365 licences. And it does not remove the Premium prerequisite: someone still has to register the machine and hold the desktop flow entitlement. Meter the runs, licence the people.

At a glance

Power Automate desktop flow entitlements and prices, read from the Power Automate pricing page, Microsoft Learn and Microsoft licensing news on 1 September 2026

Licence or meterPublished priceDesktop flow entitlement
Windows licence (seeded)Included with WindowsAttended RPA, local execution only, no orchestration, no connectors
Power Automate Free$0Author and run desktop flows locally, attended, no flow sharing
Power Automate Trial$0 for 90 daysOne attended bot and one unattended bot, Premium capabilities except AI Builder credits and storage
Power Automate Premium$15.00 user/month, paid yearlyOne attended bot, machine registration, RPA management portal, sharing, premium and custom actions
Power Automate Process$150.00 bot/month, paid yearlyOne unattended bot, one unattended run at a time per bot
Power Automate Hosted Process$215.00 bot/month, paid yearlyOne hosted bot, one Microsoft-hosted machine, includes the unattended entitlement
Pay-as-you-go attended desktop run$0.60 per runMetered via Azure, effective 2022-07-19
Pay-as-you-go unattended desktop run$3.00 per runMetered via Azure, effective 2022-07-19
Pay-as-you-go cloud flow run$0.60 per runMetered via Azure, effective 2022-07-19
Retired $40 per user figureNot publishedAppears on 2024-dated third-party pages, not on Microsoft's current pricing page

What mistakes should you avoid?

  • Repeating the retired $40 per user desktop figure that still ranks on 2024-dated pages
  • Believing the Windows entitlement covers orchestrated or unattended RPA
  • Buying Process licences without any Premium user to register the machine
  • Assuming one Process licence lets a machine run several unattended flows at once
  • Leaving machine auto-allocation on and losing track of allocated bots
  • Overlooking the $3.00 per unattended run meter for genuinely low-volume automations
  • Expecting Hosted Process to act as a Process licence today, when Microsoft says that behaviour is not yet available

FAQ

Is Power Automate Desktop free?
For local, attended, unshared use, effectively yes. Microsoft Learn lists Windows licences as including attended RPA limited to local execution of desktop flows with no orchestration, and the Power Automate Free user licence covers authoring and running desktop flows locally in attended mode with standard connectors only and no sharing. Anything orchestrated, shared or unattended is a paid licence.
What does a Power Automate desktop licence cost?
Power Automate Premium at $15.00 per user a month paid yearly gives the attended bot and the RPA management entitlements. Power Automate Process at $150.00 per bot a month gives one unattended bot. Hosted Process at $215.00 per bot a month adds the Microsoft-hosted virtual machine. All read from Microsoft's pricing page on 1 September 2026.
Do I need a Premium licence if I only run flows unattended?
Yes. Microsoft states that allocating Process capacity to a machine still requires the machine to have been registered by a Power Automate Premium user, and that triggering desktop flow runs from a cloud flow under a Process licence requires the connecting user to hold a Premium licence or equivalent desktop flow entitlement.
How many unattended flows can one Process licence run?
One at a time. Each Process licence allocated to a machine is one unattended bot, and each bot entitles the machine to one unattended desktop flow run concurrently. For parallel runs, buy one Process licence per simultaneous run. A machine can hold as many bots as it can open concurrent Windows sessions.
Is Hosted Process just a more expensive Process licence?
It is documented as a superset that can also act as a Process licence, but Microsoft states that superset behaviour, and the associated admin centre setting, are not yet available. In the meantime Microsoft advises organisations with Process overage that their Hosted Process licences could cover to ignore the overage. Buy Hosted Process for the hosted machine, not as a Process substitute.

Sources & further reading

Done for you

Want this built for your business?

Tell us the workflow. We scope, build, and ship the agent with guardrails and the numbers to prove it worked. The scoping call is free.

Free scoping call. You own the code.

Request a scoping call

Was this page helpful?