Is Power Automate Free With Microsoft 365? What You Really Get, and When You Cross the 13 EUR Line

Scenario: A finance team, one SharePoint library, and a creeping scope

Imagine a finance/operations team of 15 people.

They already have:

• Microsoft 365 E3 (or Business Standard)
• SharePoint Online for document libraries
• Exchange Online mailboxes
• One small Power BI workspace

The team wants to automate:

1. Invoice intake – when a supplier sends a PDF to invoices@company, save it in SharePoint.
2. Approval workflow – route the invoice to the right approver based on cost centre.
3. Posting support – push approved invoice data into their accounting system.

They start with 1 and 2. Everything looks “free” because Power Automate appears in the Microsoft 365 app launcher. The trouble begins with step 3, when someone says: “Let’s integrate with the accounting SaaS API and maybe our on‑prem ERP too.”

That’s where you cross the 13 EUR per user per month line.

What you actually get “for free” with Microsoft 365

Power Automate capabilities are included with most Microsoft 365 licences, but they’re not unlimited and they’re scoped to Microsoft 365‑connected scenarios. You get:

• Standard connectors
  • SharePoint, OneDrive, Outlook, Excel Online, Teams
  • Many common SaaS apps marked as Standard in the connector list
• Cloud flows
  • Automated, instant, scheduled flows running in the cloud
  • Use of Dataverse only within the limits of your Microsoft 365 plan (if you have it)
• Basic approvals and notifications
  • The Approvals connector
  • Adaptive cards in Teams
  • Email alerts, reminders
• Limited Power Platform capacity
  • Some environment, API, and Dataverse capacity bundled with Microsoft 365

For our finance scenario, this means you can build, without extra licence cost:

• A flow triggered by new email in Exchange Online
• Save attachments to SharePoint Online
• Start an approval in Teams or via email
• Update a SharePoint list with approval status

All of that is covered by Microsoft 365. No standalone Power Automate Premium licence needed.

Quick way to check: connector type

Open the connector list in Power Automate and look at the connector badges:

• Standard – generally covered by Microsoft 365 (subject to capacity and your specific plan)
• Premium – requires a Power Automate Premium or equivalent licence
• Custom connector – treated as Premium usage

If your flow uses only Standard connectors and no custom connectors, you’re usually still in the Microsoft 365 zone.

Where the 13 EUR line starts: Premium and “Process” licences

Polish buyers often see two price points quoted, similar to the JFlow Labs framing:

• Power Automate Premium – around 13 EUR net per user per month
• Power Automate Process – around 130 EUR net per bot per month

Actual prices vary by region and agreement, but the ratio and positioning are stable:

• Premium = per user licence
• Process = per bot / per flow licence for unattended scenarios

Premium licence – what changes for our finance team

Once a user has a Power Automate Premium licence, they can:

• Use Premium connectors (e.g. many ERP, CRM, and finance SaaS APIs)
• Use custom connectors to call any REST API
• Use on-premises data gateway to reach SQL Server, on‑prem ERP, etc.
• Run desktop flows (Power Automate Desktop) with attended RPA

In our scenario, crossing the 13 EUR line happens when the team wants to:

1. Call the accounting SaaS API using a Premium connector or custom connector.
2. Read/write data in on‑prem SQL Server via the gateway.
3. Automate the legacy accounting client using desktop flows.

The moment any of those enter the design, you’re in Premium territory.

Process licence – when 130 EUR per bot makes sense

The Process licence is aimed at:

• High‑volume, unattended desktop flows (bots running without a user logged in)
• Line‑of‑business processes where you don’t want to licence many individual users

For the finance team, this becomes relevant if they say:

“We want a bot that runs on a VM, 24/7, reading invoices from a folder and punching them into the old ERP client, with no one watching.”

That’s typically Process licence territory, not just Premium per user.

Detailed scenario walk‑through: what’s free, what isn’t

Let’s map the three steps of our finance workflow to licence boundaries.

Step 1: Invoice intake via email and SharePoint – still Microsoft 365

Flow outline:

• Trigger: When a new email arrives (V3) – Outlook connector (Standard)
• Condition: Check sender, subject, or keywords
• Action: Create file in SharePoint document library (Standard)

All of this is covered by Microsoft 365.

You might also:

• Create/update a SharePoint list item with metadata
• Send a Teams message to the finance channel

Still Standard connectors.

Step 2: Approval routing – still Microsoft 365

Flow outline:

• Trigger: When a file is created in SharePoint (Standard)
• Action: Start and wait for an approval (Approvals connector – included)
• Action: Post adaptive card in Teams (Standard)
• Action: Update SharePoint with approval result

As long as you stay inside:

• Exchange Online
• SharePoint Online
• Teams
• Approvals

…you’re still in the Microsoft 365 licence.

Step 3: Posting to accounting system – where Premium appears

Here the team has three options, with different licence implications.

Option A: Accounting SaaS has a Standard connector

If the accounting system exposes a Standard connector, you can:

• Use that connector in your flow
• Stay within Microsoft 365 (subject to any app‑specific licence)

This is the best case: no extra standalone Power Automate licence.

Option B: Accounting SaaS has a Premium connector

If the connector is marked Premium:

• Every user who runs flows using that connector needs a Premium licence
• The flow itself can live in the same environment, but execution is controlled by user licensing

For our finance team, this typically means:

• Approvers who only click Approve/Reject in email/Teams may stay on Microsoft 365
• Users who trigger or own flows using the Premium connector need Premium

Option C: Custom connector or HTTP to API / on‑prem gateway

If you build a custom connector or use the HTTP action to call an API:

• This is treated as Premium usage

If you use the on‑premises data gateway to reach:

• SQL Server
• On‑prem ERP
• File shares

…that also falls under Premium.

In practice, the moment you wire Power Automate into non‑Microsoft 365 data sources, plan for Premium.

Desktop flows and RPA: where the 130 EUR bot licence shows up

Our finance team may want to automate a legacy accounting client that has no API.

They can use Power Automate Desktop to:

• Record UI actions (clicks, keystrokes)
• Extract data from PDFs or UI controls
• Run flows on a local machine or VM

Licensing split:

• Attended RPA (user is logged in, watching or triggering the run)
  • Covered by Power Automate Premium per user
• Unattended RPA (bot runs without a user session)
  • Requires Process licence (per bot / per flow)

For the finance team:

• If one analyst runs the desktop flow on their machine when needed → Premium
• If they schedule it on a VM to run overnight without a user → Process licence

That’s where the ~130 EUR per bot per month framing becomes relevant.

Practical checks before you cross the 13 EUR line

Before you tell management “we need Premium”, do three concrete checks.

1. Connector audit of your flows

Open each flow and list the connectors:

• If all are Standard, you’re likely safe on Microsoft 365
• If any are Premium or Custom, you’re in Premium territory

Do this before building complex solutions. It’s much easier to redesign early.

2. User roles vs. licence needs

Not everyone needs Premium.

• Needs Premium:
  • Users who create and own flows using Premium/custom connectors
  • Users who run Premium desktop flows
• Can stay on Microsoft 365:
  • Approvers using email/Teams only
  • Users interacting only via SharePoint lists or Teams messages

Map your finance team roles to this split. Often you can keep Premium licences to a small subset.

3. Environment strategy

Use environments to separate:

• Microsoft 365 workflows (Standard only)
• Premium workflows (custom connectors, on‑prem gateway, RPA)

Benefits:

• Clear boundary for governance and cost
• Easier to apply DLP (Data Loss Prevention) policies
• Cleaner communication to stakeholders: “This environment requires Premium.”

Common misconceptions that cause licence surprises

Experienced practitioners still run into a few traps.

“Power Automate is free because it’s in the app launcher”

Access to the product UI is included, but:

• Premium connectors and desktop flows are not fully covered by Microsoft 365
• Capacity limits (API calls, Dataverse, etc.) still apply

“If only one person builds the flow, only they need Premium”

Execution and interaction matter.

• Users who trigger Premium flows or run Premium desktop flows also need appropriate licensing
• For flows triggered by system events (e.g. new item in SharePoint) and affecting many users, you need to align usage with licence rules, not just creator identity

“Approvals always need Premium”

The Approvals connector and basic approval scenarios are included with Microsoft 365.

You cross into Premium only when the flow uses Premium connectors or features beyond that.

One concrete takeaway for your next project

Before you design your next Power Automate solution, especially one touching finance or ERP, do a connector-first design review: decide which systems you’ll integrate, check each connector’s Standard/Premium status, and map that to user roles. That single step will tell you whether you can stay inside Microsoft 365 or you’re about to cross the 13 EUR Premium line – before you write a single action.