A long-form, plain-English deep dive into Microsoft Power Automate for Australian small and mid-sized businesses. Covers the four kinds of flow (automated, instant, scheduled cloud flows and desktop RPA), 1000+ connectors, approvals, real SME examples like saving email attachments to SharePoint and multi-step leave approvals, the honest split between free seeded rights and paid Premium and Process licensing, common pitfalls like flow sprawl and personal ownership, indicative July 2026 AUD pricing, and a side-by-side of five everyday moments with and without automation.
Microsoft Power Automate: automating the boring, repetitive work
Every business has jobs that a person does the same way, over and over, all day. Saving attachments. Chasing approvals. Copying data between two systems. Power Automate is the tool that watches for the trigger and does the next steps for you. It is if-this-then-that for your business software.
The short version
Power Automate is if-this-then-that for your business software. It watches for a trigger, a new email, a form submission, a file added, then does the next steps automatically: save the attachment, post to Teams, get an approval, update a spreadsheet. It removes the boring repetitive clicking.
There are two main kinds. Cloud flows connect 1000+ apps through connectors and run automatically, on a button press, or on a schedule. Desktop flows (RPA) record and replay clicks to automate old apps and websites that have no proper connector.
A free seeded version comes with Microsoft 365 for flows that stay within standard Microsoft connectors. Premium connectors, RPA and Dataverse need a paid plan. This guide explains what it does, shows the everyday examples, and is honest about the costs and the traps.
Prices in this guide are indicative AUD figures current as of July 2026 and are subject to change. Always confirm with your licensing partner before purchase.
If this happens, then do that
Microsoft Power Automate is an automation tool. You describe a trigger, the thing that starts it off, and then a list of actions, the steps that follow. When the trigger happens, the actions run. No one has to be sitting there clicking.
Think of the small jobs your team does the same way every time. An invoice arrives, so someone saves it to a folder. A form comes in, so someone tells the right person. A booking is made, so someone types it into the accounts package. Each of those is a trigger followed by a few predictable steps. That is exactly the shape Power Automate is built for.
You build a flow in a designer that reads like a checklist. Pick the trigger, add the actions, choose the apps. For most everyday flows there is no code at all. The result runs quietly in the background and gives your team back the time they were spending on the repetitive stuff.
A flow, start to finish
Trigger
Action
Action
Done
One trigger, a few actions. This flow runs in a couple of seconds, every time an invoice lands, whether anyone is at their desk or not.
More everyday examples
| When this happens (trigger) | The flow does this (actions) |
|---|---|
| New email arrives with an attachment |
|
| A staff member submits a leave form |
|
| A new lead fills in your website form |
|
Four flavours, one tool
Power Automate comes in a few shapes. Three are cloud flows that live online and connect your apps. The fourth is a desktop flow that drives your screen for you. Here is the difference in plain terms.
Automated cloud flows
Something happens
The flow watches for an event and runs on its own. A new email arrives with an attachment, a form is submitted, a file lands in a folder, a record changes. No one has to press a button. These are the workhorses. Most of the time you save comes from here.
Instant cloud flows
You press a button
You kick the flow off yourself, from a button in Teams, on your phone, or inside an app. Handy for things you do on demand: log a job, request an approval, send a templated update. The person stays in control of when it runs.
Scheduled cloud flows
On a timer
The flow runs on a schedule you set. Every morning at 8, every Friday afternoon, the first of the month. Good for recurring chores: a weekly report, a reminder to chase overdue invoices, a nightly sync between two systems.
Desktop flows (RPA)
Records your clicks
Robotic process automation records your clicks and keystrokes, then replays them. This is for old software and websites that have no proper connector. If a task means copying data between an accounting package from 2009 and a web portal, a desktop flow can do the typing for you.
The parts you will actually use
Here is what Power Automate puts in your hands, in the order most businesses grow into it.
1000+ app connectors
Connectors are the pre-built plugs that let Power Automate talk to other software. Outlook, SharePoint, Teams, Excel, OneDrive and Dataverse are all covered, plus hundreds of third-party tools. You pick the app, sign in once, and the flow can read and write to it. No code.
Approvals built in
Power Automate has a proper approvals engine. Someone gets a clear approve-or-reject card in Teams, Outlook or the mobile app. The flow waits for their decision, records who approved and when, then carries on down the right path. No more chasing sign-off over email.
File and data handling
Move a file from an email into the right SharePoint folder. Pull rows out of an Excel sheet. Create a folder when a new client is added. Copy data from one system into another on a schedule. The dull copy-paste work that eats an afternoon becomes a flow that runs in seconds.
Notifications and reminders
Ping a Teams channel when a form comes in. Text a manager when a big order lands. Nudge someone whose task is overdue. Power Automate is good at making sure the right person hears about the right thing at the right moment, without anyone remembering to send it.
Keeping two systems in sync
If your booking system and your accounting package do not talk to each other, a flow can carry data between them. New booking creates an invoice draft. Paid invoice updates the CRM. It is the digital equivalent of the person who used to re-key everything, except it does not make typos or take annual leave.
RPA for legacy apps
Desktop flows automate the software that has no modern way in. Old line-of-business apps, clunky supplier portals, that one program only Sharon knows how to drive. Power Automate records the steps and repeats them. It is not elegant, but for stubborn old systems it is often the only option.
An approval flow with a yes or no branch
Approved
Update the leave calendar, notify payroll, tell the staff member yes. All logged.
Rejected
Let the staff member know, with the manager's reason. Nothing else changes.
Pros and cons
What works well
- A seeded version comes free with Microsoft 365. For flows that stay within standard Microsoft connectors (Outlook, SharePoint, Teams, Excel, OneDrive), you can start automating today at no extra licence cost.
- No code required for most flows. The designer is drag-and-drop with plain-English steps. A capable staff member can build a useful flow in an afternoon. You do not need a developer for the everyday stuff.
- It plugs into the tools you already have. If you are on Microsoft 365, Power Automate already knows your Outlook, your SharePoint, your Teams. The connectors are there and signed in.
- Real approvals, properly recorded. Leave, purchases, expenses, sign-offs. The flow routes the request, waits, records the decision, and moves on. You get an audit trail for free.
- It scales from one tiny task to a whole process. Start by saving email attachments. End up running a multi-step onboarding workflow across five systems. Same tool, same skills.
- RPA reaches the software connectors cannot. When an app has no modern integration, desktop flows still get the job done by driving the screen like a person would.
Where it gets tricky
- Flows sprawl and break quietly. It is easy to end up with dozens of flows nobody is tracking. When one hits a limit or a connection expires, it just stops. Often the first sign is someone asking why the report did not arrive. Governance matters.
- A flow owned by one person breaks when they leave. If Sharon built the flow under her own account and Sharon leaves, her connections die with her. Flows should be owned by a shared account or service principal, not an individual, so they survive staff changes.
- Premium licensing adds up. The free seeded rights only cover standard Microsoft connectors. The moment you need a premium connector, RPA or Dataverse, you are into paid per-user or per-flow plans. Costs are manageable, but they are real and worth planning for.
- Complex logic gets fiddly. Simple trigger-and-action flows are easy. Once you add branches, loops, error handling and conditions, it starts to feel like programming, because it is. Ambitious flows benefit from someone who has built them before.
- RPA is brittle. Desktop flows replay clicks on the screen. If the target app changes its layout, moves a button or updates its login, the flow can break. RPA is powerful but needs more babysitting than a proper connector.
Free to start, paid to go further
The honest picture: a lot of useful automation is free if you are already on Microsoft 365. You only pay once a flow needs a premium connector, desktop RPA, or Dataverse. Here is the split.
| Plan | Approximate AUD cost | What you get |
|---|---|---|
| Seeded / use rights (with Microsoft 365) | Included, no extra cost | Automated, instant and scheduled cloud flows that stay within standard Microsoft connectors: Outlook, SharePoint, Teams, Excel, OneDrive, Planner and more. Enough to automate a lot of everyday work. |
| Power Automate Premium (per user) | ≈ $25 AUD/user/month | Adds premium connectors (Salesforce, SAP, SQL, third-party business systems), desktop flows / RPA, Dataverse and process mining. Priced per user, for people who build and run their own premium flows. |
| Power Automate Process (per flow) | ≈ $250 AUD/flow/month | Licenses a single high-value flow no matter how many people it serves. Best when one shared process runs across the whole team, or an unattended RPA bot runs in the background. Cheaper than per-user once enough people are involved. |
| AI Builder (add-on) | Add-on credits | Optional AI capabilities inside flows: reading text from invoices and receipts, form processing, prediction. Small credit allowances come with Premium; heavier use needs an add-on. |
The quick rule: per-user Premium suits a handful of people who each build and run their own premium flows. Per-flow Process suits one shared process used by lots of people, or a background bot. Once enough people touch a single flow, per-flow works out cheaper than licensing them all. We help you work out which side of that line you are on.
Indicative figures only, in AUD and excluding GST. Current as of July 2026 and subject to change. Microsoft licensing shifts often, so confirm with your licensing partner before purchase.
Where it earns its keep
The business drowning in email admin
Invoices, remittances, signed forms and supplier documents arrive as attachments all day. Someone saves each one to the right folder by hand. A flow does it the moment the email lands, files the attachment in SharePoint, and posts a note so the team knows it arrived. Hours a week, gone.
Anyone with approvals stuck in inboxes
Leave requests, purchase orders, expense claims and quotes that need a manager's yes. Right now they sit in email threads and get forgotten. A flow routes each one to the right approver, chases if there is no answer, records the decision, and updates the spreadsheet. Nothing slips.
Two systems that will not talk
A booking tool and an accounting package. A CRM and a mailing list. Staff copy data from one to the other every day and occasionally get it wrong. A flow carries the data across automatically, so the two systems stay in step without anyone re-keying a thing.
Teams that miss things
A website enquiry lands and nobody notices for two days. A flow posts every new form submission straight into a Teams channel the second it arrives, tags the right person, and logs it. The team sees it, acts on it, and the lead does not go cold.
Stuck with old software
You run a line-of-business app or supplier portal that has no modern way to connect. Data still has to move in and out of it by hand. A desktop flow records those clicks and repeats them, so the old system keeps working without a person doing the typing.
The manual way versus the automated flow
These are five small jobs that happen in every office, over and over. On their own each one is trivial. Added up across a year, they are days of your team's time. Here is the difference a flow makes.
| The moment | The manual way | With a flow |
|---|---|---|
| A supplier invoice arrives by email | Someone opens the email, downloads the PDF, finds the right SharePoint folder, saves it with a sensible name, then flags the email so it is not done twice. Repeat forty times a day. Occasionally one gets missed or filed in the wrong spot. | The flow spots the incoming email, saves the attachment to the correct folder automatically, names it consistently, and drops a note in the accounts channel. It happens in seconds, every time, whether anyone is watching or not. |
| A staff member requests leave | They email their manager. The manager means to reply but forgets. Two days later they chase it. Eventually it is approved verbally and someone remembers to update the leave spreadsheet. Maybe. | The staff member fills in a form. The flow sends the manager an approve-or-reject card, waits, records the decision and who made it, updates the leave calendar and lets payroll know. The whole thing is logged and nothing gets lost. |
| A new enquiry comes through the website | The form emails a shared inbox nobody watches closely. The lead sits unread over a busy afternoon. By the time someone spots it, the customer has rung a competitor. | The moment the form is submitted, the flow posts it to the sales channel in Teams, creates a record, and sends the customer a friendly acknowledgement. Someone picks it up within minutes. |
| A task on a project is overdue | The task sits there. Nobody is watching the due dates. It surfaces at the next meeting, a week late, when someone finally checks the list. | A scheduled flow checks for overdue tasks each morning and quietly nudges the owner with a reminder. The manager only hears about it if it stays overdue. Small things stop falling through. |
| The same data has to go into two systems | A staff member re-types every new booking into the accounting package. It works until it is busy, then bookings get skipped, mistyped, or entered twice. Reconciling the two lists becomes its own job. | A flow moves each new booking across automatically. The two systems match without anyone re-keying anything. The person who used to do it gets their afternoon back. |
A supplier invoice arrives by email
The manual way
Someone opens the email, downloads the PDF, finds the right SharePoint folder, saves it with a sensible name, then flags the email so it is not done twice. Repeat forty times a day. Occasionally one gets missed or filed in the wrong spot.
With a flow
The flow spots the incoming email, saves the attachment to the correct folder automatically, names it consistently, and drops a note in the accounts channel. It happens in seconds, every time, whether anyone is watching or not.
A staff member requests leave
The manual way
They email their manager. The manager means to reply but forgets. Two days later they chase it. Eventually it is approved verbally and someone remembers to update the leave spreadsheet. Maybe.
With a flow
The staff member fills in a form. The flow sends the manager an approve-or-reject card, waits, records the decision and who made it, updates the leave calendar and lets payroll know. The whole thing is logged and nothing gets lost.
A new enquiry comes through the website
The manual way
The form emails a shared inbox nobody watches closely. The lead sits unread over a busy afternoon. By the time someone spots it, the customer has rung a competitor.
With a flow
The moment the form is submitted, the flow posts it to the sales channel in Teams, creates a record, and sends the customer a friendly acknowledgement. Someone picks it up within minutes.
A task on a project is overdue
The manual way
The task sits there. Nobody is watching the due dates. It surfaces at the next meeting, a week late, when someone finally checks the list.
With a flow
A scheduled flow checks for overdue tasks each morning and quietly nudges the owner with a reminder. The manager only hears about it if it stays overdue. Small things stop falling through.
The same data has to go into two systems
The manual way
A staff member re-types every new booking into the accounting package. It works until it is busy, then bookings get skipped, mistyped, or entered twice. Reconciling the two lists becomes its own job.
With a flow
A flow moves each new booking across automatically. The two systems match without anyone re-keying anything. The person who used to do it gets their afternoon back.
What automation looks like day-to-day
A good flow is invisible to the people it helps. The work just gets done. Here is what different people in the business actually experience once a few flows are running.
| Who | Their experience |
|---|---|
| A staff member who submits an approval | They fill in a form or press a button in Teams. Later they get a message telling them the outcome. They never think about the flow doing the work in between. It just happens. |
| A manager approving requests | They get a clear card in Teams or Outlook: here is the request, approve or reject. One tap. The flow handles the rest and keeps a record of who decided what and when. |
| The person who built the flow | They open Power Automate now and then to check the run history, see anything that failed, and tweak a step. For a well-built flow, this is a few minutes a month. |
| StartCloud (managed automation) | We design the flows, host them under a shared owner so they survive staff changes, monitor for failures and expired connections, and adjust them as your processes change. You get the time savings without owning the plumbing. |
| A flow that hits a snag | A connection expires or an app changes. The flow fails and logs why. With monitoring in place, someone is alerted and fixes it before anyone notices. Without monitoring, it can sit broken for weeks. |
From a good idea to a flow you can trust
Automation goes wrong when flows are built in a rush, owned by one person, and left unwatched. Our automation service is built to avoid exactly that. Here is how we approach it.
Step 1. Find the boring, repetitive work
We sit with your team and map the small jobs that eat time: the manual filing, the chasing, the re-typing, the approvals stuck in inboxes. Not everything should be automated. We pick the tasks where a flow pays back quickly and clearly.
Step 2. Check what connectors you need
We work out whether each flow stays within the free standard Microsoft connectors or needs a premium connector, RPA or Dataverse. That tells us honestly whether you can run it on seeded rights or need a paid plan, before you spend anything.
Step 3. Build and test the flows
We build each flow, test it against real examples, and add error handling so it fails gracefully and tells someone when it does. A flow that breaks silently is worse than no flow, so we design for the day something goes wrong.
Step 4. Own flows properly, not personally
Flows are set up under a shared account or service principal, not one staff member's login. That way they keep running when people change roles or leave. This one decision prevents the most common and most painful failure.
Step 5. Monitor and maintain
We keep an eye on run history, catch expired connections and failures early, and refresh flows when your processes or the underlying apps change. Automation is not set-and-forget, so we treat it as an ongoing service, not a one-off build.
Step 6. Grow it sensibly
Once the first few flows are earning their keep, we look for the next ones. We keep a register of what exists, who owns it and what it does, so your automation stays a tidy asset rather than a pile of mystery flows nobody understands.
Not sure where to start? An efficiency audit is often the first step. We look at where your team's time actually goes and point out the tasks worth automating first. If your flows need to reach across separate systems, our integrations work is what joins them up.
Common pitfalls
-
Building flows under a personal account. The single most common mistake. When that person leaves, their connections die and the flows stop. Always own important flows under a shared account or service principal.
-
Automating a bad process. If a process is broken, automating it just makes it break faster. Fix or simplify the process first, then automate the good version. A flow amplifies whatever you point it at.
-
No monitoring, so failures go unnoticed. Flows fail quietly. Without someone watching the run history, a broken flow can sit dead for weeks while everyone assumes it is working. Build in alerts for failures from day one.
-
Assuming everything is free. The seeded rights are generous, but premium connectors, RPA and Dataverse need paid plans. Check the licensing before you build a flow around a premium connector, not after.
-
Leaning on RPA when a connector exists. Desktop flows are brittle and should be a last resort. If the app has a proper connector, use it. Save RPA for the genuinely old software that has no other way in.
-
Letting flows multiply with no register. Fifty undocumented flows built by five different people is a mess waiting to happen. Keep a simple list of what exists, who owns it and what it does.
Our automation service keeps that register and the monitoring for you.
Should your business use Power Automate?
Yes, if your team is doing the same manual admin over and over. Saving attachments, chasing approvals, copying data between systems, telling people when something arrives. That work is quietly expensive, and Power Automate is very good at taking it off your team's plate.
The best part is you can start for free. If you are already on Microsoft 365, the seeded rights cover a surprising amount of everyday automation. You only reach for a paid plan when a flow needs a premium connector, desktop RPA, or Dataverse, and by then you usually know it is worth it.
The catch is governance. Flows that are built in a hurry, owned by one person, and left unmonitored will let you down eventually. Automation is a small ongoing responsibility, not a one-off. Treat it that way, or have someone treat it that way for you, and it pays back handsomely.
Where StartCloud fits in
The tool is free to start. Here is where we help.
What is your team still doing by hand?
If your week has jobs that go the same way every time, there is probably a flow for it. StartCloud finds the repetitive work worth automating and builds flows that keep running long after they are set up.
Book an automation chatNo obligation. Straight answers. Perth-based team.
References
- Microsoft Power Automate product page
https://www.microsoft.com/en-au/power-platform/products/power-automate - Power Automate pricing (Microsoft)
https://www.microsoft.com/en-au/power-platform/products/power-automate/pricing - Power Automate documentation (Microsoft Learn)
https://learn.microsoft.com/en-us/power-automate/ - Types of cloud flows
https://learn.microsoft.com/en-us/power-automate/flow-types - Desktop flows and robotic process automation (RPA)
https://learn.microsoft.com/en-us/power-automate/desktop-flows/introduction - Connectors reference
https://learn.microsoft.com/en-us/connectors/connector-reference/ - Licensing overview for Power Automate
https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/types
Document prepared July 2026 by StartCloud (Start Technologies Pty Ltd). Pricing and feature information is indicative only and current as of the date of preparation. Microsoft licensing changes frequently, so confirm with your licensing partner before any purchase decision.