A Microsoft 365 licence already lets you build and run cloud flows, but only with standard connectors, which in practice means Microsoft 365 services such as SharePoint, Outlook, Teams, Forms and Approvals. You need a paid Power Automate licence the moment a flow touches a premium connector, a custom connector, an HTTP action, Microsoft Dataverse, an on-premises data gateway or robotic process automation. The choice is then between Power Automate Premium, which licences a named user, and Power Automate Process, which licences a single flow or machine for everyone who uses it.
Most organisations meet Power Automate licensing at the worst possible moment: three hours into a flow that already works. This guide explains what the paywall actually is, how to tell whether you need per-user or per-flow licensing, and how to avoid buying twenty licences when you need two.
Home / Guides / Power Automate Licensing UK
Last updated: 3 August 2026. By Matty Hatton, founder of Digital Adaption.
The moment always looks the same. Someone in operations has spent an afternoon on a flow that reads a Microsoft Form, checks a value and writes a line into the production database. It works in test. Then they add the SQL Server action, a small diamond icon appears next to it, and saving produces a message about the flow using a premium connector their plan does not include. Ten minutes later this is a procurement question sitting on the desk of whoever signs the invoice, with none of the context attached.
That person has no way of knowing whether the right answer is eleven pounds a month or eleven hundred, and the gap has nothing to do with negotiation. It depends on which of two very different licensing models fits the flow. This guide covers what a Microsoft 365 licence genuinely includes, which design decisions push a flow over the premium line, per-user versus per-flow licensing, a decision table to hold against your own flows, the daily action limits that catch people out after they have bought the licence, and a checklist for diagnosing a block before you spend anything.
Power Automate is sold twice, to two different buyers, and the two stories collide inside one product.
The first is Power Automate as an extension of Microsoft 365. Microsoft's own wording is that limited use rights are included with select Office 365 licences to let users customise and extend Office 365 for personal productivity scenarios. That is the seeded entitlement, and it was never meant to be an integration platform. The second is Power Automate as a standalone product competing with dedicated integration and RPA tooling, reaching into databases, ERP systems, REST endpoints and legacy desktop applications, priced accordingly.
The boundary is enforced by connector classification. Every connector is labelled Standard or Premium, and that label is the tollgate. It is not a judgement about difficulty or data volume. The HTTP connector illustrates it: Microsoft classes it as Premium for Power Automate and Power Apps, but Standard for Azure Logic Apps, which run the same underlying engine. The line is commercial, not technical, which is why it feels arbitrary when you hit it.
The second source of confusion is Microsoft's own renaming. The Per-user plan is now Power Automate Premium and the Per-flow plan is now Power Automate Process, while P1 and P2 stopped being available after 31 December 2020. Much of the content ranking for licensing questions still quotes plans Microsoft no longer sells. The current position is in Microsoft's types of Power Automate licenses reference and the Power Platform Licensing Guide.
Users on Microsoft 365 Business Standard, Business Premium, E1, E3, E5 or the equivalent education and frontline SKUs already hold real Power Automate rights, narrower than most people assume and broader than the panic caused by a premium warning suggests.
| Included with a Microsoft 365 licence | Not included |
|---|---|
| Creating and running automated, scheduled and instant (button) cloud flows | Premium connectors, with a carve-out for Dataverse for Teams environments |
| Standard connectors: SharePoint, Outlook and Exchange, Teams, OneDrive for Business, Excel Online (Business), Forms, Planner, Approvals and similar | Custom connectors outside of app context |
| Sharing and co-owning flows | The on-premises data gateway outside of app context |
| Approvals, including multi-stage approvals | Robotic process automation, meaning desktop flows |
| 6,000 Power Platform requests per user per 24 hours as the official limit | AI Builder, process mining and task mining |
| Solution-aware flows where the environment has a Dataverse database attached | Business process flows outside of app context |
Note the difference between that seeded entitlement and the free Power Automate licence anyone with a work or school account gets. The Free licence builds and runs standard-connector flows but cannot share them, which is why so much departmental automation quietly lives in one person's account and dies when they leave.
A large share of genuinely useful SME automation never crosses the premium line. A shared inbox that receives supplier queries, routes them for approval and files the outcome is standard-connector work throughout, which is why building an approval flow from a shared mailbox is usually the first automation I recommend. It removes real handling time and costs nothing you have not already bought.
Five design decisions push a flow over the line. If none apply, you do not need to buy anything.
Anything reaching a line of business system. SQL Server, Azure SQL, MySQL, Oracle Database, Salesforce, ServiceNow, SAP, Azure Blob Storage and SFTP are all Premium, along with several hundred others. Microsoft maintains the full list of premium tier connectors, and the designer shows a diamond badge on the card. Check the badge before you design, not after.
The plain HTTP connector and HTTP with Microsoft Entra ID (preauthorized) are both Premium for Power Automate. This catches people because HTTP feels like a built-in primitive rather than a connector. Any flow calling a REST API with no prebuilt connector is a premium flow.
Wrap your own API in a custom connector and running any flow that uses it needs a premium or trial licence. The Microsoft 365 seeded entitlement does not cover custom connectors, and Power Apps and Dynamics 365 licences cover them only where the flow is genuinely in context of, and associated to, the app.
The Microsoft Dataverse connector is Premium. This surprises people who think of Dataverse as part of the platform rather than a data source. If your flow reads or writes Dataverse rows through the connector, it is a premium flow.
Desktop flows are premium in every direction, as is the on-premises data gateway, the component a flow needs to reach a server in your own building rather than a cloud endpoint. For manufacturers still running an on-premises ERP, that alone usually settles the question.
The question people actually have is not "what plans exist" but "what do I have to buy for the thing in front of me".
| If your flow does this | You need this |
|---|---|
| Reads and writes SharePoint, Outlook, Teams, OneDrive, Excel Online (Business), Forms, Planner or Approvals only | Nothing extra. The Microsoft 365 seeded entitlement covers it |
| Queries or updates SQL Server, Oracle, MySQL or another database | Power Automate Premium for the owner, or Power Automate Process on the flow |
| Calls a REST API using an HTTP action | Power Automate Premium or Power Automate Process |
| Uses a custom connector built for your ERP or a supplier portal | Power Automate Premium or Power Automate Process |
| Reads or writes Microsoft Dataverse tables | Power Automate Premium or Power Automate Process |
| Reaches an on-premises server through the data gateway | Power Automate Premium or Power Automate Process |
| Runs a desktop flow attended, on the maker's own machine | Power Automate Premium (one attended bot per licence) |
| Runs a desktop flow unattended, overnight, on a server you own | Power Automate Process allocated to the machine, plus a Premium user to register it |
| Runs unattended RPA with no machine of your own to manage | Power Automate Hosted Process |
| Is an automated or scheduled premium flow with one owner | One Premium licence, for the owner only |
| Is an instant premium flow (button or Power Apps trigger) run by 30 people | Either 30 Premium licences, or one Process licence on the flow |
| Needs process mining or task mining | Power Automate Premium, plus the process mining add-on at tenant scale |
| Uses AI Builder for document or form processing | Premium or Process, which include AI Builder credits, plus credit add-ons at volume |
The two italicised rows are where the money is won or lost.
Microsoft's rule is set by the trigger type, and it is the most commercially significant fact in the whole subject.
The consequence is stark. A premium automation running on a schedule or a record change can serve a 200-person business on one licence. The same logic delivered as a button everyone presses needs 200 licences, or a Process licence on the flow instead. Before buying, ask whether the instant trigger is necessary, or whether the same outcome can come from writing to a list and letting an automated flow pick it up. That single design change moves the flow from a per-user cost to a single-owner cost, which is usually the largest saving available on the whole question.
Two warnings. Do not use the rule to route many users' work through a single licensed account to cut licence count. Microsoft calls that multiplexing and treats it as a violation, drawing the line at users who merely consume output rather than triggering it. And an automated flow depends on its owner's licence staying active: if the owner leaves and the licence is reclaimed, the flow stops. Business-critical premium flows should be owned by a service account, or at least co-owned.
Power Automate Premium is a named-user licence covering unlimited cloud flows that user creates, runs and shares, with standard, premium and custom connectors, plus attended RPA with one bot, process mining, AI Builder credits and a modest Dataverse allocation. This is what people mean by a "power automate premium license", and it is the right default for makers.
Power Automate Process is a capacity licence allocated to a specific cloud flow, or to a machine where it becomes an unattended bot. Allocated to a flow, it lets that flow use standard, premium and custom connectors while being accessed by unlimited users across the organisation, whatever their own licence. The flow must sit in a solution for the licence to be assignable. It carries a far larger daily action allowance, and up to ten Process licences can be stacked on one flow, or one licence shared across a flow group of up to 25 flows.
Power Automate Hosted Process is the same idea, with each licence also supporting a Microsoft-hosted virtual machine on Azure, so you get unattended RPA without provisioning or patching a VM. The legacy Per-user and Per-flow plans still function if you hold them, but Microsoft treats them as legacy and recommends replacing them at renewal.
On the Microsoft UK Power Automate pricing page, checked on 3 August 2026, the listed figures were Power Automate Premium at GBP 11.50 per user per month, Power Automate Process at GBP 115.30 per bot per month and Power Automate Hosted Process at GBP 165.30 per bot per month, all quoted paid yearly and excluding VAT. Treat those as a shape, not a quote: they are list prices before discount, they move, and resellers price differently. The durable fact is the ratio. One Process licence costs roughly what ten Premium licences cost, and that ratio is the whole decision.
Ignore the plan names and answer two questions about your actual estate.
How many people need to build? Makers need user licences, and capacity licences do not replace them. Microsoft is explicit that some capabilities are only available to licensed users, including creating automations and registering machines for RPA. In most SMEs the honest answer is two to four makers, not twenty.
Is premium usage concentrated or spread? If a few flows carry all the premium connectors and many people depend on them, buy Process for those flows. If premium usage is spread across many flows owned by a handful of people, buy Premium for those people.
The common failure mode is buying Premium for everyone who will ever touch a flow, because it is the easiest line to draw. It is also the most expensive line to draw, since most of those people never own a premium flow and never trigger one. If the prior question is whether the automation justifies any licence, the Replace-It Calculator frames it faster than a spreadsheet.
Buying a licence answers the connector question, not the throughput question, and that is where the second surprise lives. Every trigger and every action counts as a Power Platform request, including the ones that do not feel like requests: initialise variable, compose, condition evaluation, HTTP actions, and each iteration inside an apply-to-each loop. Retries count. Pagination counts. Failed actions count. A flow looping over 500 rows with four actions per row consumes over 2,000 requests in one run.
| Licence | Official daily limit | Transition period limit |
|---|---|---|
| Microsoft 365 / Office 365 seeded | 6,000 per user | 10,000 per cloud flow |
| Power Automate Free | 6,000 per user | 10,000 per cloud flow |
| Power Automate Premium | 40,000 per user | 200,000 per cloud flow |
| Power Automate Process | 250,000 per licence | 500,000 per licence |
| Power Automate Hosted Process | 250,000 per licence | 500,000 per licence |
| Dynamics 365 Enterprise or Professional | 40,000 per user | 200,000 per cloud flow |
| Dynamics 365 Team Member | 6,000 per user | 10,000 per cloud flow |
All organisations are currently in a transition period during which the higher limits apply and enforcement is loose. Microsoft's guidance is to build against the official limits, because the transition ends six months after the admin centre usage reports reach general availability. Building a flow that only works under transition limits is borrowing against a date you do not control. Limits are also not pooled: eight users on Microsoft 365 licences get 6,000 requests each, not 48,000 between them.
Microsoft's requests limits and allocations page carries the detail, and the Power Platform admin centre produces a downloadable per-user and per-flow request report that is the correct evidence base for a capacity purchase. Estimate actions per run multiplied by runs per day before you buy, not after you get throttled.
Power Apps and Dynamics 365 licences carry premium connector rights, but only for flows in context of, and associated to, the app. Microsoft's own example: a flow reading and writing Azure DevOps in service of a Dynamics 365 case escalation is covered, while the same user's separate flow updating an Oracle database is not, and needs a standalone licence. For automated and scheduled flows the link to the app must be established explicitly.
Microsoft's licensing FAQ excludes premium connectors from Microsoft 365 seeded rights, then carves out Dataverse for Teams environments. If your automation lives inside a Teams-embedded app, check that carve-out before assuming you need Premium.
Child flows are licensed in their own right, and Process capacity does not cascade from a parent to its children. Each flow needing capacity must be assigned a licence directly or added explicitly to a flow group. A parent that looks correctly licensed while its child fails is a common and confusing failure.
Flows owned by a service principal draw on a separate tenant-level pool, and Power Automate's base pool is 25,000 requests per day for the whole tenant with no per-licence accrual. That is less generous than people expect when they move ownership to a service account for continuity. Likewise, if an instant premium flow is shared with guests from other tenants, you cannot verify what their home tenant entitles them to, so licence the flow with Process capacity rather than hoping.
There are two trials: a 90-day self-service trial a user starts from the portal, and a 30-day admin-managed trial provisioned from the Microsoft 365 admin centre and extendable once. Both create the same failure, a business-critical flow quietly stopping on a date nobody diarised. Separately, a cloud flow not triggered within 90 days can be turned off, though flows owned by premium-licensed users or carrying capacity licences are exempt.
Work through this before raising a purchase request. A good number of "we need to buy Premium" conversations end somewhere in this list instead of at a purchase order.
Licensing questions rarely arrive alone. They come attached to a half-built flow, an undocumented dependency on one person's account, and a process nobody has written down. If that is your position, Digital Adaption provides Power Automate consultancy for UK organisations, covering approval workflows, controlled automation and the governance around them, including settling the licensing position before anyone commits to a plan. The useful output is usually not a cheaper licence but fewer flows doing more, owned properly, with the premium requirement designed out where it was never needed.
If you are still deciding whether to bring anyone in, what a Power Automate consultant actually does sets out the scope honestly. To start with something that costs nothing to licence, the shared mailbox approval flow guide is standard-connector work end to end. On the LiquidLipo engagement, automation saved eight hours a week, and that is the number that should drive the licence conversation rather than the other way round. Where automation sits inside a wider ERP or reporting problem, see the full service list.
You need one if your flow uses a premium connector, a custom connector, an HTTP action, Microsoft Dataverse, the on-premises data gateway or robotic process automation. Flows that stay inside Microsoft 365 services such as SharePoint, Outlook, Teams, Forms and Approvals run on rights already included with your Microsoft 365 licence.
Premium is a user licence covering one named person for unlimited flows they own, including premium connectors and one attended RPA bot. Process is a capacity licence allocated to a single cloud flow or machine, covering everyone who uses that flow whatever their own licence, with a much higher daily action allowance. Choose Premium when premium usage is spread across a few makers, and Process when it is concentrated in a few flows used by many people.
Yes. Microsoft classes the HTTP connector and HTTP with Microsoft Entra ID (preauthorized) as Premium for Power Automate, while the same operations are Standard in Azure Logic Apps. A flow calling a REST endpoint through an HTTP action needs a Power Automate Premium user licence or a Process licence on the flow.
Only for instant flows. Automated and scheduled flows run in the owner's context, so if the flow uses a premium connector, only the owner needs the Premium licence. Instant flows, including button and Power Apps triggers, run in the context of the person invoking them, so each of those users needs a licence. Allocating a Process licence to the flow covers all of them instead.
On Microsoft's UK pricing page, checked on 3 August 2026, Power Automate Premium listed at GBP 11.50 per user per month paid yearly, Power Automate Process at GBP 115.30 per bot per month, and Power Automate Hosted Process at GBP 165.30 per bot per month. Microsoft revises these regularly, so verify on the official page before committing. The more durable fact is that one Process licence costs roughly ten Premium licences.
They were renamed. The Per-user plan became Power Automate Premium and the Per-flow plan became Power Automate Process, with more entitlements at the same price point. Existing licences under the old names still work but count as legacy and should be replaced at renewal. P1 and P2 stopped being available after 31 December 2020, which is why so much third-party content quotes retired plan names.
Power Automate licensing is not complicated once you know that connector classification is the tollgate and trigger type decides who pays. It becomes expensive when those two facts arrive after the flow is built, the users are trained and the process depends on it. Thirty minutes of design review beforehand beats any negotiation afterwards.
If you have a flow stuck behind a premium warning, a quote you are not sure about, or an automation estate that has grown without anyone owning the licence position, I will look at it and tell you what you actually need. Book a 30-minute call and bring the flow, not the quote.
Matty Hatton is the founder of Digital Adaption, an ERP and data consultancy based on the Wirral, working across the North West and the UK. He holds an MSc in Digital Transformation and IT Strategy from Manchester Metropolitan University and is Microsoft PL-200 certified. LinkedIn | Get in touch