If you've ever pasted the same data from one app into another, sent the same email three times a week, or watched a colleague spend an hour reformatting a spreadsheet that should have been done in seconds — Power Automate probably has a place in your business.
This guide covers what Power Automate actually is, what it costs Australian businesses, where it works well, and — just as importantly — where it doesn't. We've built dozens of flows for clients across construction, professional services, retail, and not-for-profit. The honest version is below.
No marketing fluff. No "10x your productivity". Just what we'd tell a friend over coffee.
What is Power Automate?
Power Automate is Microsoft's workflow automation platform. At its simplest, it lets you build "if this happens, then do that" rules across hundreds of apps — without writing code. It started life as Microsoft Flow back in 2016 and was renamed in 2019, which is why you'll still see both names in older documentation.
Three things make it different from generic automation tools:
It plugs into Microsoft 365 natively. Outlook, Teams, SharePoint, Excel, OneDrive, Word, OneNote, Planner, Forms — all of these have first-class connectors that work without any setup. If your business runs on Microsoft 365 (and most Australian SMBs do), Power Automate is the path of least resistance.
It supports three different automation modes — cloud flows (run on Microsoft's servers), desktop flows (run on a Windows machine to drive legacy software with no API), and business process flows (used to standardise how a record moves through stages, mostly inside Dynamics).
It's part of the broader Power Platform — alongside Power Apps (custom apps), Power BI (dashboards), Power Pages (websites), and Copilot Studio (AI agents). Flows you build in Power Automate can be triggered from Power Apps, surface data in Power BI, and call Copilot agents. That ecosystem matters more the bigger your environment grows.
The upside is genuine breadth. The downside, which the marketing pages don't mention, is that the licensing is genuinely confusing and there are a lot of footguns. We'll cover both.
What Power Automate costs in Australia
Microsoft's pricing changes regularly and the names of the plans seem to shift every 18 months. The figures below were accurate at time of writing — verify on Microsoft's pricing page before committing budget.
What's included with Microsoft 365
If you have any Microsoft 365 business plan — Business Basic, Business Standard, Business Premium, or one of the Enterprise E1/E3/E5 plans — you already get a "seeded" version of Power Automate. The seeded version supports unlimited standard connectors (Outlook, SharePoint, OneDrive, Excel, Teams, Forms, Planner) and a limited number of runs per user per day.
For most small businesses, the seeded version is enough to automate 80% of what they want automated. Don't pay for a standalone plan until you've hit the wall on what comes free.
Power Automate Premium — formerly Per-User
Standalone plan, currently around AUD $23.30 per user per month at the time of writing. Gives that user unlimited cloud flows including premium connectors (Salesforce, ServiceNow, SAP, Adobe Sign, DocuSign, Stripe, custom HTTP, etc.) and access to AI Builder.
This plan suits the person in your business who's becoming the "automation owner" — the operations manager who's building dozens of flows for the whole team.
Power Automate Process — formerly Per-Flow
Currently around AUD $155 per flow per month with a 5-flow minimum. Licenses an entire flow (not per user), so if a flow is consumed by 50 employees, you pay once.
This plan suits production-grade automations that the whole organisation depends on — invoice routing, expense approvals, lead distribution. The maths flips in your favour as soon as the flow is used by more than ~7 users.
RPA / Desktop automation
If you need to drive legacy desktop software that has no API — old accounting systems, ancient ERPs, government portals — you'll need Power Automate Desktop with the Hosted RPA add-on. Pricing is per RPA bot per month and is currently meaningfully more expensive than cloud flows. Get a quote from Microsoft directly.
What we recommend
For most Australian SMBs we work with, the path is:
- Start with the seeded version that came with your Microsoft 365 plan
- Upgrade one or two power users to Premium when they outgrow standard connectors
- Consider Process licensing only when a single flow becomes business-critical and is used by many people
- Look at RPA only when you're being asked to drive software that has no API at all
Don't over-buy upfront. Microsoft will happily sell you bigger plans before you need them.
The three flow types
Knowing which flow type to reach for is half the battle. Most beginner mistakes come from forcing the wrong tool at the problem.
Cloud flows
Run on Microsoft's servers, triggered by an event (an email arrives, a SharePoint item is created, a button is pressed in Power Apps) or on a schedule (every Monday at 9 am).
This is the bread and butter. 90% of what we build for clients is cloud flows. They're cheap, they scale, they don't require any local infrastructure, and they recover gracefully when things go wrong.
Use cloud flows when the systems you're connecting both have APIs that Power Automate can talk to.
Desktop flows (Power Automate Desktop)
Run on a Windows machine, automate keyboard and mouse actions inside applications. This is RPA — Robotic Process Automation. Use it when the software you need to drive has no API and you're left logging in, clicking buttons, typing into fields, and copying data out of windows.
Desktop flows are powerful but brittle. The flow breaks the moment the target application updates its UI. We use them sparingly and always document the exact application version they were built against.
Business process flows
Used to standardise how a record progresses through defined stages — mostly inside Dynamics 365 and Dataverse. If you're not already inside that ecosystem, you'll rarely encounter these.
In practice: cloud flows for almost everything, desktop flows for the legacy edge cases, business process flows only if you're already a Dynamics shop.
Connectors — what they actually do
A connector is the pre-built integration that lets Power Automate talk to a specific app. Microsoft maintains over 1,000 of them — for everything from Adobe Sign to Zendesk.
There are two tiers:
Standard connectors are included with the seeded Microsoft 365 license — Outlook, SharePoint, OneDrive, Excel, Teams, Word, Planner, Forms, Approvals, OneNote.
Premium connectors require Premium or Process licensing — Salesforce, SAP, ServiceNow, Dynamics 365, custom HTTP, SQL Server, MySQL, PostgreSQL, common-data-service, AI Builder, Adobe Acrobat Sign, DocuSign, Stripe, Zendesk, ServiceNow.
The HTTP connector deserves a special mention. It lets you call any REST API on the internet — meaning if a SaaS tool has a public API but no dedicated Power Automate connector, you can still integrate by writing a few HTTP requests. This is the "escape hatch" we lean on heavily.
A trap to watch for: the same action can require different connectors depending on context. Reading email is "Office 365 Outlook" (standard, free). Reading a shared mailbox is "Office 365 Outlook" with the right action (still free). But reading from an Exchange Online inbox using Microsoft Graph is a separate connector with different permissions. Pick the wrong one and you'll spend an afternoon debugging.
Real-world use cases (the ones we actually build)
These are the patterns we keep seeing across Australian businesses. None of them are hypothetical.
1. Invoice arrives → save attachment + log row + notify
The classic. An email lands in a shared inbox with an invoice attached. The flow saves the PDF to SharePoint with a structured filename, extracts the supplier name from the subject line, logs a row to Excel or a SharePoint list, and posts a notification in Teams. Five minutes of admin work eliminated per invoice.
2. New job created → run an approval chain
A new project is created in a SharePoint list. The flow routes it through your approval chain (project manager, then operations, then finance), tracks responses, and updates the record's status as each approval lands. Decision-makers approve from inside Teams or Outlook without ever opening a portal.
3. Daily/weekly report compilation
Every Friday at 4 pm, the flow pulls data from three different sources, formats it into an Excel file with charts, and emails it to the leadership team. The person who used to spend two hours of their Friday on this gets it back.
4. Field team submits form → instant downstream actions
A mobile worker submits a Microsoft Forms or Power Apps form on their phone. The flow generates a Word document from a template, converts it to PDF, emails it to the customer, and updates the job record in your scheduling system. No back-and-forth, no manual document creation.
5. Customer query in shared inbox → triaged and assigned
Emails to info@ or support@ are auto-categorised by content (using AI Builder or simple keyword rules), assigned to the right team, and tracked for response time. Reduces the "did anyone see this?" problem.
6. SharePoint approval workflows
Document submitted for review → routed to reviewers in sequence → final version archived to a different library with permissions automatically tightened. Useful for policies, contracts, and ISO documentation.
7. CRM data sync
A lead enters via your website (Web3Forms, HubSpot, custom form). The flow creates the contact in your CRM, logs an activity, sends a personalised first response via Outlook, and notifies the salesperson in Teams. Speed of first contact is the single biggest predictor of close rate — automating it pays for itself fast.
8. Compliance reminders
Insurance certificates, licences, and qualifications expiring. The flow checks a SharePoint list daily, calculates days-until-expiry, and emails the relevant person 60, 30, and 7 days before the deadline. Stops the "nobody told me" problem cold.
9. Onboarding orchestration
New hire added to HR list → the flow creates their Microsoft 365 account, adds them to the right Teams and security groups, sends the welcome pack from a Word template, schedules onboarding meetings, and notifies IT to provision a laptop. Day-one is ready before they walk in.
10. Bidirectional Excel ↔ system sync
Operations runs out of an Excel file. Sales runs out of a CRM. Finance runs out of an accounting system. The flow keeps key fields in sync between them, ideally bidirectionally, so each team can stay in their preferred tool without anyone having to be the human bridge.
Common Power Automate mistakes
These are the ones we keep cleaning up after.
1. No ownership. A flow is built in someone's personal account. They leave the business. The flow disappears with their licence. Their replacement spends six weeks figuring out why the invoices stopped routing. Solution: build production flows in service accounts or shared environments, never personal accounts.
2. No documentation. "How does this flow work?" — if your answer is "let me open it and read the connector blocks", you're going to spend three hours next time something breaks. We document every production flow with: trigger description, plain-English description of each step, error-handling behaviour, who owns it, and where to escalate.
3. No error handling. A connector returns a transient error and the flow stops. You don't notice for a week. Fix: every flow that matters should have a Configure run after block sending failures to an error log + Teams notification. Five minutes to add, saves you from silent failure.
4. Hardcoded values. Email addresses, SharePoint URLs, list IDs all baked into the flow. When something needs to change — and it will — you're hunting through twelve action steps. Use environment variables or a SharePoint config list.
5. Polling instead of triggers. Some teams build flows that poll for changes ("check this folder every 5 minutes") when a real trigger exists. Native triggers are faster, cheaper on API calls, and more reliable. Always check whether the connector you're using has a When ___ is created/modified trigger before reaching for the scheduled-poll pattern.
6. Too many flows for one workflow. Three flows that all do part of one process, with messy handoffs between them. Easier to debug as one well-documented flow than three small ones. Cohesion beats granularity.
7. Building before defining the process. Power Automate is good at automating defined processes. It's bad at fixing chaotic ones. If five different staff do the same task five different ways, automating one of those ways will frustrate four of them. Standardise the process on paper first.
Power Automate vs Zapier vs Make.com
A short, honest take.
Power Automate wins when you live inside Microsoft 365. The Outlook, SharePoint, Teams, Excel and Dataverse connectors are first-class. Licensing is often already paid for. Approvals, AI Builder, Copilot integrations are tightly woven. If your stack is Microsoft, this is your default.
Zapier wins on speed of setup and breadth of SaaS connectors outside Microsoft world. If you're integrating Notion, Slack, HubSpot, Stripe, ConvertKit, Calendly, Airtable — Zapier will get you there in 10 minutes flat. The trade-off is task-based pricing that gets expensive at volume.
Make.com (formerly Integromat) sits in the middle — more visual, more powerful for branching logic and data transformation than Zapier, generally cheaper, but a steeper learning curve. Loved by power users.
We use all three at GBIT. About 70% of what we deliver to clients is Power Automate (because most of them are on Microsoft 365), 20% Make.com (for non-Microsoft stacks where data manipulation gets hairy), 10% Zapier (when speed of setup matters more than cost-at-scale).
Don't pick the tool first. Pick the process you want to automate, then ask which tool fits the systems involved.
How to get started
If you're brand new and your business is on Microsoft 365:
- Open
https://make.powerautomate.comand sign in with your work account. - Click Templates. Microsoft has hundreds of pre-built flows. Find one close to what you want and clone it.
- Modify the connectors — point them at your accounts, your SharePoint sites, your inboxes.
- Run a test. Watch each step execute. When something fails, the failure message is usually clear.
- Save and turn it on.
The free Microsoft Learn paths — particularly PL-900 (Power Platform Fundamentals) and PL-100 (Power Platform App Maker) — are genuinely good. Each takes a few hours to work through.
For everything else, the official Power Automate documentation at https://learn.microsoft.com/power-automate/ is comprehensive and accurate.
When to hire a consultant
Genuinely, you don't need one for most simple flows. Build them yourself.
Get help when:
- The flow handles financial data or personally identifiable information and needs error handling, logging, and access control done right.
- You're integrating with a system that has no Microsoft connector and you need to write custom HTTP calls or build a custom connector.
- You're hitting performance limits — Power Automate has run-time limits, throttling, and request quotas that bite at scale, and working around them needs experience.
- You've inherited an environment with hundreds of existing flows and you need someone to audit, document, and consolidate.
- You want flows that survive — proper service accounts, environment variables, version control via solutions, deployment between dev/UAT/prod environments.
A good consultant will leave you with documentation, training, and ownership — not a black box that depends on them. Avoid anyone who builds in their own tenant or insists on remaining the only person who can edit the flows.
Final word
Power Automate is genuinely useful. It also has more rough edges than the marketing suggests. The businesses that get the most out of it are the ones who treat their automation portfolio like any other piece of software — with owners, documentation, error handling, and a willingness to retire flows that have outlived their purpose.
Start small. Document as you go. Build for the next person who has to fix it.
If you're an Australian business and you'd like a hand getting started — or you've inherited a Power Automate environment that's gone sideways and you need it stabilised — book a free consultation. We'll tell you honestly whether you need our help or whether you should just spend an afternoon on Microsoft Learn instead.