Is Power Automate Worth It? What It Costs and When to Pay
Power Automate cost depends far less on headcount than on what you are actually trying to automate. The platform is included with most Microsoft 365 plans, covering automated, scheduled and button flows, standard connectors and a daily action allowance, and for straightforward automation that entitlement is genuinely enough.
That last part is where the real cost hides. The most common licensing mistake we see is not overspending. It is people making their lives considerably harder in order to stay within the seeded entitlement, and building fragile automation as a result.
The example that comes up repeatedly is the convert to PDF action. It sits in the OneDrive for Business connector rather than the SharePoint one, so people copy a file out of SharePoint into OneDrive, convert it, then move it back. Three steps and two extra failure points, to avoid a licence that would have made it one step.
There is also a rule that saves organisations money and is widely missed: if a flow is associated with a Power Apps application, it is already covered by the Power Apps licence. That has a specific boundary, which is worth understanding before you assume it applies.
Quick summary
The licensing decision is less about price and more about what you are willing to work around:
The question worth asking is not whether Power Automate is worth paying for in the abstract. It is whether the automation you actually need can be built cleanly on what you already own.
What you get without paying anything
Most Microsoft 365 and Office 365 plans include limited Power Automate rights, intended for personal productivity and light customisation. That covers creating and running automated, scheduled and button flows, access to standard connectors, and an allowance of 6,000 actions per user per day.
Standard connectors cover the Microsoft 365 estate and a reasonable set of common services: SharePoint, Outlook, Teams, OneDrive, Excel, Forms, Planner and similar. For a great many everyday automations, that is entirely sufficient.
What is not included is access to premium connectors, robotic process automation, AI Builder, business process flows within app context, custom connectors within app context, and on-premises gateways within app context. Microsoft’s own Power Automate licensing FAQ sets the boundaries out in full.
The mistake that costs more than the licence
The most common licensing mistake we see is not organisations overspending. It is organisations contorting their automation to stay inside the seeded entitlement, and paying for it in complexity instead.
The convert to PDF action is the example that comes up most. It lives in the OneDrive for Business connector rather than the SharePoint one. So rather than licensing properly, people build a flow that copies the file from SharePoint into OneDrive, converts it, moves the converted file back to SharePoint, and then tidies up the copy left behind in OneDrive.
That flow works. It also has several more steps than it needs, more points at which it can fail, more permissions to get right, and considerably more to explain to whoever maintains it next. When it breaks, and it will, somebody spends an afternoon working out why a document conversion involves OneDrive at all.
This is the cost that never appears in a licensing comparison. The licence is a line on an invoice. The workaround is a permanent tax on everyone who touches that flow afterwards.
The rule that saves money and gets missed
Before assuming you need to buy Power Automate licences, check whether you already have the rights.
Power Apps Premium, Power Apps per app and Power Apps pay-as-you-go licences all include Power Automate use rights for automating workflows associated with Power Apps applications. If your flows exist to support an app you have already licensed, they are covered.
The boundary is the phrase “within the context of the app”, and it is specific. For both triggers and actions, a flow inside a Power Apps application can connect to any data source already within the use rights of that application, or interact directly with the app through a built-in trigger or action.
Microsoft’s own example makes it clear. A user with a Power Apps licence runs an app using a SQL Server database, and has flows that read from or write to that same database, or that send a push notification to the app. All covered. The same user then wants a flow that updates an Oracle database, entirely unrelated to the app and touching none of its data sources. That flow needs a full Power Automate licence.
So the test is not whether a flow exists near an app. It is whether the flow uses the app’s data sources or talks to the app itself. Isolated automation needs its own licence, and treating this rule loosely is how organisations end up under-licensed at audit rather than saving money.
This is also why the licensing decisions across the Power Platform are best made together rather than product by product, which is covered in our post on why we now recommend Power Apps Premium first.
Why we generally lean towards premium
Our position on Power Apps licensing is that premium deserves consideration from the outset, and that view largely carries across to Power Automate.
The reason is practical rather than technical. Power Automate is a key tool, and working within the seeded entitlement means accepting constraints on what you can build before you have properly understood what you need to build. That is the wrong way round. Designing automation while mentally excluding every premium connector produces solutions shaped by the licence rather than the problem, and the convert to PDF workaround is what that looks like in practice.
Premium removes that constraint. You design the flow that solves the problem, rather than the flow the entitlement permits.
To be clear about the obvious objection, recommending the paid licence is not a comfortable position for a partner and it is not one taken lightly. The honest case rests on what the alternative costs in maintenance, fragility and time, which are real costs that simply do not appear on a licensing comparison.
When the free entitlement is genuinely the right answer
There is a clear case where paying for premium is waste, and it is worth stating plainly.
If your flows are very simple and use only Microsoft 365 services, the seeded entitlement is the correct answer. A flow that posts a Teams message when a Form is submitted, moves a file when a SharePoint item is approved, or sends a reminder on a schedule needs nothing beyond what you already own. Buying premium licences for that pattern of use adds cost without adding capability.
The signal to watch for is not the number of flows. It is whether you are starting to design around the licence. The first time someone suggests routing a file through OneDrive to reach an action, or asks whether a flow could avoid a particular system, the constraint has started to shape the solution and the calculation has changed.
Power Automate cost in the UK
As of August 2026, UK list pricing starts at £11.50 per licence per month for the Power Automate per user plan, £12.08 per licence per month for Power Automate Premium, and £92.28 per licence per month for the per flow plan.
Two things fall out of those numbers that are worth pausing on.
The gap between the per user plan and Premium is 58 pence. For that difference, Premium adds attended robotic process automation through desktop flows, alongside unlimited cloud flows. If you are already prepared to pay for a per user licence, choosing the plan without RPA to save under a pound a month rarely makes sense, and it is the sort of decision that quietly limits what your team can build a year later.
The per flow plan works differently and is easy to misread. It licenses a single process rather than a person, with reserved capacity, and serves everybody who needs that process. At £92.28 against £12.08, the arithmetic puts the crossover at roughly eight users. Below that, licensing the individuals is cheaper. Above it, a single heavily used process is cheaper licensed per flow. Organisations tend to default to per user licensing without checking whether a shared process would be better served the other way round.
Worth knowing that the per-user licence is not the only cost that can appear. Unattended robotic process automation is a separate add-on, AI Builder runs on credits, and Dataverse capacity sits outside the licence entirely.
The managed environments catch
One point worth flagging for anyone tightening up governance, because it surprises people.
If you run flows inside a Managed Environment, every user running a Power Automate cloud flow needs a Power Apps Premium licence, a Power Automate Premium licence, or a Dynamics 365 Enterprise licence carrying premium Power Apps rights. The seeded Microsoft 365 entitlement is not sufficient there.
That matters because Managed Environments are exactly what organisations turn on when they start taking Power Platform governance seriously. Improving your governance posture can therefore change your licensing position, and it is better to know that before the invoice arrives than after. The wider version of this problem is covered in why Power Platform governance fails in growing organisations.
Not sure whether you need to pay for Power Automate?
We will look at what you are automating, check whether your existing Power Apps or Dynamics licences already cover it, and tell you where premium would genuinely pay for itself. If your flows are simple enough to run on what you already own, we will tell you that.
The bottom line on Power Automate cost
Power Automate is worth paying for when the automation you need cannot be built cleanly on standard connectors, and it is not worth paying for when it can. That sounds obvious, but it is not how the decision usually gets made. What normally happens is that an organisation decides not to spend, and then quietly absorbs the cost as complexity instead.
Check what your existing licences already cover, because flows tied to a Power Apps application may need nothing further. Be honest about whether you are designing solutions or designing around a licence. And if very simple Microsoft 365 automation is all you need, keep your money.
Our Business Process Automation Services team works through exactly this, usually as part of a wider conversation about what is worth automating in the first place.
STRAIGHT ANSWERS
Frequently asked questions
Is Power Automate free with Microsoft 365?
Power Automate rights are included with most Microsoft 365 and Office 365 plans, covering automated, scheduled and button flows using standard connectors, with an allowance of 6,000 actions per user per day. That is genuinely useful for everyday automation. Premium connectors, robotic process automation, AI Builder and business process flows are not included.
Do I need a Power Automate licence if my flows are part of a Power App?
Often not. Power Apps Premium, per app and pay-as-you-go licences include Power Automate use rights for flows associated with the app, provided those flows stay within the context of that application. In practice that means using data sources already covered by the app’s use rights, or interacting with the app through a built-in trigger or action. A flow unrelated to the app requires its own Power Automate licence.
What does “within the context of the app” actually mean?
It means the flow has a genuine relationship to the application. Microsoft’s own example is a Power App using a SQL Server database, where flows reading from or writing to that same database are covered. If the same user builds a flow updating an unrelated Oracle database that never touches the app or its data sources, that flow needs a full Power Automate licence. The test is the data source and the interaction, not proximity.
How much does Power Automate cost in the UK?
As of August 2026, UK list pricing starts at £11.50 per licence per month for the per user plan, £12.08 for Power Automate Premium, and £92.28 for the per flow plan. Premium is only 58 pence more than the per user plan and adds attended robotic process automation, so the cheaper option is rarely the better one if you are paying either way.
What is the difference between the per user and per flow plans?
The per user plan licenses a person to build and run flows. The per flow plan licenses a single process with reserved capacity, available to everyone who needs it, regardless of headcount. At £92.28 against £12.08, the crossover sits at roughly eight users, so a process needed by a large group is often cheaper licensed per flow than by licensing each person individually.
When should we not pay for Power Automate premium?
When your flows are simple and use only Microsoft 365 services. Posting a Teams message from a Form submission, moving a file after a SharePoint approval, or sending a scheduled reminder all run perfectly well on the seeded entitlement. Paying for premium in that situation adds cost without adding capability.
Why do premium connectors matter so much?
Because avoiding them tends to cost more than licensing them. The convert to PDF action, for instance, sits in the OneDrive for Business connector rather than SharePoint, so organisations build flows that shuttle files out to OneDrive and back purely to avoid a licence. The result is a longer flow with more failure points and more to maintain, which is a permanent cost rather than a one-off saving.
Does turning on Managed Environments change our licensing?
Yes, and it catches people out. Every user running a Power Automate cloud flow inside a Managed Environment needs Power Apps Premium, Power Automate Premium, or a Dynamics 365 Enterprise licence with premium Power Apps rights. The seeded Microsoft 365 entitlement is not sufficient, so tightening governance can change your licensing position.
KEEP READING
Related posts
Power Apps Licensing: Why We Now Recommend Premium First
Microsoft Secure Score: Why a Good Number Doesn’t Always Mean Good Security No Content…
The Power Platform CoE Starter Kit Is No Longer Maintained. It Is Still Worth Running.
Microsoft Secure Score: Why a Good Number Doesn’t Always Mean Good Security No Content…