Contents
- Fast answer
- Quick facts
- What this covers
- Why it matters
- Where to go next
- Outcomes
- Step by step
- The four SKUs you can buy today
- The rename map, including the plans you cannot buy
- User licences versus capacity licences
- Action limits and the daily meter
- Seeded licences and what they leave out
- Pay-as-you-go as a fifth option
- Picking the licence for a real automation
- At a glance
- Mistakes to avoid
- FAQ
Fast answer
There are four Power Automate SKUs you can buy today, all read from Microsoft's pricing page on 1 September 2026: Power Automate Premium at $15.00 per user a month, Power Automate Process at $150.00 per bot a month, Power Automate Hosted Process at $215.00 per bot a month, and the Process Mining add-on at $5,000.00 per tenant a month, every one of them paid yearly. Premium is a user licence. Process and Hosted Process are capacity licences allocated to a cloud flow or a machine rather than to a person. Alongside them sit a Free user licence, a 90-day self-service Trial, admin-managed 30-day trials, seeded entitlements inherited from Microsoft 365, Dynamics 365, Power Apps and Windows, and a pay-as-you-go meter billed through Azure at $0.60 per cloud flow run. Everything else you will find named in old documentation is retired: the Per-user plan became Premium, the Per-flow plan became Process, the Unattended RPA add-on became Process at the same price with more entitlements, and P1 and P2 stopped being purchasable or auto-renewable after 31 December 2020.
Facts last verified 2026-09
Quick facts
- Premium
- $15.00 user/month paid yearly, user licence (read 2026-09-01)
- Process
- $150.00 bot/month paid yearly, capacity licence
- Hosted Process
- $215.00 bot/month paid yearly, capacity licence
- Process Mining add-on
- $5,000.00 tenant/month paid yearly, Premium only
- Per-user plan
- Legacy. Replaced by Premium. Do not renew
- Per-flow plan
- Legacy. Replaced by Process. Do not renew
- Unattended RPA add-on
- Replaced by Process, same price, more entitlements
- P1 and P2
- Not purchasable or auto-renewable after 2020-12-31
- Daily actions
- 6k seeded M365, 40k Premium, 250k per Process licence
- Process stacking
- Up to 10 on one cloud flow, or a flow group across up to 25 flows
- Pay-as-you-go
- $0.60 cloud run, $0.60 attended desktop run, $3.00 unattended desktop run
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.
- 01The four SKUs you can buy today
- 02The rename map, including the plans you cannot buy
- 03User licences versus capacity licences
- 04Action limits and the daily meter
- 05Seeded licences and what they leave out
- 06Pay-as-you-go as a fifth option
Why does this matter now?
Power Automate licensing has been renamed twice and the old names outlive the SKUs by years. Search results, internal wikis, consultancy decks and half of Microsoft's own partner content still talk about Plan 1, Plan 2, Per-user, Per-flow and the Unattended RPA add-on, none of which you can buy. Meanwhile the real decision - user licence or capacity licence - is the one that decides whether a department rollout costs a few hundred dollars or a few thousand. This page reconciles the names against Microsoft's current documentation so the rest of the cluster can go deep on the individual questions.
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.
What you should be able to do after this
- Map every legacy plan name to its current SKU
- Tell user licences and capacity licences apart
- See which entitlement each licence actually carries
- Know which licence a given automation needs
How do you do it, step by step?
1. Start with what is on sale
Premium at $15.00 user/month, Process at $150.00 bot/month, Hosted Process at $215.00 bot/month, Process Mining add-on at $5,000.00 tenant/month, all paid yearly, all from Microsoft's pricing page on 1 September 2026. Process Mining is available only as an add-on to the Premium plan. If a name you have been given is not one of those four, it is either a free or trial tier, a seeded entitlement from another product, or a retired SKU.
2. Translate the legacy name
Microsoft Learn's deep dive on specific licenses carries the map. Power Automate Per-user plan was replaced by Power Automate Premium. Power Automate Per-flow plan was replaced by Power Automate Process. The Unattended RPA add-on was replaced by Process at the same price with more entitlements, and existing add-ons were upgraded so the two SKUs are now interchangeable. P1 and P2 are described as grandfathered and no longer available for purchase nor via autorenewal after 31 December 2020.
3. Decide user licence or capacity licence
A user licence entitles a person. A capacity licence is allocated to an automation and entitles that automation regardless of who touches it. If ten people each need to build premium-connector flows, that is ten Premium seats. If one flow needs to serve the whole organisation, a single Process licence allocated to that flow entitles unlimited users to it. Getting this wrong in either direction is where the money goes.
4. Size the daily action limit
Free and Microsoft 365 seeded users get 6,000 actions a day. Premium and Power Apps Premium seeded users get 40,000 a day. A Process licence gives a cloud flow 250,000 a day and stacks up to ten times on one flow for 2.5 million, or can be assigned to a flow group to share 250,000 a day across up to 25 flows with no stacking on the group. Microsoft's guidance is to estimate actions per run multiplied by runs per day and buy to cover it.
5. Check the seeded entitlement before buying anything
Microsoft 365, Dynamics 365, Power Apps and Windows licences all seed some Power Automate rights. They are narrow: Microsoft 365 seeds standard connectors only with no RPA, Power Apps Premium seeds premium connectors only when the flow is in context and associated with a Power App, and Windows seeds attended desktop flow local execution with no orchestration. Where the flow fits inside one of those, you do not need to buy anything.
6. Price pay-as-you-go as a real alternative
Microsoft's licensing news page publishes three meters effective 19 July 2022: $0.60 per cloud flow run, $0.60 per attended desktop flow run and $3.00 per unattended desktop flow run, billed through an Azure subscription. Very low-volume unattended automation is genuinely cheaper metered than licensed, and almost no comparison page mentions this option exists.
The four SKUs you can buy today
Everything purchasable in the Power Automate line fits on one short list, and it is worth committing to memory because most of the confusion in this space comes from names that are not on it. Power Automate Premium is $15.00 user/month paid yearly. Power Automate Process is $150.00 bot/month paid yearly. Power Automate Hosted Process is $215.00 bot/month paid yearly. The Power Automate Process Mining add-on is $5,000.00 tenant/month paid yearly and is available exclusively as an add-on to the Premium plan. All four figures were read from Microsoft's Power Automate pricing page on 1 September 2026.
Premium is the only user licence in that list. Process and Hosted Process are capacity licences, which Microsoft defines as automation-centric: they are allocated to a cloud flow, a machine, a hosted machine or a hosted machine group rather than assigned to a person, and they provide entitlements to that automation the way a user licence provides entitlements to a user. Process Mining is neither; it is a tenant-level capacity add-on that raises the process mining data storage ceiling.
Around the paid list sit the free and time-limited tiers. The Power Automate Free user licence covers creating and running cloud flows with standard connectors, without sharing, plus authoring and running desktop flows locally in attended mode. The self-service Power Automate Trial runs 90 days and carries Premium-equivalent capabilities except AI Builder credits and storage capacity, and it uniquely includes one unattended bot as well as one attended bot. Admin-managed trials of Premium, Process and Hosted Process run 30 days with the same entitlements and can be extended once.
Then there are seeded entitlements, which are not Power Automate purchases at all. Microsoft 365, Dynamics 365 Enterprise, Professional and Team Member, Power Apps Per-app, Premium, Plan 1 and Plan 2, and Windows licences all seed some Power Automate rights. They are covered in their own section below because they are the single most common reason an organisation buys a licence it did not need.
The rename map, including the plans you cannot buy
Microsoft has renamed this product line twice, and the old names are still in circulation in internal wikis, procurement templates, training material and a great deal of third-party writing. The authoritative map lives in Microsoft Learn's deep dive on specific licenses, under legacy licences, and it is short enough to reproduce in full.
The Power Automate Per-user plan was replaced by Power Automate Premium, which Microsoft says provides more entitlements for the same price. Already-purchased Per-user plan licences remain usable but are considered legacy and should not be renewed. The Power Automate Per-flow plan was replaced by Power Automate Process, with the same guidance: usable, legacy, do not renew. The Unattended RPA add-on was replaced by Power Automate Process at the same price with more entitlements, and Microsoft states that existing Unattended RPA add-ons have been upgraded to align with the Process licence, so that once assigned to an environment the two SKUs can be used interchangeably.
P1 and P2, commonly written as Plan 1 and Plan 2, are the hardest stop on the list. Microsoft's legacy table describes them as grandfathered licences no longer available for purchase nor via autorenewal after 31 December 2020. Organisations with renewals due on or after 1 January 2021 were required to transition to Power Automate Premium or Power Apps Premium. Organisations with active contracts that started before 1 January 2021 continue to be supported until the contract end date. That is five years of a retired SKU still generating search demand, which tells you how deeply the old names are embedded.
There is one more retired name worth pinning down because it causes real confusion: the legacy Per-flow plan and the current Process licence are not identical in behaviour even though one replaced the other. The legacy Per-flow plan carried 250,000 actions a day per plan, but Microsoft notes only one Per-flow plan could be allocated to a cloud flow, with no multi-allocation and no stacking of action limits. A modern Process licence stacks up to ten times on a single cloud flow. If you are running on legacy Per-flow plans, that is a live capability difference, not just a naming one.
User licences versus capacity licences
This is the decision that determines the size of the bill, and it is genuinely a decision rather than a lookup. A user licence entitles a person to build and run things. A capacity licence entitles an automation to exist and run regardless of who touches it. Microsoft's own framing: allocated to a cloud flow, a Process licence entitles it to use standard, premium and custom connectors while being accessed by unlimited users within the organisation, regardless of their user licence.
So a flow that forty people trigger costs either forty Premium seats at $15 or one Process licence at $150, and the second is cheaper by a factor of four. A department where ten people all build their own automations costs ten Premium seats and no amount of capacity licensing changes that, because capacity licences do not confer authoring rights. Most real organisations need both, in a ratio that depends entirely on how many builders they have versus how many shared flows.
Microsoft is explicit that the substitution only runs one way. Its guidance states that capacity licences are not meant to replace user licences within an environment, because some essential capabilities are only available to licensed users, including creating automations and running desktop flows attended or unattended. It adds two specifics that catch people out: allocating a Process licence to a machine still requires that the machine was registered by a Power Automate Premium user, and several monitoring pages in the Power Automate portal, including the work queue page, machine list page and desktop flow list page, display only to Premium users.
There is a mechanical step people forget. A capacity licence has to be assigned to the environment where the cloud flow or machine lives before it can be allocated to anything, and for cloud flows the flow must be in a solution for a Process licence to be assigned. Buying the licence is not the same as the flow having it, and the gap between those two states is where a lot of first-week troubleshooting goes.
Action limits and the daily meter
Every Power Automate licence carries a daily action allowance, reported in the admin centre as Power Platform Requests, and it is the constraint that bites before price does on any flow that loops. The published figures: 6,000 per user per day on the Free licence and on Microsoft 365 seeded licences, 40,000 per user per day on Premium and on Power Apps Premium and Dynamics 365 Enterprise or Professional seeded licences, and 250,000 per day per Process or Hosted Process licence allocated to a cloud flow.
Process capacity stacks, and this is the release valve for a heavy flow. Up to ten Process licences can be stacked on a single cloud flow, each adding 250,000 actions a day, for a ceiling of 2.5 million a day at $1,500 a month. The alternative shape is a flow group: one Process licence assigned to a flow group shares 250,000 actions a day across up to 25 cloud flows, with child flows explicitly added to the group. Stacking is not available for flow groups, and Microsoft notes that automatic capacity inheritance from parent to child flows is not available either, so every flow needing Process capacity must be directly assigned a licence or added to a group.
Microsoft's sizing method is worth following literally: estimate actions per run multiplied by runs per day, and buy Process licences to cover that volume. The admin centre's Power Platform request reports show each flow's actual daily action count, which is the only reliable way to find the flows that need stacking. Estimating from flow complexity by eye reliably underestimates, because loops multiply and nested loops multiply twice.
One caveat Microsoft attaches to all of these numbers: Power Platform requests are subject to higher limits during a transition period, with the details on the request limits page. That means the published allowances are the floor you should plan against rather than the enforcement you are experiencing today. Building a business case on the temporarily higher limits is a way to get a nasty surprise when the transition period ends.
Seeded licences and what they leave out
Seeded entitlements are Power Automate rights that arrive attached to a different product, and they are the reason the first honest step in any licensing exercise is to buy nothing. Microsoft lists the sources: Microsoft 365, Dynamics 365 Enterprise, Professional and Team Member, Power Apps Per-app, Premium, Plan 1 and Plan 2, and Windows licences. All of them entitle the user to create and run cloud flows with standard connectors.
The premium connector entitlement is where the restriction lives, and it is a strict one. Seeded licences can entitle premium and custom connectors only if the flow is in context and associated with the application from which the seeded licence is inherited. Microsoft's own example: a premium-connector flow owned by a Power Apps Premium user, associated to a Power App and triggered by that app, can be run by any user with a Power Apps licence. But if the cloud flow is isolated and has nothing to do with the application, a standalone Power Automate Premium licence must be purchased. In-context is doing enormous work in that sentence.
The daily action allowances differ sharply between seeded sources. Microsoft 365 and Dynamics 365 Team Member seed 6,000 actions a day per user. Power Apps Premium, Dynamics 365 Professional and Dynamics 365 Enterprise applications seed 40,000 a day. Power Apps Premium is also the only seeded licence that carries AI Builder credits, at 500 a month, and the only one carrying Dataverse storage, at 250 MB database and 2 GB file per licence.
Windows is the odd one out and the most misunderstood. Microsoft lists Windows licences under machine scope rather than user scope, with no daily action limit, no connectors of any kind, and attended RPA included with the footnoted limitation that it only includes local execution of desktop flow, with no orchestration. That single footnote is the honest answer to whether Power Automate for desktop is free, and it is covered in detail on the desktop licensing page in this cluster.
Pay-as-you-go as a fifth option
Microsoft publishes a metered alternative to licensing that hardly ever appears in third-party comparisons of Power Automate cost, including our own earlier pricing page. Three meters, published on Microsoft's licensing news site and effective 19 July 2022 with billing from 1 August 2022: $0.60 per cloud flow run, $0.60 per desktop flow run in attended mode, and $3.00 per desktop flow run in unattended mode. Billing runs through an Azure subscription, so it lands on a different invoice from your Microsoft 365 licences.
The break-evens are simple divisions and both are useful. Against a $15.00 Premium seat, a metered cloud flow is cheaper below about 25 runs a month. Against a $150.00 Process bot, metered unattended desktop runs are cheaper below fifty runs a month. Neither threshold is high, but plenty of genuinely valuable automations sit below them: month-end reconciliations, quarterly reporting, occasional exception handling, anything triggered by a rare business event.
The structural advantage of metering is that it removes capacity planning entirely. You do not have to decide how many bots, assign capacity to environments, or watch for overage. The structural disadvantage is that it removes the ceiling too: a flow that unexpectedly loops is a licensing non-event on a seat and a billing event on a meter. That asymmetry is the reason to meter only workloads whose run count you understand.
The practical reason pay-as-you-go gets overlooked is organisational rather than technical. In most companies Microsoft 365 licences and Azure subscriptions are bought by different people with different budgets and different approval paths, and the person pricing a Power Automate rollout is usually on the Microsoft 365 side. It is worth asking the question anyway, because for a low-volume portfolio the difference is not marginal.
Picking the licence for a real automation
Work through four questions in order and the answer falls out. First: does the flow use only standard connectors, and is it used by one person who already has Microsoft 365? If yes, you are done, the seeded entitlement covers it at 6,000 actions a day. Second: does it use premium connectors, and is it in context of a Power App or Dynamics 365 app the user is licensed for? If yes, the seeded entitlement covers it, subject to the in-context restriction.
Third: does the flow need to be authored, shared or owned by people in their own right? Every one of those people needs a Power Automate Premium licence at $15.00 a month. Fourth: does the flow need to serve users who are not licensed, or need more than 40,000 actions a day, or need to run desktop flows unattended? Those are the three doors into a Power Automate Process licence at $150.00 a month, allocated to the flow or to the machine as appropriate.
Add Hosted Process at $215.00 a month only when you specifically want Microsoft to run the Windows machine, which buys away the physical infrastructure and the machine management rather than buying more capacity. Microsoft documents Hosted Process as a superset of Process that can also act as one, but states that superset behaviour and its admin centre setting are not yet available, and advises organisations with Process overage that Hosted Process could cover to ignore the overage in the meantime. Do not buy it as a Process substitute today.
Add the Process Mining add-on at $5,000.00 per tenant a month only when the seeded 50 MB per Premium licence of process mining data storage, capped at 100 GB per tenant, is genuinely exhausted. There is no published intermediate step, so this is the sharpest cliff in the whole product line, and the honest advice is to measure the storage before you plan the programme rather than after.
At a glance
Every current and retired Power Automate SKU, with published price and status, read from Microsoft on 1 September 2026
| Licence | Type | Published price | Status and notes |
|---|---|---|---|
| Power Automate Premium | User licence | $15.00 user/month, paid yearly | Current. Replaced the Per-user plan |
| Power Automate Process | Capacity licence | $150.00 bot/month, paid yearly | Current. Replaced the Per-flow plan and the Unattended RPA add-on |
| Power Automate Hosted Process | Capacity licence | $215.00 bot/month, paid yearly | Current. Superset behaviour as a Process licence not yet available |
| Process Mining add-on | Tenant add-on | $5,000.00 tenant/month, paid yearly | Current. Available exclusively as an add-on to Premium |
| Power Automate Free | User licence | $0 | Current. Standard connectors only, 6,000 actions/day, no flow sharing |
| Power Automate Trial | User licence | $0, 90 days | Current. Premium capabilities except AI Builder credits and storage, plus one unattended bot |
| Admin-managed trial | User or capacity | $0, 30 days | Current. Trials of Premium, Process or Hosted Process, extendable once |
| Power Automate Per-user plan | User licence | Not published | Legacy. Usable, should not be renewed. Replace with Premium |
| Power Automate Per-flow plan | Capacity licence | Not published | Legacy. One per cloud flow, no stacking. Replace with Process |
| Unattended RPA add-on | Capacity add-on | Not published | Legacy. Upgraded to align with Process; the two are now interchangeable |
| Power Automate P1 and P2 | User licence | Not published | Retired. No purchase or autorenewal after 2020-12-31 |
| Pay-as-you-go cloud flow run | Azure meter | $0.60 per run | Current, effective 2022-07-19 |
| Pay-as-you-go attended desktop run | Azure meter | $0.60 per run | Current, effective 2022-07-19 |
| Pay-as-you-go unattended desktop run | Azure meter | $3.00 per run | Current, effective 2022-07-19 |
What mistakes should you avoid?
- Shopping for Plan 1 or Plan 2, which have not been purchasable since 31 December 2020
- Treating the Unattended RPA add-on as a separate product from Power Automate Process
- Buying user licences for an automation that a single capacity licence would cover for everyone
- Assuming a capacity licence removes the need for any user licence, when creating and running automations still requires one
- Ignoring pay-as-you-go entirely on low-volume automations
- Planning around the 5,000 seeded AI Builder credits that end on 1 November 2026
FAQ
- What Power Automate licences can I actually buy in 2026?
- Four paid SKUs: Premium at $15.00 user/month, Process at $150.00 bot/month, Hosted Process at $215.00 bot/month, and the Process Mining add-on at $5,000.00 tenant/month, all paid yearly, plus pay-as-you-go metering through Azure. There is also a Free user licence and a 90-day self-service Trial.
- What replaced the Power Automate Per-user and Per-flow plans?
- Power Automate Premium replaced the Per-user plan and Power Automate Process replaced the Per-flow plan. Microsoft Learn states both legacy licences remain usable but should not be renewed. Process also replaced the Unattended RPA add-on at the same price with more entitlements.
- Do I need a user licence if I have a Process licence?
- Yes. Microsoft states capacity licences are not meant to replace user licences, because creating automations and running desktop flows attended or unattended requires a licensed user. Allocating a Process licence to a machine still requires that the machine was registered by a Power Automate Premium user.
- How many actions does each licence allow per day?
- 6,000 per user on Free and Microsoft 365 seeded licences, 40,000 per user on Premium, and 250,000 per Process or Hosted Process licence allocated to a cloud flow. Process stacks up to ten times on a single cloud flow; a flow group shares one licence's 250,000 across up to 25 flows without stacking.
- Is there a pay-as-you-go option for Power Automate?
- Yes, billed through an Azure subscription and effective 19 July 2022: $0.60 per cloud flow run, $0.60 per attended desktop flow run and $3.00 per unattended desktop flow run. It is a genuine alternative to a licence for low-volume automations and it is rarely mentioned in third-party pricing comparisons.
- What is the Power Automate Free licence good for?
- Creating and running cloud flows with standard connectors only, at 6,000 actions a day, plus authoring and running desktop flows locally in attended mode. Microsoft notes you cannot share flows on the Free licence, which is usually the limit people hit first.
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.
Was this page helpful?

