Back to Blog

Power Automate Licensing in Australia - What You Need

May 24, 2026•10 min read•Michael Ridland

Power Automate licensing is the single most confusing part of the Power Platform. Microsoft has redesigned it three times since 2021, the documentation is written for licensing specialists, and the difference between what is "included" in your Microsoft 365 subscription and what costs extra is genuinely hard to work out without a spreadsheet.

We get this question from Australian businesses every week, usually after they have either (a) bought too much licensing and want to know if they can cancel some, or (b) bought too little and are getting throttled in production. This post is the honest answer to both groups, with real AUD pricing as of May 2026.

The Short Version

If you only remember three things from this article, make them these:

  1. Microsoft 365 includes basic Power Automate. Most small businesses never need to pay more.
  2. The moment you touch a "premium connector" (Dataverse, SQL Server, SAP, Salesforce, ServiceNow, custom HTTP endpoints), you need a Power Automate Premium licence or a Process licence.
  3. Per-flow licensing exists and is wildly underused. For most enterprise scenarios, it is far cheaper than per-user.

If those three lines saved you reading the rest, good. If they raised more questions, keep going.

What You Already Have - Microsoft 365 Included Rights

Almost every Australian business with Microsoft 365 already has some Power Automate entitlement. This is the starting point, and the entitlement is more useful than most teams realise.

If you have any of these plans, you get the basics included:

  • Microsoft 365 Business Basic, Standard, or Premium
  • Microsoft 365 E1, E3, or E5
  • Microsoft 365 F1 or F3 (with limits)
  • Office 365 E1, E3, or E5

What is included

  • Cloud flows using standard connectors (Outlook, SharePoint, Teams, OneDrive, Excel, Forms, Planner, Lists, To Do)
  • Automated, instant, and scheduled flows
  • Approvals
  • Basic data loss prevention policies

What is not included

  • Premium connectors (SQL Server, Dataverse, SAP, Salesforce, ServiceNow, Oracle, custom connectors, HTTP requests to arbitrary endpoints)
  • Desktop flows (Power Automate Desktop running in unattended mode)
  • AI Builder credits
  • Process mining
  • Business process flows
  • Higher per-user request limits

Here is the thing that catches people out - a flow that calls a single premium connector once means the whole flow needs premium licensing. There is no "one cheeky API call" allowance.

The Premium Tiers in 2026

Microsoft renamed and restructured the plans in 2023 and tweaked them again in 2025. Here is where we are in 2026.

Power Automate Premium (per user) - approx $24.10 AUD per user per month

This is the per-user licence for individuals who need premium connectors. It includes:

  • All standard and premium connectors
  • Custom connectors
  • On-premises data gateway
  • Power Automate Desktop in attended mode
  • AI Builder credits (limited)
  • Dataverse for Power Automate (limited storage)

This is the right pick when you have a small number of named users (a finance team, an operations lead, an admin team) who need to run premium flows. Once you start needing it for 30+ people, do the maths against the per-flow plans.

Power Automate Process (per flow) - approx $225 AUD per flow per month

This licences a specific cloud flow (or a desktop flow in unattended mode), regardless of how many users trigger or interact with it. Includes everything in Premium but tied to the flow, not the user.

This is the underused one. If you have a flow that processes invoices for the whole company, or an automation that runs nightly across your CRM, you do not need to license every person who might benefit. You license the flow once. We have saved clients tens of thousands of dollars a year by moving them off per-user to per-flow plans.

Power Automate Hosted Process - approx $310 AUD per bot per month

This is per-flow plus a Microsoft-hosted machine for unattended desktop flows. If you are doing RPA (robotic process automation) where a bot runs in the background scraping a web app or driving a legacy thick-client system, this is what you need. No need to manage your own VMs.

Pay-as-you-go - around $0.95 AUD per flow run

You can run premium flows under an Azure subscription on a pay-as-you-go basis. The pricing looks small but adds up quickly if your flow runs frequently. Useful for low-volume edge cases. Not useful for anything that runs more than a few hundred times a month.

Comparison Table

Plan Cost (AUD, approx) Best for Watch out for
Microsoft 365 included $0 (already paid) Standard connector workflows, approvals, notifications Touching one premium connector breaks the licence
Premium per user $24.10 per user per month Small teams who all use premium connectors Multiplies fast across departments
Process (per flow) $225 per flow per month Department or org-wide automations You still need the right governance to track which flows are licensed
Hosted Process $310 per bot per month Unattended RPA without managing VMs Bot needs to be utilised - quiet bots are wasted money
Pay-as-you-go $0.95 per run Very low volume premium flows Cost blows out fast above ~200 runs per month

Prices vary by EA, CSP partner, and any discount your organisation has negotiated. Treat these as list price reference points.

The Mistakes We See Most Often

Mistake 1 - Buying per-user when per-flow is cheaper

A finance team of 12 buys Premium per-user at $24.10/month each. Total - $289 per month. The actual scenario is one invoice processing flow that runs in the background. A single Process licence at $225/month would have done the job. Annual saving - $768.

Multiply that across an enterprise with 40 automated processes and you are looking at $30k-$80k a year being wasted on the wrong SKU.

Mistake 2 - Not realising HTTP connector is premium

Teams build a flow that calls an external REST API using the HTTP action. They test it on their personal account, it works, ship it. Six months later, IT does a licensing audit and discovers half the organisation is using flows that should have been licensed as Premium. Cue retroactive billing or, worse, flows breaking when admins enforce policy.

Mistake 3 - AI Builder credits surprise

AI Builder credits are bundled into Premium licences in small amounts - around 5,000 credits per user per month. Document processing burns through these fast. A single invoice extraction might cost 10-50 credits. If you are processing 500 invoices a month, you are out of credits by the 100th. You then need an AI Builder add-on capacity, which is around $750-$1,200 AUD per month for the smallest tier.

Mistake 4 - Forgetting the on-premises data gateway is licensed

If you connect Power Automate to an on-prem SQL Server or file share, you need an on-premises data gateway. The gateway itself is free to install, but every flow that uses it counts as premium. We have seen teams install the gateway, get flows working, then have IT shut it all down once licensing catches up.

Mistake 5 - Per-user licences for service accounts

You cannot legally licence a service account with a per-user plan that is shared by multiple humans. Microsoft licensing terms require named-user assignment. We see this constantly - one "[email protected]" account running 40 flows used by 200 people. Eventually this comes up in audit. Move those flows to per-flow Process licences before it does.

How to Work Out What You Actually Need

Walk through your existing or planned flows and answer these questions for each:

  1. Does the flow touch any premium connector or custom HTTP endpoint? If no, you are fine on Microsoft 365. If yes, continue.
  2. Is the flow used by a small, identifiable group of named people (under 10)? If yes, Premium per user might be cheapest.
  3. Is the flow more like infrastructure - it runs in the background or serves a wide group? If yes, Process per flow is almost always cheaper.
  4. Is it desktop flow / RPA driving a UI? If yes, Hosted Process if Microsoft can manage the machine, otherwise Process and your own VM.
  5. Is it very low volume (under 100 runs a month) and you do not want a commitment? If yes, pay-as-you-go.

Repeat for each flow. Group by SKU. That is your shopping list.

The trap is that this exercise rarely happens before licences are bought. People buy a few Premium per-user licences, deploy a flow, realise more people need it, buy more licences, and end up over-licensed and over-paying within 18 months. Doing this audit even once a year is worth it.

What About Power Automate Desktop for Free

Microsoft made Power Automate Desktop free for Windows 10 and 11 users in 2021. This is real and useful. You can build and run desktop flows on your own machine for free in attended mode. The catch is two-fold.

First, unattended mode (running on a server in the background) requires either Premium per-user or Process licensing, plus a machine to run on.

Second, the free version saves flows to OneDrive personal, not to your tenant. There is no central management, no version control, no governance. This is fine for one analyst automating their own work, not fine for anything you want to support across an organisation.

If you are running anything serious in production, you want the licensed version, with flows stored in your tenant, governed by your DLP policies, monitored properly. Our Power Automate consultants help clients move from a sprawl of personal-account scripts to a governed automation estate every quarter.

Government and Education Pricing

Australian government and education customers get materially better pricing through the Microsoft Volume Licensing channels. We have seen Premium per-user as low as $17-$19 AUD per user per month for state government departments under their negotiated agreements, and Process licences discounted similarly. If you are in the public sector, talk to your Microsoft account manager before going off published prices.

Annual vs Monthly Commitments

Most Microsoft licences are annual commitments billed monthly. You can choose monthly commitments for a 20% premium. For Power Automate, the monthly option is useful for proof-of-concept flows where you are not sure yet whether the flow will stay in production. Once a flow is stable, switch it to annual to save the 20%.

When to Get Help

If your Power Automate footprint is small - under 10 flows, fewer than 20 users - you can work this out yourself in an afternoon with a spreadsheet.

If you are running 50+ flows across multiple departments, with a mix of citizen developers and IT-built solutions, you almost certainly have licensing waste, and probably licensing risk. We do Power Platform licensing audits as a fixed-fee engagement that usually pays for itself in the first six months of remediation.

For broader automation strategy, our AI automation company team works with mid-market and enterprise clients on the bigger picture - which processes belong in Power Automate, which need Copilot Studio, which need Power Apps, and which need a custom build.

If you want a straight conversation about what you actually need before you sign anything with Microsoft, contact us and we will book a call. We do not resell licences, we do not get kickbacks on Microsoft purchases, and we will tell you when you do not need to buy anything more than you already have.

Most Australian businesses are paying for the wrong Power Automate plan. The good news is that fixing it is one of the easier wins in your IT budget.