Last updated: October 14, 2026
By ZapAI Team
TL;DR: Most Microsoft 365 plans already include Power Automate cloud flows on standard connectors like SharePoint, Outlook, Teams, Forms, Planner, and Approvals, capped at 6,000 actions per user per day. That covers a surprising amount of business process automation. Premium connectors, Dataverse, custom connectors, and orchestrated RPA need Power Automate Premium at $15 per user per month. Build approvals and intake flows first, set data policies, and buy Premium only for the flows that need it.
Microsoft 365 business licenses include Power Automate cloud flows with standard connectors such as SharePoint, Outlook, Teams, Forms, and Approvals. Premium connectors, Dataverse, custom connectors, and cloud-triggered desktop flows require Power Automate Premium at $15 per user per month.
A familiar scene. A company pays for 200 Microsoft 365 seats, then asks for a quote on a separate workflow tool because invoice approvals still run through forwarded emails and a shared spreadsheet. The automation engine was sitting in their tenant the whole time.
So what does business process automation in Microsoft 365 actually cover with the licenses you already own? Where does the premium wall start? And what’s worth paying for?
For the broader method of picking and mapping processes, see our guide to automating business processes on Power Platform. Here we stay on licenses, limits, and first moves.
What Does Microsoft 365 Already Include for Business Process Automation?
Power Automate cloud flows that use standard connectors, at no extra cost. Each user gets 6,000 actions per day. Premium connectors, custom connectors, Dataverse storage, business process flows, and the on-premises gateway aren’t included.
Microsoft calls this a seeded license. Per Microsoft’s seeded license comparison on Learn, updated September 22, 2026, Microsoft 365 users can create and run cloud flows with standard connectors, at 6,000 actions per user per day. Premium connectors, custom connectors, attended and unattended RPA, process mining, AI Builder credits, and Dataverse storage all show Not included for Microsoft 365.
Six thousand actions sounds tiny. It isn’t. Every trigger, condition, and compose step counts, but a 15-step approval flow can still run a few hundred times a day for one owner before it gets close. The limit bites when someone builds a scheduled flow that loops through a 5,000-row list every hour. Don’t do that.
Two quieter extras are worth knowing. Select Microsoft 365 plans include Dataverse for Teams, a small database tied to one team (about 1 million rows, enforced as 2 GB), where flows can run without Premium. And Windows itself lets users author and run desktop flows locally in attended mode, with no cloud orchestration. Handy for one person’s repetitive clicks. Not a plan for a department.
Which Connectors Are Standard and Which Need Premium?
The Microsoft 365 workhorses are standard, including SharePoint, Outlook, Teams, Forms, Planner, Excel Online, OneDrive, and Approvals. Dataverse, Salesforce, SQL Server, Word templates, and the generic HTTP action are premium.
Microsoft keeps the official list of standard connectors on Learn, refreshed October 2, 2026. Check it before you promise anyone a flow. The table below covers the connectors and features that come up in nearly every first project.
| Capability | Included in Microsoft 365 | Needs Premium (or another license) |
|---|---|---|
| SharePoint, OneDrive, Excel Online (Business) | Yes, standard connectors | No |
| Office 365 Outlook, Office 365 Users, Teams | Yes, standard connectors | No |
| Microsoft Forms, Planner, Approvals | Yes, standard connectors | No |
| Some non-Microsoft apps (Gmail, Dropbox, Slack, Smartsheet, Trello, Adobe Acrobat Sign) | Yes, listed as standard | No |
| Word Online (Business), for filling Word templates and converting to PDF | No | Premium connector |
| Microsoft Dataverse, SQL Server, Salesforce | No | Premium connectors |
| Generic HTTP action and HTTP request trigger | No | Premium (SharePoint’s own HTTP action stays standard) |
| Custom connectors and on-premises data gateway | No | Premium |
| Cloud-triggered or shared desktop flows (attended RPA) | No | Premium, one attended bot per user |
| Unattended RPA | No | Process license, $150 per bot per month |
| Daily action limit | 6,000 per user | 40,000 per Premium user, 250,000 per Process license |
Word Online catches people out. HR builds a beautiful onboarding flow, then adds Populate a Microsoft Word template for the offer letter, and the whole flow flips to premium. One action. Whole flow.
Where Do Copilot Chat, Agents, and the Workflows Agent Fit?
Copilot Chat users can run agents your organization builds, billed on a metered basis. Microsoft 365 Copilot users build and use internal agents at no extra cost. The Workflows agent, which builds flows from plain English, is still a Frontier early-access feature.
Workflows is the one people ask about. Microsoft’s Workflows support article, last updated April 2026, says you describe what you want and the agent builds it from Outlook, Teams, SharePoint, Planner, and Approvals actions. The fine print? Frontier enrollment, a data policy that allows those connectors plus AI actions, no non-Microsoft or custom connectors, no sharing, English only. Fine for personal chores. Not yet a department tool.
Agents are a separate meter. On Microsoft’s Copilot Studio pricing page, Microsoft 365 Copilot is $30 per user per month paid yearly, and licensed users can build and use internal agents at no additional cost. Letting unlicensed users run an agent, or publishing it outside Microsoft 365, needs a Copilot Studio plan. Credit packs run $200 per month for 25,000 Copilot Credits, with pay-as-you-go available. If you’re weighing a Copilot Studio agent against a custom build, our Copilot Studio vs custom AI agents comparison walks through it.
What Should Each Department Automate First?
Start with approvals and intake that live entirely in SharePoint, Forms, Outlook, Teams, and Planner. Every example below runs on standard connectors, so it costs nothing beyond the licenses you already pay for.
- Finance. Invoices emailed to an AP mailbox get saved to a SharePoint library, metadata lands in a SharePoint list, and anything over a threshold goes through Approvals to the budget owner, with the result posted in a Teams channel. Swap the threshold for the one in your delegation-of-authority policy.
- HR onboarding? A Forms submission or SharePoint list item for each new hire creates Planner tasks for IT, facilities, and the manager, sends calendar invites for day one, and posts a welcome in Teams. Keep offer letters manual or budget Premium for Word templates.
- IT requests. Forms intake, a SharePoint list as the queue, the Office 365 Users connector to find each requester’s manager, and an approval only for hardware or software that costs money.
- Sales handoffs are the honest exception. If your deals live in Salesforce or Dataverse, the trigger is premium on day one. If they live in a SharePoint list or an Excel table (no judgment), a won deal can post to a delivery channel and spin up kickoff tasks for free.
Want more ideas once those work? Our list of Power Automate use cases goes further, including the premium ones.
When Do You Hit the Premium Wall, and What Does It Cost?
The moment a flow touches a premium connector, a custom connector, the gateway, or orchestrated RPA. Power Automate Premium is $15 per user per month, Process is $150 per bot or flow, and Hosted Process is $215.
Those are US list prices from Microsoft’s Power Automate pricing page, paid yearly, checked October 14, 2026. Premium covers cloud flows on any connector, one attended bot, process and task mining, and 250 MB of Dataverse database capacity per license. Process gives one unattended bot or licenses a single cloud flow for everyone who uses it. Hosted Process adds a Microsoft-hosted virtual machine, so nobody babysits a bot server.
Run the math for a 40-person finance team. Premium for everyone is $600 a month, or $7,200 a year. Usually you don’t need everyone, though, which is the next section. For the full catalog of Power Apps, Power BI, Dataverse, and Copilot Studio prices, see our Power Platform licensing breakdown.
Unattended bots have one more catch. Microsoft’s FAQ notes that unattended RPA touching Microsoft 365 apps also requires the Microsoft 365 Unattended License. Budget for it early. If you’re comparing desktop automation platforms, our Power Automate vs UiPath breakdown covers that decision.
Who Actually Needs a Premium License?
For automated and scheduled flows, only the flow owner. For instant flows started by a button or an app, every user who runs it. And if users get value back from a premium flow, they need licenses too.
Microsoft’s Power Automate licensing FAQ, updated September 22, 2026, states the owner rule plainly. Then it adds the part most teams skip. Multiplexing.
Take a simple example. A premium flow fires when anyone adds an item to a SharePoint list, writes it to Dataverse, and emails only the flow owner. Only the owner needs Premium. Change that flow so it emails the person who submitted the item, and now every submitter needs a Premium license, because they indirectly trigger the flow and get value from it. Same flow. Very different bill.
Service accounts don’t dodge this either. Microsoft says one Premium license on a service account shared by a crowd isn’t compliant. When usage is broad, put a Process license on the flow instead. And if a license lapses? The flow gets downgraded, owners are notified, and it turns off after 14 days if nobody acts. Better to learn that here than from an angry AP clerk.
What Governance Do You Need Before Anyone Builds?
Data policies first, then an environment strategy. Managed Environments come later, because every active user in one needs a premium license, and Microsoft 365 seeded rights don’t qualify.
Data policies (still called DLP by most admins) sort connectors into Business, Non-business, and Blocked groups, so a flow can’t move SharePoint data into a personal Dropbox. Microsoft’s data policies overview explains that violating flows get suspended, and that enforcement usually lands within an hour but can take up to 24 hours. So test a policy change on a Friday morning, not Friday at 5 PM.
Environments are next. Every licensed user can build in the default environment, which turns it into everybody’s junk drawer within a year. Keep the default for personal productivity flows, and create a separate environment for anything a department depends on.
Managed Environments add usage insights, sharing limits, and stronger controls. The licensing is strict, though. Per Microsoft’s Managed Environments licensing page, every user running a cloud flow there needs Power Apps Premium, Power Automate Premium, or a qualifying Dynamics 365 license. In-app license notices started in June 2026, and starting February 2027 unlicensed users get blocked from opening apps in those environments. Turning on Managed Environments for a tenant of Microsoft 365-only users is a licensing decision, not a checkbox.
When Should You Step Up to Premium, Copilot Studio, or a Consultant?
Buy Premium for the few people who own flows that need ERP, CRM, or SQL data. Add Copilot Studio when people need to ask an agent for answers or actions. Bring in help when flows cross departments, systems, or audit scope.
- Your finance flow needs vendor data from Dataverse, Salesforce, or SQL Server. License the owner with Premium, or put a Process license on the flow if it’s instant and widely used.
- Requests arrive as messy emails or chat questions instead of clean forms. That’s agent territory, and our Copilot Studio services team scopes those builds.
- A legacy desktop app with no API sits in the middle of the process. Now you’re pricing RPA bots, not connectors.
- Twenty flows, five owners, nobody documenting anything. Governance debt. Fix it before adding flow number twenty-one.
Bias disclosed, since we sell implementation work. Plenty of companies never need us for the standard-connector tier. A capable admin with a Microsoft 365 license can build the department flows above in an afternoon each.
Wrapping Up
Your Microsoft 365 licenses already cover approvals, intake, notifications, and task handoffs across SharePoint, Outlook, Teams, Forms, and Planner. Premium starts when a flow touches Dataverse, a CRM, SQL, Word templates, HTTP, or RPA, and the owner rule plus multiplexing decide who pays. Set data policies before the first flow goes live.
ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric, and AI consulting firm based in Irving, Texas, helping US businesses get more out of the Microsoft stack they already pay for. If you’d like a flow-by-flow map of what runs on your current licenses and where Premium pays for itself, our Power Automate consulting team can build it from your actual processes.
Questions IT and Ops Leaders Ask About Microsoft 365 Automation
Is Power Automate really free with Microsoft 365?
For standard connectors, effectively yes. Microsoft 365 licenses include cloud flows on connectors like SharePoint, Outlook, Teams, and Approvals at 6,000 actions per user per day, with no extra charge.
Are approvals a premium feature?
They’re standard, which surprises people. Microsoft lists the Approvals connector in the standard tier, so approval flows built on SharePoint, Forms, and Outlook run on Microsoft 365 licenses. The premium trap is usually something else in the same flow, like a Word template or a Dataverse step.
Standard vs premium connectors, how do we tell which is which?
Look for the Premium label in the Power Automate designer, or check Microsoft’s standard connector list on Learn before you build. A single premium action makes the whole flow premium.
Do all 300 employees need Premium if one flow uses Salesforce?
Probably not. If it’s an automated or scheduled flow and only the owner benefits, the owner’s Premium license covers it. If it’s an instant flow, or submitters receive something back from it, each of those users needs Premium, or you license the flow itself with a $150 per month Process license. That second option is usually cheaper once more than ten people touch the flow, since ten Premium seats already cost $150.
Can the Workflows agent replace Power Automate?
Not today. It’s a Frontier early-access feature limited to Microsoft connectors, its workflows can’t be shared, and Microsoft itself points users to Power Automate for advanced or non-Microsoft scenarios.
What breaks first when automation grows without governance?
Ownership. A flow built by someone who leaves keeps running on their connections until it doesn’t, and nobody knows what it did. Set data policies, use a separate environment for department flows, and give every production flow two named owners.