Power Platform looks like a per user seat cost, but Dataverse capacity, premium connectors, and AI credits drive the real bill. Govern those at design time and the platform stays predictable.
Microsoft Power Platform licensing is driven by Dataverse capacity, premium connectors, and AI credits that sit outside the seat price. This guide explains the plans, the 2026 cost lines, the overrun traps, and how to keep the platform predictable.
Power Platform pricing looks like a per user seat cost, but the real bill is driven by Dataverse capacity, premium connectors, and AI credits that sit outside the seat price.
Budget on seats alone and the platform overruns. Budget on capacity and connectors and it stays predictable.
Power Platform is licensed through a mix of per user, per app, and pay as you go plans, with capacity and AI consumption billed on top. The seat is the entry point, not the whole cost.
The premium per user plan gives a user full rights across custom apps. The per app plan limits a user to a defined set of apps. Pay as you go bills usage through Azure. Microsoft sets the current structure on the Power Platform pricing page.
Standard connectors are included with Microsoft 365. Premium connectors, custom connectors, and Dataverse require a premium Power Platform license. The split between standard and premium decides whether a workload needs paid licensing at all, and Microsoft lists the classification in the connector reference.
Published pricing is per user per month for the seat plans, with Dataverse capacity and AI credits priced separately. Microsoft documents the SKUs and billing in its licensing and billing reference.
Copilot Studio and generative actions consume message and AI credits that bill outside the seat plan. A heavily used agent can cost more in credits than the seats behind it, so model the consumption before rollout.
Illustrative Power Platform plan structure (confirm live rates before any quote)
| Plan | Scope | Billing note | Buyer side move |
|---|---|---|---|
| Premium per user | All custom apps and flows | Per user per month | Use for makers and heavy users |
| Per app | Defined apps only | Per user per app | Use for single workload users |
| Pay as you go | Usage based | Billed via Azure | Use for spiky or pilot use |
| Dataverse capacity | Storage and API | Per gigabyte above allowance | Monitor before it overruns |
The overruns come from the parts that are not the seat. Premium connectors quietly pulling apps into paid licensing, Dataverse capacity creeping above allowance, and AI credits with no cap.
An app built on a standard connector is free to Microsoft 365 users. Add one premium connector and every user of that app now needs a premium license. A single connector choice can change the licensing cost of a whole workload.
Dataverse storage grows quietly as apps log data. Once it passes the included allowance, the per gigabyte charge starts, and it rarely appears in the original business case.
The standard message is that Power Platform is effectively free because Microsoft 365 already includes Power Apps and Power Automate. We disagree. In the Power Platform estates we have reviewed, the included standard tier covered a minority of real workloads, and the moment a premium connector, Dataverse, or a custom connector entered the design, the per user cost jumped to a full premium license. The buyer side move is to govern connector and Dataverse use at design time, not after the invoice, so the team chooses the licensing consequence deliberately rather than discovering it at renewal.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Power Platform is only free until the first premium connector. After that, the connector, not the seat, sets the price of the whole workload.
Control comes from governance, not from buying fewer seats. You decide connector and capacity policy at design time, then match each user to the cheapest plan that fits.
Set data loss prevention policies that classify connectors and control where premium connectors are allowed. This makes the licensing consequence of every app a deliberate choice, not an accident. Microsoft documents the controls in its data loss prevention guidance.
Power Platform is licensed through per user, per app, and pay as you go plans, with Dataverse capacity and AI credits billed on top. The seat is the entry point, but capacity and connectors drive the real cost, so budget on all of them.
Standard connectors are included with Microsoft 365, while premium, custom, and on premises connectors require a premium Power Platform license. The connector choice decides whether a workload needs paid licensing at all, so it is a licensing decision, not just a technical one.
Yes. Adding a single premium connector to an app means every user of that app needs a premium license. One connector choice can convert a free Microsoft 365 app into a fully licensed Power Platform workload, which is why governance at design time matters.
Dataverse provides an included storage allowance, then bills per gigabyte above it for database, file, and log capacity. The charge rarely appears in the original business case, so monitor capacity monthly because it creeps up quietly as apps log data.
Copilot Studio and generative actions consume message and AI credits that bill outside the seat plan. A heavily used agent can cost more in credits than the seats behind it, so model the expected consumption before you roll an agent out.
Use a per app plan for users who only need a defined set of apps, because it is cheaper than the premium per user plan for narrow use. In our reviews, 25 to 40 percent of premium seats fit a per app plan once real usage was mapped.
Only partly. Microsoft 365 includes Power Apps and Power Automate on standard connectors, but the included tier covers a minority of real workloads. The moment premium connectors, Dataverse, or custom connectors enter the design, full premium licensing applies.
Control comes from governance, not from buying fewer seats. Set data loss prevention policies on connectors, monitor Dataverse capacity, model AI credits, and match each user to the cheapest plan that fits, deciding the licensing consequence at design time.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
