You have found a repetitive process, mapped the steps, and decided Power Automate could handle it. Then the licensing question stops the project cold: is Power Automate already included with Microsoft 365, or does everyone need Premium?
The honest answer is it depends on the connectors, how the flow starts, and who uses it. You do not automatically need Power Automate Premium for every useful workflow. You also should not assume that one Premium licence covers an entire team.
Here is the practical way to work it out before you build.
Licensing checked against Microsoft guidance available August 17, 2026. Verify the current terms for your exact licences before purchasing or deploying.
Is Power Automate included with Microsoft 365?
Select Microsoft 365 and Office 365 licences include limited Power Automate rights for automated, scheduled, and button flows using standard connectors. Microsoft describes the Office 365 entitlement as supporting personal-productivity scenarios and recommends Power Automate Premium for enterprise scenarios. Current standard connectors include SharePoint, Office 365 Outlook, Microsoft Teams, Excel Online (Business), and Approvals.
You are more likely to need Power Automate Premium, a Process licence, or another entitlement when the workflow uses:
- a connector marked Premium;
- a custom connector;
- an on-premises gateway;
- attended desktop automation that must be shared, centrally managed, run outside the default environment, or triggered through Power Automate—or unattended desktop automation;
- AI Builder or another capacity-based feature; or
- a premium flow that many people need to run manually.
Microsoft's Power Automate licensing FAQ and licence-type overview are useful current guidance. Verify the Power Platform Licensing Guide and the terms that apply to your agreement before purchasing or deploying. Connector classifications and plan terms can change.
Start with the connectors, not the flow diagram
A flow can have many steps and still use only standard connectors. Another can be short and require Premium because one step calls a premium service.
List every system the workflow needs to read from or write to. Then check each one in Microsoft's current connector reference. Do not rely on an old screenshot, a forum answer, or the licence used for a different flow.
For example, a workflow that watches a SharePoint list, sends a Teams message, requests an approval, and updates the list may fit within the limited Power Automate rights included with an eligible Microsoft 365 licence. Add a premium connector or a custom API, and the licensing decision changes.
That is why licensing belongs in discovery. It is part of the solution design, not a purchase you make after the flow is finished.
Who actually needs the licence?
This is where most of the confusion comes from. The answer changes with the way the flow is triggered.
Automated and scheduled flows
Automated flows start when something happens, such as a new list item arriving. Scheduled flows run at a set time. Microsoft's current guidance says these flows use the owner's licensing context.
If an automated or scheduled flow uses premium features, the owner needs the appropriate Premium entitlement, or the flow can be assigned suitable Process capacity. A person whose action happens to trigger the automated flow does not need Premium solely for causing that trigger.
Instant and app-triggered flows
Instant flows start when someone presses a button or deliberately runs the flow. For a standalone instant flow that uses premium connectors, Microsoft says each person who invokes it needs Power Automate Premium unless the flow is covered by Process capacity.
A Power Apps- or Dynamics 365-triggered flow that is properly associated with and used in the context of the licensed app may instead use the invoking user's Power Apps Premium or Dynamics 365 entitlement. A premium button used by a large team may be better evaluated for Process capacity.
People who only approve or reject
Approvers are a useful exception. Microsoft's FAQ says someone who only responds to an approval request does not need Power Automate Premium solely to approve or reject it. The flow still needs the correct licence for any premium actions it performs.
Service accounts are not a shortcut
Putting one Premium licence on a shared service account does not automatically license everyone using a premium flow. Microsoft calls it non-compliant multiplexing when one licensed account is used to give a larger unlicensed group access to premium automation.
Critical or widely shared workflows need a specific ownership and licensing check so they do not stop when an employee leaves or loses a licence. This is worth deciding before launch, not during an outage.
Premium user licence or Process licence?
The two choices solve different problems.
Power Automate Premium is assigned to a user. It can cover that user's cloud flows with standard, premium, and custom connectors within Microsoft's current plan limits. It also includes attended desktop-flow rights and other entitlements described in the licence documentation.
Power Automate Process assigns capacity to eligible flows or machines rather than a person. For eligible cloud flows, it can cover premium and custom connectors regardless of the owner or invoking users' individual licences. Microsoft also supports assigning Process capacity through flow groups, so confirm the current allocation rules for the proposed design. Process is worth evaluating when a premium process is shared broadly, needs an ownership model that is not tied to one employee, or uses unattended desktop automation.
Hosted Process adds a Microsoft-hosted machine for unattended desktop automation. That is a different requirement from an ordinary cloud workflow and should not be the default choice.
Do not choose between these plans by comparing sticker prices alone. Compare the number of users, trigger type, connector tiers, ownership model, support needs, and how the workflow may grow. Microsoft maintains the current Canadian plan details on its Power Automate pricing page.
Dataverse, desktop flows, and AI Builder need a closer look
Some features make a simple yes-or-no answer risky.
Dataverse
Full Dataverse use, Dataverse for Teams, Power Apps, and Dynamics 365 can carry different use rights depending on the app context and the licences involved. A flow that is properly associated with a licensed Power App can be treated differently from an unrelated standalone flow.
If Dataverse is part of the design, map the app, flow, data sources, and user licences together. My plain-language Dataverse guide can help with the platform decision, but the final licensing check still needs current Microsoft guidance.
Desktop automation
Power Automate Premium includes attended desktop-flow rights for a licensed user. Unattended desktop automation requires Process or Hosted Process capacity under Microsoft's current plan model. The people who build and manage the automation, and the account behind the desktop connection, can also need appropriate user entitlements. If the workflow must operate a desktop application without a person present, treat that as a separate licensing and infrastructure decision.
AI Builder
AI Builder actions consume AI Builder credits or Copilot Credits, but adding an AI Builder action by itself does not turn a Power Automate flow into a premium flow. As of August 17, 2026, Microsoft says the credits seeded by Power Automate Premium and Process will be removed on November 1, 2026, and new customers use Copilot Credits instead of buying an AI Builder capacity add-on. Estimate the model usage and confirm the current AI Builder licensing guidance before deployment.
A practical workflow check
Use this as a starting point, not a substitute for checking your exact Microsoft licences.
- Automated workflow using only standard Microsoft 365 connectors: limited Microsoft 365 rights may be enough. Verify the exact SKU, connector tiers, owner, intended business use, and action limits.
- Automated or scheduled flow using a premium or custom connector: evaluate Premium for the owner or Process for the flow. Verify the connector classification, ownership, solution requirements, and expected scale.
- Standalone instant premium flow run by several people: evaluate Premium for each invoker or Process for the flow. Confirm how many people will run it and whether app-context rights apply.
- Approval recipients who only approve or reject: Premium is not required solely for the response. Confirm that recipients do not perform another premium action.
- Unattended desktop automation: evaluate Process or Hosted Process, plus the required user entitlements. Confirm the machine, environment, security, concurrency, connection, and support model.
- AI document processing: confirm available AI Builder or Copilot Credits. Premium is needed only if another part of the flow requires it.
Five questions to answer before you build
- Which exact Microsoft 365 licences do the users already have? “We have Microsoft 365” is not specific enough. Check the actual SKUs against Microsoft's current Power Platform Licensing Guide.
- Which connectors will the flow use? Include every trigger and action, then confirm whether each connector is standard or premium.
- How does the flow start? Automated and scheduled flows are licensed differently from flows that users invoke manually.
- Who owns, runs, and benefits from it? Those may be different people, and that difference can affect licensing.
- Will the design need desktop automation, AI Builder, an on-premises gateway, guests, or custom APIs? Each one deserves a specific licensing check.
If those answers are unclear, do not buy licences yet. Sketch the workflow first. A short discovery step is cheaper than rebuilding the solution around a licensing assumption.
When Premium is worth it—and when it is not
Premium is worth considering when it unlocks a high-value connection, gives a shared process the right ownership model, or removes enough manual handling to justify the ongoing cost.
It is not automatically the right answer because a workflow sounds important. If standard connectors can solve the problem cleanly, adding premium components may create cost and support work without improving the outcome.
The opposite mistake is forcing every process into standard connectors to avoid a licence. A fragile workaround that needs constant attention can cost more than the correct entitlement. Choose the simplest design that is reliable, supportable, and properly licensed.
For examples of the processes Power Automate can handle, see five practical workflow patterns.
The takeaway
You may not need Power Automate Premium when an eligible Microsoft 365 licence and standard connectors cover the workflow. You are more likely to need it when premium connectors, custom integrations, desktop automation, or broad manual use enter the design.
Confirm the licences, connectors, trigger, owner, and users before anyone starts building. If you are not sure how those pieces fit together, tell me what the process looks like. I can help you identify the licensing questions that need answers before you build.