Microsoft Power Automate: An Honest Look at Where It Fits

Updated June 2026. Rewritten with current per-user pricing, the premium connector licensing trap, and an honest read on where Power Automate beats the alternatives and where it does not.

Microsoft Power Automate is excellent inside the Microsoft 365 stack and clumsy the moment you step outside it. That sentence is most of what you need to decide whether it is right for you. If your business runs on SharePoint, Teams, Outlook and Dataverse, it is probably the obvious choice. If it does not, the calculation changes fast.

We are Osher Digital, a Brisbane automation and AI consultancy. We build on Power Automate, n8n, Make and custom code, which means we have no reason to talk anyone into a tool that does not fit. This is the honest version: what Power Automate does well, where it gets awkward, what it actually costs once the licensing dust settles, and the cases where we steer clients elsewhere.

What Microsoft Power Automate Actually Does

Power Automate is Microsoft’s workflow automation tool. At its core it connects triggers to actions: when an email arrives with an attachment, save it to SharePoint and post a Teams message. When a form is submitted, create a record in Dataverse and start an approval. It is the Microsoft answer to Zapier, bundled deep into the Power Platform alongside Power Apps and Power BI.

There are really three products wearing one name, and people conflate them constantly:

• Cloud flows are the bread and butter: API-to-API automation triggered by events or schedules.
• Desktop flows are the robotic process automation side, Power Automate Desktop, which clicks through legacy applications that have no API.
• AI Builder adds document extraction, prediction and, increasingly, generative steps inside a flow.

When someone asks how Microsoft Power Automate works, the honest answer is “which of the three do you mean”, because the licensing, the reliability and the use cases differ sharply across them.

Where Microsoft Power Automate Earns Its Place

Inside Microsoft 365, nothing else comes close on integration depth. The SharePoint, Outlook, Teams, Excel and Dataverse connectors are first-party and they behave. Approvals are a genuine strength: the built-in approval action posts to Teams and email, tracks responses, and handles reminders without you wiring any of it together. We have shipped document-approval and onboarding flows for clients where the entire thing lived in connectors that already understood their tenant’s permissions.

Two more things it does well. Governance, for one: the Power Platform admin centre gives IT real control over environments, data loss prevention policies and who can build what. For a business already managing a Microsoft tenant, that is one less governance model to learn. And Power Automate Desktop is a credible RPA tool that comes effectively free with most Windows and M365 licences, which makes it the cheapest way to script a legacy Windows application that refuses to expose an API.

So the sweet spot is clear. A Microsoft-centric business automating internal processes across its own stack will get further, faster, with Power Automate than with anything else.

Where Microsoft Power Automate Gets Clumsy

Step outside the Microsoft garden and the experience changes. The third-party connectors exist, but they lag their first-party cousins on depth and reliability, and the good ones are nearly all premium, which is where the bill starts climbing.

The editor itself fights you on anything complex. Expressions live in a cramped formula box using a syntax that is its own small language. There is no real version control: you export a flow as a zip and pray, rather than diffing a change in Git the way you would with code or with a tool like n8n. We have lost time to a flow that worked on Tuesday and broke on Wednesday with no way to see what changed, because nothing tracked it. Branching logic and loops are workable but verbose, and debugging a flow with a dozen nested conditions is genuinely unpleasant.

Then there is throttling. Power Automate enforces action limits per connection and per plan, and a flow processing a few thousand items an hour will hit them. The fixes (batching, concurrency control, splitting flows) are doable, but they are friction that an engine built for volume does not impose. For high-throughput, code-heavy or multi-vendor workflows, we usually reach for n8n instead, where the logic lives in real JavaScript and the whole thing version-controls cleanly.

Microsoft Power Automate Pricing, and the Connector Trap

Pricing is where most people get caught, so here is the current shape of it. The headline plan is Power Automate Premium at around $15 USD per user per month, roughly $23 AUD, which gives one user unlimited cloud flows plus attended desktop flows, 5,000 AI Builder credits, and a small allocation of Dataverse database and file storage. Unattended desktop automation, the kind that runs RPA bots on a server with nobody watching, is a separate and considerably more expensive add-on.

Here is the trap. Microsoft 365 E3 and E5 licences include “Power Automate for Microsoft 365”, and teams assume that means Power Automate is free for them. It covers standard connectors only. The instant a flow touches a premium connector, and Salesforce, SAP, most databases, HTTP requests and custom connectors are all premium, that flow needs a Premium licence for whoever it runs as. We have reviewed more than one client’s automation that was quietly out of licence compliance because nobody clocked that the HTTP action is premium.

The practical planning number: budget the Premium per-user plan from day one if you are integrating anything outside Microsoft, and price unattended RPA carefully because it is the line item that surprises people. For a small team automating inside M365 only, your existing licences may genuinely cover it. For everyone else, model the real cost before you commit. If you want a quick sense-check on whether your flows are correctly licensed, book a call and we will look at it.

Can Power Automate Read a PDF?

Yes, and this is a common reason teams adopt it, so it is worth being precise. AI Builder’s document processing model extracts structured fields from invoices, receipts and custom forms, and it is genuinely decent on clean, consistent documents. For a steady stream of similar invoices from known suppliers, it works.

Where it strains is variety. Throw a messy mix of layouts, scanned faxes and multi-page contracts at it and accuracy drops, and AI Builder credits get consumed quickly at scale. For high-volume or high-variety document extraction we increasingly build a small pipeline around a frontier model like Claude Sonnet 4.5 or GPT-4.1 with a validation layer, which handles the long tail of weird documents far better than the built-in model. We covered that pattern in our piece on automating invoice processing. For light, consistent extraction inside an existing M365 setup, AI Builder is the path of least resistance.

Power Automate vs Zapier, Make and n8n

The short version of how we steer clients:

• Power Automate wins when you are Microsoft-centric and automating internal processes across your own tenant, and when you want IT-grade governance built in.
• Zapier wins for non-technical users wiring together SaaS tools quickly, with the widest connector library and the gentlest learning curve. It gets expensive at volume.
• Make sits in between: more visual logic than Zapier, friendlier than Power Automate, good for mid-complexity SaaS automation.
• n8n wins for technical teams who want real code, self-hosting, version control and predictable costs at high volume. It is our default when the logic is genuinely complex.

None of these is the right answer for everyone, and a business of any size usually ends up running two of them. Our n8n versus Zapier comparison goes deeper on the code-first end of that spectrum.

Things That Bite in Production

A few hard-won notes from running Power Automate flows for real businesses:

• Flow sprawl. Without governance, every department builds its own flows and you end up with hundreds, half of them orphaned when the builder leaves. Name them with a convention and own a register from the start.
• The connection that expires. A flow runs as whoever authorised the connection. When that person leaves or their token expires, the flow dies silently. Use service accounts for anything that matters.
• Throttling under load. Test at realistic volume, not with three sample records. The limits only show up when the flow processes the Monday backlog.
• No clean rollback. Because version control is so weak, treat changes carefully and keep an exported copy before you edit a production flow. We have rebuilt a flow from memory after a bad edit, exactly once, and never again.

When Microsoft Power Automate Is Not the Right Tool

We talk clients out of Power Automate when the workflow is high-volume and code-heavy, where the editor’s friction and throttling become a daily tax. We steer away when most of the systems involved sit outside Microsoft, because you end up paying premium-connector prices for a worse experience than a tool built for those systems. And we avoid it for anything that needs proper engineering discipline, version control, automated testing, code review, because the platform simply does not support that way of working.

It is also the wrong tool when the real need is an intelligent agent rather than a fixed workflow. If the job involves reasoning over messy inputs and deciding what to do, that is agent territory, not a trigger-action flow. Power Automate can call an AI model, but it is not the right home for genuinely agentic logic.

Frequently Asked Questions

How does Microsoft Power Automate work?

It connects a trigger to one or more actions. A trigger is an event, such as an email arriving or a form being submitted, and the actions are the steps that follow, often across other apps. Cloud flows handle API-based automation, desktop flows handle clicking through applications that have no API, and AI Builder adds document and prediction steps inside a flow.

Do I need Power Automate?

If your business runs on Microsoft 365 and you are automating internal processes across SharePoint, Teams, Outlook and Dataverse, it is the natural fit and you may already be partly licensed for it. If most of your tools sit outside Microsoft, or your workflows are high-volume and code-heavy, a tool like n8n, Make or Zapier is often a better match.

Can Power Automate read a PDF?

Yes. AI Builder’s document processing extracts structured fields from invoices, receipts and custom forms, and it works well on clean, consistent documents. For high volume or a wide variety of messy layouts, a pipeline built around a frontier model with a validation step usually delivers better accuracy and lower cost at scale.

How much does Power Automate cost in AUD?

The Premium per-user plan is roughly $23 AUD per user per month, covering unlimited cloud flows and attended desktop flows. Unattended RPA is a separate and more expensive add-on. Microsoft 365 E3 and E5 include Power Automate for standard connectors only, so any flow using a premium connector needs the Premium licence.

What counts as a premium connector?

Premium connectors include Salesforce, SAP, most SQL and other databases, the HTTP action, and any custom connector. The first-party Microsoft 365 connectors are standard. The catch is that the very common HTTP request action is premium, so many flows that look like they should run on a standard licence actually require Premium.

Power Automate or n8n?

Power Automate for Microsoft-centric internal automation with built-in governance. n8n for technical teams who want real code in their workflows, self-hosting, clean version control and predictable costs at high volume. Many businesses run both: Power Automate for the M365 side and n8n for the complex, multi-vendor or high-throughput work.

Is Power Automate good for RPA?

Power Automate Desktop is a credible RPA tool, and for attended automation it comes effectively free with most Windows and M365 licences, which makes it a cheap way to script a legacy Windows app. Unattended RPA running on a server is a separate paid tier. For modern document and data work, AI extraction has overtaken classical RPA, so reserve desktop flows for the genuinely legacy cases.

Does Power Automate support version control?

Not in any meaningful sense. You can export a flow as a solution package and store it, but there is no proper diffing, branching or code review the way there is with a code-first tool. For teams that need real engineering discipline around their automations, this is one of Power Automate’s weakest points and a common reason to choose a different tool.

Power Automate is a strong tool with a clear home: the Microsoft stack. The mistake is assuming that because it is bundled, it is the right tool for every automation a business has. Match it to the Microsoft-centric work, reach for something else where it strains, and watch the connector licensing. If you want help deciding which automation platform fits your stack, get in touch with our team.