Is Power Automate Free with Microsoft 365? What’s Included and When You Start Paying

Scenario: HR wants to automate onboarding, IT wants to avoid surprise bills

Imagine a mid‑size organisation:

• Everyone has Microsoft 365 E3 or Business Premium.
• HR wants a flow to automate onboarding: Teams message, SharePoint folder, Outlook welcome email, Planner task.
• A few power users start adding connectors for external tools (e‑signature, ticketing, custom APIs).
• IT suddenly sees Power Platform appear in licensing reports and asks: “Are we still within the Microsoft 365 entitlement, or do we need standalone Power Automate licences?”

We’ll use this scenario to anchor the discussion:

• What HR can do for free with Microsoft 365.
• Which extensions and integrations require paid Power Automate licences.
• How pricing works today for Romania.

What you actually get with Microsoft 365

Microsoft 365 includes rights to use Power Automate with the standard Microsoft 365 services your users are already licensed for.

In practice, with a typical Microsoft 365 E3 / Business Premium licence, a user can:

• Create and run cloud flows that use:
  • SharePoint, OneDrive for Business
  • Outlook (Exchange Online), Teams
  • Excel for web (in OneDrive/SharePoint)
  • Planner, To Do, Forms
  • Dataverse (with limitations depending on the licence)
• Build flows that trigger on:
  • New/changed items in SharePoint lists and libraries
  • Incoming emails in Exchange Online
  • New messages or events in Teams
  • Form submissions
• Use Power Automate in Microsoft 365 apps:
  • Approvals in Teams and SharePoint
  • Power Automate entry points in OneDrive/SharePoint document libraries

For our HR onboarding scenario, this means:

• Trigger: When a new item is created in a SharePoint list (New hire requests).
• Actions: Create Teams post, send Outlook email, create Planner task, create OneDrive folder.

All of that is covered by the Microsoft 365 licence. No standalone Power Automate licence is required as long as:

• The user creating the flow has the necessary Microsoft 365 licence.
• The flow only uses standard connectors tied to services you already own.

The key rule: licence must cover the data source

Power Automate usage is tied to the licence for the underlying service:

• If your flow writes to SharePoint, the user must be licensed for SharePoint (via Microsoft 365).
• If your flow uses Dataverse with premium features, you may need Power Apps / Power Automate per‑user or per‑app licences.

If a user doesn’t have a licence for a service, using that connector doesn’t magically grant rights; you’re out of compliance even if the flow technically runs.

Standard vs premium connectors: where “free” ends

The simplest way to explain when you start paying is: standard connectors are included with Microsoft 365, premium connectors are not.

Standard connectors (included with Microsoft 365, within licence scope)

Typical examples relevant to our scenario:

• Office 365 Outlook
• Office 365 Users
• Office 365 Groups
• SharePoint
• OneDrive for Business
• Microsoft Teams
• Planner
• Forms

If HR builds the onboarding flow with just these, you stay within your Microsoft 365 entitlement.

Premium connectors (require Power Automate / Power Apps licences)

Examples that often creep into onboarding and IT processes:

• SQL Server (cloud and on‑prem via gateway)
• Azure DevOps
• ServiceNow
• Salesforce
• Dynamics 365 (beyond the rights included with Dynamics licences)
• HTTP (Premium), Custom connectors
• SAP, Oracle, many third‑party SaaS connectors

As soon as a flow:

• Uses a premium connector, or
• Uses a custom connector, or
• Calls the Premium HTTP connector

…you’re in paid licence territory for the users who run or benefit from that flow.

In our scenario, if IT adds a step to create a ticket in ServiceNow using the ServiceNow connector, that flow now requires appropriate Power Automate licensing beyond Microsoft 365.

Current Power Automate pricing in Romania (cloud flows)

Microsoft lists Power Automate prices per user and per flow on its Romanian pricing pages, billed in EUR and RON. As of late 2026, typical public prices you will see are structured roughly like this (exact numbers vary by promotion and billing currency):

• Power Automate per user plan

  • One licence per user, that user can run unlimited flows (subject to usage limits) including premium connectors.
  • Price is shown per user/month, usually in the range of a mid‑tier SaaS licence when converted to RON.

• Power Automate per flow plan

  • A set number of flows (for example, a small bundle) that can be run by any user in the tenant.
  • Price is shown per flow/month, again in a similar mid‑tier SaaS range.

On the Romanian pages, you will typically see:

• Prices displayed both per month and per user/per flow.
• Separate lines for Power Automate vs Power Apps, plus add‑ons.

For exact current values you should:

1. Go to the official Microsoft Romania pricing page for Power Automate.
2. Check:
   • Currency (EUR vs RON).
   • Whether prices are for annual commitment or monthly.
   • Differences between commercial, government, and academic if relevant.

Licensing decisions should be based on those live values, not on any approximate numbers.

Where Microsoft 365 stops being enough in practice

For most teams, the “is Power Automate free” question shows up in a few repeat patterns.

1. You need premium connectors or custom APIs

Common triggers for needing standalone licences:

• Integrating with on‑prem SQL Server or third‑party SaaS.
• Calling internal APIs via HTTP.
• Using custom connectors to wrap bespoke services.

For the HR onboarding scenario:

• If you add an HTTP call to your internal HR system API to create the employee record, that’s a premium connector.
• If you wrap that API in a custom connector, that’s also premium.

You now need:

• Either a per user Power Automate licence for each user who runs or owns the flow.
• Or a per flow licence if you want the flow to be shared broadly without licensing each user.

2. RPA / Desktop flows

Robotic Process Automation (RPA) — the Power Automate for desktop side — is not covered by standard Microsoft 365 licences.

If you:

• Automate legacy desktop applications.
• Use desktop flows to click through a thick‑client HR or finance system.

…you’re in the desktop flows licensing model, which is separate and generally more expensive than basic cloud flows.

For onboarding, if HR wants to automate data entry into an old on‑prem HR application via the UI, that requires specific Power Automate RPA licences, not just Microsoft 365.

3. Higher capacity and governance needs

Even if you stay on standard connectors, you may outgrow Microsoft 365 entitlements when:

• Flow runs per user start hitting tenant limits.
• You need dedicated capacity or environments for Power Platform.

In those cases, organisations often:

• Add Power Apps / Power Automate capacity add‑ons.
• Move critical flows into environments backed by paid capacity.

This is less about “is it free” and more about “is it reliable at our scale”.

Mapping the HR onboarding scenario to licences

Let’s break down the HR flow and see where you pay.

Version 1 – fully covered by Microsoft 365

Steps:

1. Trigger: SharePoint list item created (New hire list).
2. Action: Create a folder in OneDrive or SharePoint document library.
3. Action: Send welcome email via Office 365 Outlook.
4. Action: Post a message in Teams to the hiring manager.
5. Action: Create a Planner task for IT.

Licence impact:

• All actions use standard connectors.
• All data sources are within Microsoft 365.
• Users need appropriate Microsoft 365 licences, but no standalone Power Automate.

Version 2 – integration with external HR system

Add:

6. Action: HTTP request to external HR system API (premium).

Licence impact:

• Flow now uses a premium connector.
• You need Power Automate licences for:
  • The user(s) who own and manage the flow.
  • Depending on your interpretation and governance, potentially the users who trigger or benefit from it.

Typical options:

• Per user plan: for HR automation specialists who build and maintain multiple flows.
• Per flow plan: if you want a few centrally‑managed flows to be used across the organisation without licensing every HR user.

Version 3 – RPA for legacy app

Replace the API call with:

6. Desktop flow that opens the legacy HR app and types data into fields.

Licence impact:

• Requires Power Automate RPA licensing.
• Not covered by standard Microsoft 365.

This is where costs jump; IT usually wants to see clear ROI before approving RPA licences.

Practical checks to avoid surprise costs

If you’re the person who will get blamed for a surprise bill, build a simple checklist into your flow design process.

1. Check connector type for every action

Before approving or publishing a flow:

• Open the flow in Power Automate.
• For each action, check the connector category:
  • Standard (OK under Microsoft 365, if the service is licensed).
  • Premium (requires extra licensing).

Microsoft’s connector docs and the Power Automate UI clearly mark premium connectors; don’t rely on memory.

2. Verify user licences for each data source

For each service a flow touches:

• Confirm that all relevant users have licences for that service.
• Example: if the flow writes to a SharePoint site only some users can access, make sure you’re not automating access for unlicensed users.

3. Decide per user vs per flow early

When you know you need premium capabilities:

• Per user licences make sense if:

  • You have a small group of makers building many flows.
  • Those flows are mostly internal to their department.

• Per flow licences make sense if:

  • You have a small number of business‑critical flows.
  • Those flows are triggered or used by many users across the organisation.

Use the live Romanian pricing page to compare these options with your user counts.

4. Keep RPA separate in your planning

Treat desktop flows as a separate project:

• Different licensing.
• Different infrastructure and governance.
• Often different cost/benefit profile.

Don’t let “we’ll just automate that screen” slip into a normal cloud‑flow discussion without checking RPA licensing.

A concrete takeaway for your next project

Before you approve the next Power Automate request, ask two questions:

1. Does the flow stay entirely within Microsoft 365 standard connectors?
   • If yes, you’re usually covered by existing Microsoft 365 licences.
2. Does it use any premium or custom connector, or desktop automation?
   • If yes, open the Romanian Power Automate pricing page, decide per user vs per flow vs RPA, and budget accordingly.

If you bake those two checks into your design and review process, you’ll stop treating “Is Power Automate free with Microsoft 365?” as a panic question and start using it as a simple gating decision for every new automation.