Microsoft Power Automate: do you already have it, and is it enough?

If your business runs on Microsoft 365, you probably already have Power Automate. Microsoft’s Power Platform licensing guide (October 2026) lists limited Power Automate rights with Microsoft 365 Business Basic, Business Standard and Business Premium, and with E3, E5 and F3. Microsoft says those rights are for Microsoft 365 data and standard connectors, which include Outlook, SharePoint and Teams. For automating that work, it’s the tool I’d start with: it’s already paid for, and your IT team is more likely to approve it.

Power Automate is Microsoft’s equivalent of Zapier or n8n, and it sits somewhere between the two. In my experience it’s slower to build in than n8n, but it does very similar things, and on the Microsoft stack it makes complete sense. Everything is already integrated, so taking information from one Microsoft product to another is easier.

What is Microsoft Power Automate?

Power Automate is Microsoft’s tool for automating the repetitive steps between apps. Most of it is cloud flows, which Microsoft groups as automated, scheduled and instant (flow limits, updated 17 July 2026). An automated flow starts when something happens, such as an email arriving. A scheduled flow runs on a timetable, and someone starts an instant flow with a button.

Desktop flows are the other kind. They work through the screens of Windows apps and websites the way a person would, and Windows 11 comes with the desktop app preinstalled (Power Automate in Windows 11, updated 1 September 2026).

Against the tools people compare it with, I’d put it in the middle. Zapier is the easiest to start in, and n8n suits people who are happy to get technical or want to run it on their own server. Power Automate takes more setting up than Zapier and less technical skill than n8n.

Do you already have Power Automate with Microsoft 365?

Probably, for the work most businesses want to automate first. Microsoft’s licensing FAQ says users on the free plan or one of the Microsoft 365 plans “can only access standard connectors” (Power Automate licensing FAQ, updated 22 September 2026). The standard connectors cover the Microsoft apps most businesses live in: SharePoint, Outlook and Teams are all standard.

Microsoft describes these included rights as “intended for scenarios that use Microsoft 365 data and standard connectors” (licensing overview, updated 16 October 2026). So the version you already have is for automating your own Microsoft 365 work. It doesn’t include:

• premium connectors, such as SQL Server and Microsoft Dataverse;
• custom connectors, for systems Microsoft has no connector for;
• the on-premises data gateway, for data on your own servers;
• desktop flows run from a cloud flow, whether someone is at the PC or not.

If a flow needs any of those, it needs a paid licence. The FAQ puts it plainly: “If the flow doesn’t use a premium connector, you don’t need a Premium license.”

Is it enough? For flows that use standard connectors, usually yes. It stops being enough when a flow needs a premium or custom connector, the on-premises data gateway or a desktop flow run from the cloud. It also stops being enough when a premium button flow is shared with several people, because each of them then needs Premium, or when a flow outgrows Microsoft’s daily action limits.

On Microsoft’s Australian pricing page on 24 October 2026, Power Automate Premium was AU$22.40 a user a month, paid yearly. Power Automate Process, licensed per bot rather than per person, was AU$224.50 a month, and Hosted Process was AU$321.80. Those prices don’t include GST, and Microsoft says the prices shown are for marketing purposes and may differ from the actual list price.

Power Automate, Zapier or n8n: which should you use?

If you’re on the Microsoft stack, my advice is simple: use Power Automate. Three things decide it.

1. It’s already integrated. Moving information from one Microsoft product to another is easier when the tool is part of the same system.
2. IT is more likely to sign it off. You can use n8n or Zapier instead, but for security reasons Power Automate is the one more likely to satisfy your IT department.
3. Many MSPs build on it. I know many MSPs, the IT companies that look after a business’s Microsoft 365, that use Power Automate exclusively. They’re very happy with it, and they get great results for their clients.

Zapier and n8n still have their place. Zapier says it “connects to 9,000+ apps”, its paid plans start from US$19.99 a month (Zapier pricing), and it stores data on Amazon Web Services in the United States (Zapier security). n8n’s directory lists about 2,400 integrations (n8n integrations), and its cloud plans start at 20 euros a month, billed annually (n8n pricing). You can also run n8n on your own server under its fair-code licence, which limits use to “your own internal business purposes” or non-commercial and personal use (n8n licence).

What should a Microsoft business automate first?

Start with a job someone does by hand every week that moves information between Microsoft apps. Three examples that use only standard connectors:

1. Supplier invoices. When an invoice email lands in the accounts inbox, save the attachment to a SharePoint folder and post a note in the accounts channel in Teams.
2. Signed documents. When a signed contract is added to a SharePoint library, email the person who looks after that client.
3. Weekly follow-ups. Every Monday, post the week’s overdue items from a SharePoint list into the team’s Teams channel.

None of these needs AI. They’re rules, and the time comes back either way. Pick the one that costs you most, and write down what it costs you now, so you can tell afterwards whether the flow paid off.

Where does Copilot fit in Power Automate?

Copilot can build a flow for you. Microsoft’s page describes using “natural language to describe what you need through multiple steps of conversation” (Copilot in Power Automate, updated 18 August 2026). You describe the flow, check what it built and adjust it.

Microsoft’s FAQ lists the licences that can use it, and a Microsoft 365 licence with Power Automate rights is one of them (Copilot in cloud flows FAQ, updated 21 February 2026). Which Copilot each person has elsewhere in Microsoft 365 is a separate question, covered in Microsoft 365 Copilot pricing.

For environments in Australia, Copilot in Power Automate is on by default unless an admin turns it off (Power Automate regions, updated 19 August 2026). For those environments, Microsoft says the AI processing may happen in Australia or in the United States (Copilot data movement, updated 14 October 2026). It also says that if an admin leaves the “Move data across regions” setting off in the Power Platform admin center, no data is sent outside the region, though some Copilot features may not work. If your flows touch client information, ask your IT provider which way it’s set.

Until 1 November 2026, Power Automate Premium came with 5,000 AI Builder credits for its built-in AI features, and Microsoft’s licensing FAQs set that date for their removal (Power Platform licensing FAQs, updated 22 October 2026). Microsoft says AI Builder uses either AI Builder credits or Copilot Credits, depending on how it’s used, so check how AI features are billed before you plan around them.

Power Automate follows the steps you set. If you’re weighing tools that choose their own steps, I’ve covered whether your business should be using them yet.

How do you keep flows safe and running?

Set the data policies. In the Power Platform admin center, an admin sorts connectors into Business, Non-Business and Blocked groups. A flow can’t mix connectors from different groups, so, in Microsoft’s own example, “makers can’t create an app or flow that uses both the SharePoint and Gmail connectors” (connector classification, updated 8 April 2026). That control is a big part of why IT teams are comfortable with it.

Give important flows a second owner, and move ownership before anyone leaves. An automated or scheduled flow runs on its owner’s licence, and Microsoft’s limits page says “if the original owner leaves the organization, the flow reverts to the Low performance profile”. Add a co-owner so someone else can open and fix the flow. Then, before anyone leaves, change the owner of the flows the business relies on to another person or a properly licensed service account (change a flow’s owner, updated 25 September 2026). Microsoft’s ownership change works on flows kept in a solution, and the new owner’s licence can take up to seven days to apply. Keep a list of what runs.

Check where the data sits. Flows run in the region of the environment they belong to, and Australia is one of Microsoft’s regions. Microsoft is rolling out a change to how new environments are created. Unless a business has bought Microsoft’s Advanced Data Residency add-on for all its Microsoft 365 seats, an admin picks Asia-Pacific rather than Australia, and Microsoft places the environment in a data centre anywhere in that region, which also includes Singapore, India, Japan and South Korea (macro regions, updated 3 October 2026). Microsoft says it doesn’t expect existing environments to move from their region. If client data has to stay in Australia, have your IT provider check before you build.

Know which environment a flow lives in. Every tenant gets a default environment, shared by all its users, and Microsoft says it “shouldn’t be used for production workloads” (environments overview, updated 16 October 2026). For the flows the business relies on, Microsoft points to a production environment, which needs 1 GB of available database capacity. Ask your IT provider whether you have that capacity and where a new environment would sit.

What are Power Automate’s limits?

A few limits are worth knowing before you commit:

• Non-Microsoft apps. If most of your tools sit outside Microsoft, you may need premium or custom connectors, and the included rights cover neither.
• One premium step changes the licence. Microsoft’s licensing FAQ says that if an automated or scheduled flow uses a premium connector, only the flow’s owner needs Premium. If an instant flow, one someone starts with a button, uses a premium connector, everyone who runs it needs Premium, unless the flow has its own Process licence.
• Daily limits. Each licence comes with a daily allowance of actions. Microsoft’s official figure for a Microsoft 365 licence is 6,000 a user a day, though during the current transition period it applies 10,000 per flow instead (requests limits, updated 14 October 2026). A busy flow can use that up.
• The free Windows app is for personal use. Microsoft’s licensing guide calls the desktop app that comes with Windows “a free application not for business-critical functions, with no SLA or Microsoft support”. For anything the business depends on, plan for a paid licence.

Where should you start?

Pick one weekly job between Microsoft apps, and build it on what you already pay for.

1. Check your plan. In Power Automate, select Settings on the title bar, then View My Licenses. Microsoft includes Power Automate with Microsoft 365 Business Basic, Standard and Premium for flows that use standard connectors.
2. Pick the job. Something done by hand every week, like the examples above.
3. Build it with standard connectors. If it needs a premium connector, price the licence before you commit.
4. Give it a second owner, and write down what it does.
5. Ask your IT provider to check the data policies and the environment’s region. Both are in the Power Platform admin center, and Microsoft says the environment list shows each environment’s data location.

If you have an MSP, it may well be the right team for the build. I’ll help your team scope the flows and check they’re feasible, then hand that scope to your MSP to build. If you don’t have one, we’ll build it together. Either way, tell me about the job on a discovery call. Afterwards, I’ll come back to you with whether it’s worth automating and where it should run.

FAQ

Is Power Automate free with Microsoft 365?

For flows that use only standard connectors, Microsoft includes it. Microsoft 365 Business Basic, Standard and Premium, and E3, E5 and F3, come with limited Power Automate rights for Microsoft 365 data and standard connectors. Premium connectors, custom connectors and desktop flows run from cloud flows need a paid licence.

How much is Power Automate Premium in Australia?

AU$22.40 a user a month, paid yearly, before GST, on Microsoft’s Australian pricing page on 24 October 2026. Process was AU$224.50 a bot a month and Hosted Process AU$321.80, also paid yearly.

Is Power Automate better than Zapier?

For a business that runs on Microsoft 365, usually yes. It’s integrated with the apps you already use, and your IT team is more likely to approve it. If most of your apps aren’t Microsoft’s, Zapier connects to more of them.

Can Power Automate use AI?

Yes. Copilot can build a flow from a plain-language description, and for environments in Australia it’s on by default unless an admin turns it off. AI Builder adds more AI features, paid for with AI Builder credits or Copilot Credits, so check how those are billed first.

Can Power Automate keep data in Australia?

Flows run in the region of their environment, and Australia is one of Microsoft’s regions. For new environments, Microsoft is rolling out placement anywhere in its Asia-Pacific region unless the business has bought Advanced Data Residency for all its Microsoft 365 seats, so have your IT provider check the region before you build anything that touches client data.

General information only, not legal advice. Current as at October 2026: Microsoft’s Power Platform licences, prices and limits change often, and Microsoft Ignite (17-20 November) may change them again. Microsoft, Microsoft 365, Power Automate, Power Platform, Copilot, SharePoint, Outlook, Teams, Windows, Dataverse, Zapier, n8n and Amazon Web Services are trademarks of their respective owners. Korbai is independent and not affiliated with or endorsed by any of them.