Microsoft Power Automate Pricing Australia (2026)

For one person who needs premium connections, the published starting point is AU$22.40 per month, excluding GST, paid yearly. A separately licensed business flow or unattended bot starts at AU$224.50 per month on the same terms, as at 22 October 2026. Those are software prices. I would budget separately for deciding what to automate, building the flow and keeping it running.

What Does Power Automate Cost in Australia, and Does the Price Include GST?

None of Microsoft's Australian Power Automate prices include GST, so add it when you budget. Microsoft publishes the following Australian subscription prices excluding GST, with yearly payment. The monthly figures are the published monthly equivalents, not monthly commitment offers. All figures below are current as at 22 October 2026.

Microsoft cautions that actual prices can vary by country, currency and organisation. Confirm the checkout or reseller quote before committing. If the terminology is new, start with the workflow automation guide to map the trigger, steps and outcome before choosing a licence.

What Power Automate Is Already Included in Microsoft 365 Business?

Your existing subscription may cover the first job. Microsoft's Australian Business plan comparison lists Power Automate across Business Basic, Standard and Premium. But the Microsoft 365 licensing table limits those rights to standard connectors, with no premium or custom connectors, RPA, AI Builder credits or Dataverse storage, as at 22 October 2026.

Microsoft 365 Business Premium and Power Automate Premium are separate products. Buying the former does not grant the latter's automation rights.

I would check every proposed connection before buying anything. A flow using standard connectors may fit the subscription you already have. Add Salesforce, classified as Premium as at 22 October 2026, and the Microsoft 365 entitlement alone no longer covers that flow.

There is also a local desktop distinction: Microsoft's Windows entitlement permits limited attended desktop execution without cloud orchestration. That is different from scheduling an unattended desktop bot through the cloud.

Premium vs Process vs Hosted Process: Which Licence Fits the Job?

I would choose by who or what needs the licence. Microsoft's licence types documentation, checked 22 October 2026, makes the following distinctions.

• Premium: a person automating their own work with premium or custom connectors, or running attended desktop automation while present.
• Process: a cloud flow licensed in its own right, or an unattended desktop bot on a machine you provide.
• Hosted Process: an unattended bot with a virtual machine managed by Microsoft on Azure infrastructure.

For a shared enquiry-to-CRM flow, Process can cover premium connections regardless of the owning or triggering user's licence. The flow must be in a solution before a Process licence can be assigned. A shared workflow does not automatically require Process; check how the users and flow will be licensed.

For desktop automation, each Process bot runs one unattended desktop flow at a time, as at 22 October 2026. Also, capacity licences do not remove every user licensing requirement: registering a machine for unattended automation still requires a Premium user. Put that requirement into the quote.

What Drives Costs Beyond the Power Automate Subscription?

The connector, workload and extra services matter. I would check these before treating the plan price as the whole software budget.

Premium Connectors and Desktop Automation

Salesforce and Azure OpenAI are verified premium connectors as at 22 October 2026. Check Microsoft's premium connector list and each connector's own page. Desktop RPA adds another decision: attended execution, an unattended machine you manage, or Microsoft-hosted infrastructure.

Daily Action Allowances

As at 22 October 2026, Microsoft's published request allowances are 6,000 per user per day for Microsoft 365, 40,000 for Premium and 250,000 per Process or Hosted Process licence. Successful and failed actions count; desktop executions do not consume these requests.

Those are the official allowances, not a claim about current enforcement. Microsoft says all organisations are in a transition period, with different transitional limits and Premium and seeded allowances applied per cloud flow. Size the design against the published allowance using actions per run multiplied by runs per day.

AI Builder, Copilot Credits and Storage

Microsoft's licence comparison lists 5,000 AI Builder credits monthly for each paid licence type as at 22 October 2026. That is an allowance, so ask what the proposed AI work consumes and what happens when the allowance runs out.

Agent flows are metered through Copilot Studio rather than Power Platform requests, according to Microsoft's request documentation. Keep that budget separate; the Copilot Studio pricing guide covers the detail.

Ask about storage too. Paid licences carry limited Dataverse capacity. Premium also includes 50 MB of process mining per user as at 22 October 2026; the much larger Process Mining add-on is a separate enterprise line item.

When Is Pay-as-You-Go Cheaper Than Prepaid Licences?

Pay-as-you-go links an environment to an Azure subscription. As at 22 October 2026, the preview meters list USD 0.60 per premium cloud or attended run and USD 3.00 per unattended run. Standard-connector runs are not charged.

Microsoft identifies seasonal flows, or flows with fewer runs and more users, as suitable for this model. Frequent personal automation favours prepaid licensing. I would multiply expected billable runs by the relevant USD meter, then compare the resulting Azure bill with the Australian subscription quote. A direct numerical break-even would need consistent currencies and contract terms.

There is a configuration catch: Microsoft says Process licences cannot be used in a pay-as-you-go environment. Keep Process-dependent flows in an environment without that Azure billing link.

How Should an Australian Service Business Budget for Power Automate?

I would separate the quote into setup, software and ongoing operation. A licence gives you permission and capacity. Someone still needs to decide what should happen when a customer record is incomplete or a connection fails.

1. Define one job. Specify its trigger, systems, expected volume and the point where a person approves the next action.
2. Price the build. Ask for process design, connection setup, exception handling, testing and documentation to be stated explicitly.
3. List recurring software. Include user and capacity licences, machine hosting where applicable, storage and metered AI usage.
4. Name the ongoing owner. Ask who monitors failures, restores connections, reviews exceptions and changes rules when the business changes.

If you are comparing platforms, use the Zapier pricing guide alongside the actual connections required. The custom automation or no-code comparison helps frame the build decision.

For an Australian service business that wants automation designed, built and then run around its existing tools, with a person approving anything sensitive, Truespeak is built for exactly that. I have paid for this kind of work from the buyer's side: at Optus, self-service and digital automation cut operating costs by 40%, and in my own e-commerce business, Haus Bright, Zapier automations captured customer details while I ran the rest.

Truespeak's business process automation service covers design, build and ongoing running, including monitoring, fixing failures, reviewing exceptions and improving rules. Where a tool has no usable connection, that step stays manual. Truespeak publishes no prices and quotes after a discovery call.