Our 40-person CPA practice has Microsoft 365 Business Premium. Does that cover a document-handoff workflow, or do we need Power Automate Premium or Process?
Business Premium covers a document-handoff flow when every connector in it is a standard connector, such as SharePoint, OneDrive or Outlook, and the flow runs in the cloud. Microsoft's licensing FAQ says plainly: if the flow doesn't use a premium connector, you don't need a Premium license. Add a premium or custom connector, unattended desktop automation, or many people invoking a premium flow, and you need Power Automate Premium per user or a Process licence on the flow.
The word Premium in Business Premium is a trap. Business Premium is a Microsoft 365 suite name. Power Automate Premium is a separate per-user licence. Owning the first grants the seeded Power Automate rights that ship with Microsoft 365, and nothing in the suite name upgrades those rights to premium connectors.
Which licence fits which workflow
- Included Microsoft 365 rights fit a cloud flow built only on standard connectors, running under an enabled Power Automate service plan in your actual SKU; avoid them the moment the flow touches a premium or custom connector or needs unattended desktop runs.
- Power Automate Premium per user fits a small, named set of staff who build or run flows with premium or custom connectors, or who need attended desktop automation; avoid it as a single shared account that many people trigger, which Microsoft calls multiplexing.
- A Process licence fits a shared premium workflow where licensing the flow is cheaper or cleaner than licensing everyone who invokes it, or where an unattended bot is required; avoid assuming one Process assignment on a parent flow automatically covers every child flow or every environment.
Recommendation for a typical CPA document handoff
Most CPA document handoffs, such as moving a signed engagement letter from an Outlook attachment into a client folder in SharePoint and notifying the assigned preparer in Teams, stay inside standard connectors. For that shape of workflow, build on the Microsoft 365 rights you already pay for and buy nothing extra.
The one condition that changes the answer is a premium or custom connector entering the design. Pushing client data into a SQL database, calling a tax or practice-management system over the HTTP connector, or writing to Dataverse all move the flow into premium territory, and from that point the question becomes per-user Premium versus Process.
Between those two, headcount drives the choice. If two or three staff own and run the premium flow, per-user Premium is simpler. If the flow is instant and the whole practice triggers it, Microsoft's FAQ is explicit: every user who runs an instant flow with premium connectors needs a Premium licence, or you license the flow itself with Process instead.
Where the boundaries get fuzzy, Chrysis Networks maps the connectors, triggers and owners of the proposed workflow before anyone quotes a build, so the licensing question is settled on paper first.
Trigger type decides whose licence counts
Microsoft's FAQ, last updated 2026-09-22, states that automated and scheduled flows always run in the context of the flow owner, regardless of who starts the flow or which accounts the connections use. A premium flow triggered when a file lands in SharePoint therefore leans on the owner's entitlement, while an instant flow started by a button press leans on each person who presses it.
Owner context is not a free pass. The same Microsoft page warns that assigning a single Power Automate Premium licence to a service account that many users share is multiplexing, and the flow isn't compliant. Its examples about indirect beneficiaries, including a SharePoint-triggered flow writing to SQL, don't line up perfectly with a simple owner-only reading, so treat any shared premium flow as a case for written confirmation from your Microsoft licensing partner.
A one-page licensing inventory before you build
- Confirm the purchased SKU and service plan. Ask the tenant administrator to check the Microsoft 365 admin center under Billing, Your products, and confirm the Power Automate for Office 365 service plan is enabled. Microsoft's seeded-capability table still uses the older name Office 365 Business Premium, so match on the plan, not the marketing name.
- List every connector the flow will use and mark each one standard, premium or custom, using the label shown in the Power Automate designer.
- Record the trigger type for each flow: automated, scheduled or instant.
- Name the flow owner and every person who will start the flow or depend on its output.
- Note the environment the flow lives in and any parent and child flows it calls.
- Check the result against the Microsoft FAQ. If any row involves a premium connector with multiple invoking users or an unattended desktop step, get scenario-specific confirmation before buying.
- Keep the current staff-run handoff and a dated shared work log in place until the entitlement question is closed. The manual process costs nothing extra and protects you from running a non-compliant flow in the meantime.
Staff count matters far less than most firms expect. A 40-person practice and a 90-person practice running the same standard-connector flow have the same licensing answer, while a 12-person practice with one premium instant flow used by everyone may need more licences than either.
Microsoft's Power Apps and Power Automate licensing FAQ, with page metadata dated 2026-10-08 and updated 2026-10-22, lists Power Automate Premium as licensed per user. Those are documentation dates; neither page announces a new licensing change or an effective date for one.
Frequently asked
Does Microsoft 365 Business Premium include Power Automate Premium?
No. Business Premium includes the seeded Microsoft 365 Power Automate rights for standard connectors; Power Automate Premium is a separate per-user licence.
Are SharePoint, Outlook and Teams premium connectors?
No. They are standard connectors, so a flow built only on them can run on included Microsoft 365 rights.
Can we buy one Premium licence for a shared service account and let everyone use the flow?
No. Microsoft describes that as multiplexing and says the flow isn't compliant.
When is a Process licence better than per-user Premium?
When a premium flow is shared by many invoking users, or when you need unattended automation, licensing the flow with Process can replace licensing every user.
Does staff count decide which licence we need?
Rarely on its own. Connector type, trigger type and who invokes the flow decide it.