Power Automate Pricing for Enterprise: 2026 Plans & Hidden Costs

Power Automate's list pricing starts at zero (with a Microsoft 365 subscription) and moves through three main paid tiers: $15 per user per month for Premium, $150 per bot per month for Process, and $215 per bot per month for Hosted Process.

For enterprise buyers, the meaningful number is total cost of ownership, and it's typically substantially higher than the list price alone. Premium connectors, AI Builder credits, Dataverse storage, and per-flow versus per-user licensing decisions can all push a mid-size enterprise deployment several times above the entry-level figure.

(All prices correct as of September 2026, see Microsoft's current Power Automate pricing page for the latest.)

Below is a full breakdown of the pricing structure, the additional costs enterprise buyers typically miss, a worked example of total cost of ownership at mid-size, and the specific scenarios where Power Automate's pricing model becomes disproportionately expensive.

Power Automate licensing tiers explained

Power Automate's licensing is structured around four main tiers, each with a different pricing model and a different fit for enterprise use.

Included with Microsoft 365

• If your organization already has a qualifying Microsoft 365 subscription, users can build and run cloud flows that use standard connectors only.

• Standard connectors cover the Microsoft-native stack (SharePoint, Outlook, Teams, OneDrive, Excel, Forms, and Planner) and are enough to support internal automation between Microsoft 365 apps.

• This tier has daily API request limits and doesn't include premium connectors, RPA, or AI Builder.

Premium (per user)

• $15 per user per month, billed annually. Unlocks unlimited cloud flows, all 600+ premium connectors, attended desktop RPA, AI Builder credits, and Dataverse storage (250 MB database and 2 GB file storage per user).

• This is the standard tier for any user who needs to connect to a non-Microsoft system or run automations against premium data sources.

Process (per bot)

• $150 per bot per month, billed annually. Licenses the automation itself rather than the users, so a single shared workflow can serve unlimited users under one license. Includes unattended RPA capabilities.

• This tier was renamed from "Per Flow" during Microsoft's 2023 licensing consolidation, and the underlying model is per-workflow rather than per-user.

Hosted Process (per bot)

• $215 per bot per month, billed annually. Same as Process but adds a Microsoft-hosted virtual machine, removing the need for on-premises infrastructure to run unattended RPA.

• Best fit for regulated industries or high-volume unattended automation where infrastructure management is a burden.

Beyond these subscription plans, Microsoft also offers pay-as-you-go pricing at $0.60 per premium cloud flow run, billed through an Azure subscription. This suits organizations with variable or unpredictable automation volume, or workflows that don't fit a per-user or per-bot model cleanly.

Hidden and additional costs

The three tiers above cover platform access. The costs that add up beyond them are where enterprise TCO models most often go wrong.

Premium connectors for enterprise systems

• Standard connectors cover Microsoft 365. Everything else (Salesforce, SAP, Oracle, ServiceNow, SQL Server, HTTP, and custom APIs) sits behind premium licensing.

• Every user who runs a flow touching a premium connector needs their own Premium license, or the flow needs Process licensing.

• This is where teams get caught, a single Salesforce integration built by one developer can require 12 Premium licenses if 12 people submit against the resulting workflow.

AI Builder credits and the November 2026 packaging change

• Premium and Process licenses have historically included around 5,000 AI Builder credits per user per month.

• Microsoft has announced that these seeded credits will be removed on 1 November 2026. From that date, AI Builder features draw on Copilot Credits or a paid AI Builder capacity add-on ($500 per 1 million credits per month).

• Capacity add-ons already stopped being sold to new customers as of November 2025.

• For any enterprise deployment that relies on document processing, prediction, or text recognition inside flows, this is a genuine budget line to plan for rather than an incidental included feature.

Dataverse storage

• Premium and Process licenses include modest Dataverse storage per user (250 MB database, 2 GB file).

• Enterprise deployments that use Dataverse as the underlying data store for structured workflow data can exceed these allowances quickly, and additional Dataverse capacity is billed on a per-GB basis on top of licensing.

Process Mining and other add-ons

• Process Mining is available as an add-on at $5,000 per tenant per month.

• Additional Power Platform Request packs ($50/month for 10,000 daily requests) become necessary when a user or flow exceeds its daily API limit under heavy use.

Per-flow versus per-user licensing traps

• The Process (per bot) tier at $150 per month becomes cheaper than per-user licensing when a shared automation is used by roughly 11 or more people. Below that threshold, per-user is more cost-effective.

• Getting this decision wrong in either direction costs money, and teams often default to per-user because it's easier to procure, even when Process licensing would have been substantially cheaper for their specific workload.

A worked example of total cost of ownership

To make the TCO picture concrete, here's a worked example for a hypothetical mid-size enterprise deployment. The numbers are illustrative rather than a quote, and depend on the actual mix of premium connectors, RPA needs, and Dataverse usage in the specific workload.

Scenario

A 500-employee professional services firm. Fifty users need to interact with automated workflows across HR (onboarding, holiday requests, appraisals), finance (expense claims, purchase orders), and IT (access requests, ticketing). Most workflows connect to internal SharePoint and Teams, but four workflows also touch Salesforce (CRM), SAP (ERP), and DocuSign (contract signing), which are all premium connectors.

Licensing build-up (correct as of September 2026):

• 50 users at Premium ($15 per user per month) = $9,000 per year for platform access with premium connectors
• 3 Process bots for unattended overnight tasks ($150 per bot per month) = $5,400 per year
• Additional AI Builder capacity (once the November 2026 seeded credit change lands) for document processing on invoices = around $6,000 per year for typical usage

• Estimated total year-one licensing: around $20,400

Cost drivers not on the licensing invoice:

• Power Platform administrator time for governance, monitoring, and troubleshooting (usually 0.2-0.5 FTE for a deployment this size)

• Citizen developer or Power Platform developer time to build and maintain the flows (varies substantially by workflow complexity)

• Ongoing SharePoint and Dataverse storage growth as workflow data accumulates

• Retraining and change management as Microsoft's licensing packaging shifts (the 2023 rename from Per Flow to Process, the November 2026 AI Builder change)

The fully-loaded TCO for a deployment of this size commonly runs 2-4x the direct licensing invoice, driven by administration and development resource rather than Microsoft's own pricing.

This means that the true cost can be around $80,000.

The same is true of any workflow platform, but Power Automate's licensing complexity tends to require dedicated Power Platform expertise to model and manage.

Where Power Automate's pricing model doesn't fit enterprise workflows

Power Automate is designed for the automation patterns Microsoft's own tooling handles best, event-driven flows between Microsoft 365 apps, RPA against legacy Windows applications, and premium connector integrations to external systems. For those patterns, the pricing is competitive.

The model becomes disproportionately expensive in three specific scenarios.

Workflows shared across many users

• Per-user licensing means every user who submits data into or receives output from a Premium flow needs their own Premium license.

• A single well-designed HR onboarding workflow used across a 200-employee company means 200 Premium licenses at $15 per user per month, before any other costs.

• Process licensing helps once you're above the ~11-user break-even point per flow, but it doesn't fit workflows where users need to build their own automations rather than just interact with shared ones.

Complex multi-step business processes that need forms

• Power Automate handles the workflow part well but doesn't include form-building. Any process that needs proper form UX has to pair Power Automate with Power Apps for the forms and often Dataverse for the underlying data.

• That's three Microsoft products layered together for what could be one platform elsewhere, each with its own licensing, learning curve, and administrative overhead.

AI-heavy workflows post-November 2026

• With seeded AI Builder credits removed from Premium and Process licenses from 1 November 2026, any workflow that uses AI document processing, prediction, or text recognition needs standalone AI Builder capacity or Copilot Credits.

• For enterprise deployments that were counting on AI as an included capability, this shifts a meaningful chunk of AI usage from bundled to line-item billing.

Beyond these three, high-volume enterprise workflows can also breach daily API request limits, requiring additional Power Platform Requests capacity packs at $50 per 10,000 requests per day. This isn't a majority-of-deployments concern, but it does affect the specific processes running at highest volume.

How FlowForma pricing compares

FlowForma uses a fundamentally different pricing model. Rather than layering per-user, per-flow, per-connector, and per-add-on charges, FlowForma prices flat per user for the platform, forms, workflow, document generation, and AI features together. No premium connector surcharges, no per-flow charges for shared processes, and no AI capacity add-ons.

Concretely, that means:

• One line on the licensing invoice rather than three or four separate products
• No premium connector cost, because integration with external systems is included in the platform pricing
• Predictable annual cost, because it doesn't scale with the number of workflows or the AI features they use
• Forms, workflow, document generation, analytics, and AI Copilot included in the same platform, rather than requiring Power Apps, Power Automate, Dataverse, and AI Builder as separate purchases

For enterprise deployments where the Power Automate build stack layers up across multiple products, FlowForma's single-line pricing often works out lower across a three-to-five-year horizon, particularly when the alternative involves Power Automate plus Power Apps plus Dataverse plus AI Builder purchased separately.

Confirmed FlowForma pricing depends on your user count and deployment scope, so it comes from a quote conversation rather than a public list price. Our FlowForma vs Power Automate comparison covers the platform differences in more depth, our best SharePoint integration guide covers the integration angle specifically, and our Microsoft-certified workflow tools guide covers procurement-side considerations.

See a scoped FlowForma quote for your workload

If Power Automate's licensing structure doesn't quite fit your enterprise workflow needs, or the November 2026 AI Builder change is disrupting your budget model, FlowForma's flat per-user pricing may work out cleaner across your specific workload.

Book a demo, and we'll produce a scoped quote alongside the platform walk-through so you can compare like-for-like against your Power Automate model.