Power Automate Pricing for Small Business (2026): Premium, Process, RPA, and Real Monthly Cost

Power Automate costs $15 per user per month for Premium, $150 per bot per month for Process, or $215 per bot per month for Hosted Process at Microsoft’s current US list prices, paid yearly. A small Microsoft 365 office may pay no additional license fee for simple cloud flows that stay within its seeded rights and use standard connectors. Premium connectors, custom connectors, attended desktop automation, unattended bots, Dataverse capacity, AI usage, and higher request capacity can change that answer quickly.

For most small businesses, the practical starting point is either $0 incremental for basic Microsoft 365 approvals or $15 per maker/user monthly for Premium. Buy Process when one business-critical cloud process serves many users or when one unattended desktop bot is required. Buy Hosted Process when that unattended bot also needs a Microsoft-hosted virtual machine. Prices below were verified against Microsoft’s US pricing and licensing documentation on August 23, 2026; tax, region, currency, contract, reseller, partner, and underlying software licenses may differ.

Power Automate can be licensed around a user, a shared process, or a hosted unattended bot. Editorial illustration, not a product screenshot.

Power Automate pricing at a glance

The right plan depends on who runs the automation and whether it needs to operate without a person signed in.

These are public list prices, not quotes. Microsoft’s page says prices are informational and may not include tax. Canadian, UK, EU, nonprofit, education, enterprise-agreement, CSP, and partner pricing can differ. Annual commitment also matters: “$15 per month” is a monthly equivalent of yearly billing, not necessarily a cancel-any-month offer.

Start with the workflow’s connectors and run mode, then choose the licensing unit. Editorial illustration, not a Microsoft decision tool.

What do Microsoft 365 seeded rights include?

Qualifying Microsoft 365 licenses can cover basic Power Automate work tied to Microsoft 365 services and standard connectors, but they are not a free substitute for Power Automate Premium. A typical seeded-rights workflow might start from SharePoint, Microsoft Lists, Outlook, Teams, Forms, or OneDrive, route an approval, send notifications, and update another included Microsoft 365 service.

That can make the incremental software cost $0 for a simple internal approval flow when every participant already has the appropriate Microsoft 365 license and the flow stays within included use rights. It does not mean Power Automate is unlimited or that every connector visible in the designer is licensed.

The standalone-license line is normally crossed when a flow needs:

• a premium connector such as SQL Server or many Azure and Dynamics connectors;
• a custom connector or direct custom API integration;
• an on-premises data gateway;
• standalone Dataverse use beyond limited Microsoft 365 or Dataverse for Teams rights;
• desktop flows/RPA beyond the applicable included rights;
• capacity or governance that the seeded license does not provide.

Connector classification can change, and licensing follows the actual workflow rather than the fact that it was built inside Teams. Check every production connector in Microsoft’s connector reference and confirm the assigned licenses before rollout.

What does Power Automate Premium include?

Power Automate Premium is the simplest choice when a named employee builds or runs several premium cloud flows or needs attended desktop automation. At $15 per user per month, five licensed operations staff cost $75 per month or $900 per year at the published annual rate.

Microsoft describes Premium as including cloud flows, attended desktop flows, process mining desktop functionality, 50 MB of process-mining storage per license, and Dataverse entitlements of 250 MB database plus 2 GB file capacity. The license also carries a published Power Platform Request entitlement of 40,000 requests per user per 24 hours.

“Per user” is the part buyers routinely underestimate. A single Premium license does not automatically cover every colleague who triggers, invokes, or receives the benefit of a premium flow. Licensing depends on flow type, ownership, trigger, process assignment, and the identities using premium capabilities. For a broadly used process, compare the cost and administrative clarity of licensing the process itself rather than scattering user licenses and hoping the audit fairy is feeling charitable.

Attended desktop automation also has a hard operational boundary: the licensed user initiates or supervises the run on a machine. If the desktop flow must run after hours with nobody present, that is unattended RPA and needs bot/process capacity.

How do Process and Hosted Process licensing work?

Process licenses the automation; Hosted Process licenses the automation plus a Microsoft-hosted virtual machine. Both are $150 or $215 per bot per month respectively at current US list prices, paid yearly.

A Process license can be assigned to one cloud flow as a business process used by unlimited users within the organization, or it can provide capacity for one unattended RPA bot. Microsoft publishes 250,000 Power Platform Requests per 24 hours for a Process-licensed cloud flow, including its child and associated flows.

Hosted Process adds a Microsoft-managed hosted machine for the unattended desktop bot. The $65 monthly list-price difference can be reasonable when the alternative is provisioning, securing, patching, monitoring, and recovering a compatible VM yourself. It does not remove the need to configure the desktop app, credentials, selectors, error handling, or business continuity.

One bot is one unit of unattended capacity. If two desktop runs must execute simultaneously, plan for two bot licenses and, where relevant, two machines or sessions. Queueing work behind one bot may be fine for overnight back-office jobs; it is not fine when a customer-facing process needs parallel response.

Microsoft also warns that software automated by an unattended bot can require separate licensing. Automating Microsoft 365 or Office 365 in unattended scenarios may require the Microsoft 365 Unattended License. Windows, ERP, accounting, database, remote-desktop, or line-of-business application terms can add further cost. Power Automate licensing does not magically renegotiate another vendor’s contract.

Attended versus unattended RPA

Attended RPA assists a signed-in person; unattended RPA runs independently under bot capacity.

Desktop automation is often justified when no usable API exists. It is also more brittle than API automation because window titles, screen layouts, timing, pop-ups, MFA, and application updates can break a run. Budget for exception handling and ownership, not just the bot sticker price.

Premium connectors, custom connectors, and Dataverse costs

The first premium connector can matter more than the number of flow steps because it can move the entire scenario into standalone licensing. SQL Server, many Azure services, Dynamics products, custom connectors, and on-premises gateway access are common triggers for Premium evaluation.

Dataverse deserves separate attention. Premium includes limited accrued database and file capacity, while Process and Hosted Process each include smaller entitlements of 50 MB database and 200 MB file capacity. Storage is pooled and managed at the tenant/environment level under Microsoft’s capacity rules; it is not a promise that every flow gets a private bucket.

Microsoft’s licensing FAQ currently lists Dataverse add-ons at $40 per GB per month for database capacity, with file and log capacity sold separately. Exact add-on availability and price should be confirmed in your tenant or quote. A workflow that stores attachments, execution records, documents, or process-mining data can turn storage into a real line item.

Before buying, identify:

• every connector and whether Microsoft classifies it as standard, premium, or custom;
• whether a gateway is required;
• whether Dataverse is necessary or SharePoint/another existing data store is sufficient;
• expected database, file, log, and process-mining growth;
• development, test, and production environment requirements;
• data-loss prevention, managed environments, and admin ownership.

AI Builder, Copilot, and Copilot Studio are separate boundaries

Copilot assistance inside Power Automate, AI Builder model capacity, and Copilot Studio agents are related products—not one unlimited AI entitlement.

Copilot in Power Automate can help a maker describe or edit a flow, subject to tenant, region, product, and licensing availability. It does not make premium connectors free, remove request limits, or pay the license for everyone who uses the resulting automation.

AI Builder runs prebuilt or custom models for tasks such as document extraction, prediction, and OCR. Microsoft says AI Builder consumes AI Builder credits or Copilot Credits depending on context, with consumption varying by model and workload. Premium currently includes 5,000 AI Builder credits per user, but Microsoft’s licensing FAQ states that this grant will be removed on November 1, 2026. Treat it as transitional capacity, not a durable reason to size a 2027 deployment.

Copilot Studio is separately packaged for building and operating agents. Microsoft’s public page currently shows $200 per month for 25,000 Copilot Credits, paid yearly. Copilot Studio includes Power Automate use rights only for flows used in the context of the agent; it is not a tenant-wide Power Automate Premium license. Connected AI models, Azure services, APIs, or third-party tools may also bill separately.

How Power Platform request limits affect cost

Power Automate subscriptions include daily request entitlements, not unlimited API activity. Requests can include connector actions, built-in actions, retries, and pagination; one visible flow run can therefore consume many requests.

Microsoft currently documents these official limits per 24 hours:

• Power Automate Premium: 40,000 per licensed user;
• Power Automate Process: 250,000 per assigned license;
• Power Automate Hosted Process: 250,000 per assigned license;
• Microsoft 365/Office 365 seeded rights: 6,000 per user.

Desktop flow executions do not consume Power Platform Requests, but cloud orchestration around them can. Microsoft also documents higher temporary transition-period limits and says enforcement changes as reporting matures. Do not size a new system around a temporary ceiling. Monitor the Power Platform admin center, include retries and seasonal peaks, and obtain written guidance if the process approaches official entitlements. Capacity add-ons and pay-as-you-go may be options, but their commercial fit should be quoted for the tenant.

Real monthly cost scenarios for small businesses

The subscription calculation is simple; the licensing unit and operating assumptions are where mistakes happen. These examples use US list prices paid yearly, exclude tax, and assume existing Microsoft 365 subscriptions are already budgeted.

The approval example is not “free automation.” Someone still has to design, test, document, monitor, and repair the flow. At a planning rate of $75 per hour, four setup hours plus one hour of monthly care makes the first month $375 and later months $75 even when the incremental license is zero.

For the unattended example, assume a modest self-managed VM and operations allowance of $50 to $150 monthly plus two hours of administrator time at $75 per hour. The realistic Process TCO becomes roughly $350 to $450 per month before the automated application’s licensing. Hosted Process at $215 can reduce infrastructure work, but it does not eliminate bot support; with one hour of monthly care, a planning estimate is roughly $290 per month plus application licenses.

Hidden-cost checklist

A reliable estimate includes the work around the flow, not only Microsoft’s invoice.

An unattended bot still depends on infrastructure, software rights, credentials, monitoring, maintenance, and capacity planning.

• Annual commitment, tax, currency, reseller, partner, and contract pricing
• Premium or custom connector licensing for every affected user or process
• On-premises gateway hosting, patching, monitoring, and redundancy
• Dataverse database, file, log, and process-mining capacity
• AI Builder or Copilot Credit consumption after included/transitional capacity
• Copilot Studio licensing when an agent is part of the design
• Power Platform Request capacity and peak-volume headroom
• Development, test, and production environments
• Managed environment, security, DLP, audit, and admin work
• Desktop bot VM, Windows, Microsoft 365 Unattended, and target-application rights
• Parallel unattended runs, which require additional bot capacity
• Service accounts, MFA design, secret rotation, and credential vaulting
• Workflow design, testing, documentation, training, and change control
• Monitoring, failed-run triage, UI-change repairs, and vendor API changes
• Partner implementation or ongoing managed-service fees

Which Power Automate plan should a small business choose?

Use seeded Microsoft 365 rights for simple internal productivity flows, Premium for named makers and attended automation, Process for shared or unattended automation, and Hosted Process when Microsoft should supply the bot VM.

• Stay with seeded rights when flows remain inside Microsoft 365 services, use standard connectors, and do not require standalone Dataverse, gateway, custom API, or desktop automation capabilities.
• Buy Premium when one or more named users need premium/custom connectors, attended RPA, or broad individual automation rights. At five users, the public baseline is $75 monthly.
• Buy Process when one important cloud process benefits many users or one unattended desktop bot runs on infrastructure you manage. Validate the assignment rules and every underlying software license.
• Buy Hosted Process when unattended RPA is required and a Microsoft-hosted machine is worth $65 more per month than Process at list price.
• Consider Zapier or Make first when the team is nontechnical, the stack is mainly common SaaS products, there is no desktop automation, and straightforward builder experience matters more than Microsoft ecosystem depth. Compare live task/credit allowances, not just starting prices.

Run a proof of concept with two representative workflows, record connectors, identities, daily requests, exception rates, run frequency, and support time, then have the reseller or Microsoft account team confirm licensing in writing. A plan card is not an architecture review.

Frequently asked questions

Is Power Automate free with Microsoft 365?

Qualifying Microsoft 365 plans include limited Power Automate rights for Microsoft 365 productivity scenarios and standard connectors. Premium, custom, gateway, standalone Dataverse, and RPA scenarios can require separate licensing.

Does every user need Power Automate Premium?

Not always. It depends on the flow type, trigger, connectors, ownership, and who receives the premium capability. Premium is per named user; Process can license one shared business process for organization-wide users. Confirm the design before rollout.

Is Power Automate Process priced per flow or per bot?

Microsoft currently presents Process at $150 per bot per month. It can license one unattended automation bot or one business-critical process. Parallel unattended capacity requires additional licenses.

What is the difference between Process and Hosted Process?

Process supplies process or unattended-bot capacity. Hosted Process adds a Microsoft-hosted virtual machine and costs $215 per bot per month versus $150 for Process at current US list prices.

Are premium connectors included with Microsoft 365?

Generally no. Microsoft 365 seeded rights focus on standard connectors and Microsoft 365 scenarios. A standalone Power Automate or Power Apps license is generally required for premium, custom, and on-premises gateway use.

Does Premium include unattended RPA?

No. Premium includes attended desktop flows for the licensed user. Unattended desktop automation requires Process or Hosted Process capacity, plus any required underlying software licenses.

Are AI Builder and Copilot included without limits?

No. AI Builder and Copilot features have separate capacity, product, regional, and licensing boundaries. Microsoft says the 5,000 AI Builder credits currently included per Premium user will be removed November 1, 2026.

Are these the prices a Canadian or contracted customer will pay?

Not necessarily. The figures are US public list prices shown as monthly equivalents paid yearly. Region, currency, taxes, contract, nonprofit status, reseller, partner, and negotiated terms can change the actual invoice.

Sources and verification

This guide is an editorial synthesis verified against Microsoft’s public pricing and licensing documentation on August 23, 2026. It is not hands-on product testing, legal advice, or a Microsoft licensing quote. Google Search Console and GA4 evidence was unavailable, so no first-party traffic or performance claims were used.

• Microsoft Power Automate pricing
• Microsoft Power Platform licensing FAQ
• Microsoft Power Platform request limits and allocations
• Microsoft Power Automate licensing overview
• Microsoft Power Platform connectors