Skip to main content
Microsoft Copilotpower automatemicrosoft 365licensing

Power Automate Pricing: Per User vs Per Bot for Australian SMEs

What Power Automate Premium and unattended bots actually cost in AUD, when per-bot licensing beats per-user, and the connector inventory to do before you buy.

· Founder & AI Consultant, IOTAI9 min read

Microsoft publishes two prices for Power Automate that do most of the work in any buying decision: US$15 per user per month for Power Automate Premium, and US$150 per bot per month for unattended automation, both paid yearly, observed on 23 October 2026. The same pricing page also displayed a bot price of US$215 per month, which tells you something useful before you read another word: bot licensing varies by scenario and configuration, and the number on the page is not necessarily the number on your invoice. At an indicative conversion of around A$1.54 to the US dollar, those land near A$23 per user, A$231 per bot and A$331 per bot per month, before GST and before you confirm which entity bills you in which currency.

Those three numbers are enough to run the decision. Per-user licensing scales with the number of people who need premium capability. Per-bot licensing scales with the number of processes that need to run without a person present. Most Australian SMEs that get this wrong get it wrong in the same direction: they buy per-user licences for a process that has no users, or they buy a bot for work that three staff could have triggered themselves.

The two meters, in indicative AUD

What you are buyingMicrosoft list price (USD, paid yearly)Indicative AUD, ex GST
Power Automate Premium, per user per monthUS$15about A$23
Unattended automation, per bot per monthUS$150about A$231
Second bot price shown on the same pageUS$215about A$331

The conversion is mine, not Microsoft's. The pricing calculator, checked on 17 October 2026, showed the US$15 and US$150 figures without enough surrounding context to establish when the higher bot price applies. Treat the AUD column as a planning estimate and get a written quote in your billing currency before you commit to an annual term.

The decision rule: people or processes

One unattended bot at roughly A$231 a month costs about the same as ten Power Automate Premium user licences. That ratio is the whole decision rule, and it is more useful than any feature comparison.

Per-user wins when the automation is attached to people. A sales team of six where each rep triggers an approval, a quote assembly or a CRM sync from their own desk is a per-user scenario. Six Premium licences at roughly A$23 each is about A$138 a month, and the licence travels with the person into whatever other flows they build.

Per-bot wins when the automation is attached to a process. An overnight job that reconciles a bank feed, re-keys orders into an ERP that has no modern API, or drives a legacy desktop application at 2am has no user at all. Buying nine Premium licences so nine people are "covered" for a process none of them touches is money spent on the wrong meter.

The trap sits in the middle. A process that starts attended and grows into a scheduled job quietly changes which licence you need. So does a process that starts with two staff and ends with fifteen. Write the growth path down before you sign a yearly term, because the per-user line scales smoothly and the per-bot line scales in A$231 steps.

The inventory nobody does before buying

The licence price is the easy part. The cost driver that surprises people is the inventory of connectors and execution modes sitting underneath their flows, because that inventory decides whether a flow runs on an existing Microsoft 365 entitlement or pushes you into Premium.

For every candidate process, you need four facts:

  • Which connectors it touches, and whether each is standard or premium. A flow that only moves things between Outlook, SharePoint, Teams and Excel sits in different licensing territory to one that reaches into a SQL database, an HTTP endpoint or a third-party SaaS product.
  • How it executes. Triggered by a person, triggered by an event, scheduled, or driving a desktop application. Attended and unattended desktop automation are not the same product line and are not the same price.
  • How often it runs, and whether volume is flat or spiky. Request limits and throttling are real constraints and they bite at the worst time.
  • What happens when it fails. Who sees the error, who re-runs it, and how you prevent a retry creating a duplicate invoice or a duplicate customer record.
  • Point four is where the money actually goes. A process that works for 95 per cent of cases still needs a designed route for the other 5 per cent: a queue, an owner, a retry policy and a way to tell a partial failure from a complete one. In our experience that exception path is the single most underestimated line in any automation budget, and it is not a licensing problem.

    None of this is guessable from the pricing page, and Microsoft's documentation on what a given Microsoft 365 licence already includes is specific enough that you should check your own tenant rather than rely on a blog. The work of mapping flows to entitlements, then designing and building the Power Automate and Copilot Studio layer properly, is a different exercise to signing up for Premium and finding out later.

    Two worked examples

    Lead routing for a 12-person sales and admin team. Inbound enquiries from a web form land in a shared mailbox, get qualified, and are assigned to a rep with a task and an SLA timer. The trigger is an event, not a person, and the data sits in SharePoint and Dynamics. One scheduled flow, no desktop automation, roughly 1,500 runs a month. This is a per-user scenario only if the builders and the people whose flows run need Premium; if it can be built as a single service-owned flow, you are looking at a handful of licences, not twelve. The right answer is often two or three Premium licences, around A$46 to A$69 a month, plus the build.

    Invoice processing for a construction or trades business. Supplier invoices arrive by email, get extracted, matched to purchase orders, and posted into an accounting system that only exposes a desktop interface. This runs overnight, unattended, with no user present. That is one bot at roughly A$231 a month, possibly the A$331 configuration, plus whatever AI Builder capacity the extraction consumes. The payback maths is straightforward: at 400 invoices a month, four minutes each and a loaded rate of A$45 an hour, the manual cost is about A$1,200 a month. The licence is the small number. The build and the exception queue are the real investment.

    Where the process leaves Microsoft

    Power Automate is usually the first candidate when the process lives inside Microsoft 365, Teams, SharePoint, Outlook, Excel, Dataverse or Dynamics. It is a less comfortable commercial fit once the process is mostly talking to systems Microsoft does not own.

    n8n Cloud bills by monthly workflow execution, checked on 24 October 2026: €20 a month billed annually for 2,500 executions, €50 for 10,000 and €667 for 40,000, with executions including unlimited steps. At an indicative A$1.75 to the euro that is roughly A$35, A$88 and A$1,170 a month. n8n removed active-workflow limits in its August 2025 pricing change, so plans carry unlimited workflows, steps and users and scale on executions instead.

    That billing unit matters more than the headline. An unattended invoice process running 400 times a month is one bot in Power Automate at roughly A$231, or about 400 executions in n8n, comfortably inside a plan near A$35. The gap closes fast if the process fans out into thousands of executions, and it reverses entirely if the work is genuinely embedded in Microsoft licences you already pay for.

    Zapier showed a free plan, a Professional plan from US$19.99 a month and higher plans from US$69, checked on 24 October 2026 — roughly A$31 and A$106 — with the included task allowance depending on plan and billing configuration. Make prices around credits or operations rather than executions; a Zapier comparison updated 2 October 2026 reported a Core plan from US$12 a month billed annually with 10,000 credits, which is worth confirming in Make's own interface before you model it.

    Self-hosting n8n removes the subscription but not the cost. n8n's documentation separates Community Edition from paid Business and Enterprise features such as SSO, environments, external secrets and log streaming, and self-hosting makes you responsible for upgrades, backups, monitoring, credential rotation and incident recovery.

    Australian billing and Australian data residency are separate questions

    A vendor can invoice you in AUD with GST and still process your data offshore, and a vendor can let you self-host in Sydney while its support staff administer from elsewhere. Ask them separately: which entity issues the invoice and in what currency, where production data and logs and backups live, whether prompts and uploaded documents leave Australia, and who can access the environment for support. Self-hosting gives you infrastructure control, not automatic residency — you still have to choose Australian infrastructure and operate it to the standard your contracts require.

    The first move

    Export the flow list from your Power Platform admin centre and tag every flow with three things: the connectors it uses, whether it runs attended, scheduled or unattended, and its monthly run count. That one view tells you whether your bill should scale with people or with processes, and it usually shrinks the list of flows that genuinely need Premium.

    From there, we will take that inventory, model the per-user and per-bot cost against an n8n or Zapier alternative for the same process, and give you a scoped number: what the licences cost in AUD, what the build costs, and whether the payback justifies doing it at all. Start with the automation cost and payback calculator, or send us the flow list and we will come back with a straight answer on which processes are worth automating first and which ones are cheaper left alone.

    Share on

    Founder & AI Consultant, IOTAI

    IOTAI is Australia's leading AI consultancy and Managed Intelligence Provider, specialising in Retool, n8n, and AI agent development for SMEs.

    Want this built rather than researched?

    We scope the work, tell you what it costs, and say plainly if it is not worth automating yet. Most builds ship in two to four weeks.

    Or read more about Microsoft Copilot.