Microsoft / Power Platform
Power Platform licensing. Priced per app, paid per estate.
Power Platform looks cheap on the seat price and bills you on connectors and capacity. The plan mix and the governance you set first decide the real cost.
Power Platform looks cheap on the seat price and bills you on connectors and capacity. The plan mix and the governance you set first decide the real cost.
Power Platform pricing splits into per app, per user, and pay as you go, and the seat price is the smallest part of the bill. This guide maps the connector and capacity traps and the levers that hold the spend down.
Power Platform pricing looks simple on the page and behaves nothing like it in production. The seat price is the smallest number in the model.
The real cost sits in premium connectors, Dataverse capacity, and the slow drift from seeded entitlements into paid plans. This guide maps where the money goes and how to hold it down.
Power Platform licenses split into per app, per user, and pay as you go models, each metered differently. Microsoft publishes the current plans on its Power Apps pricing page and in the licensing and billing reference.
A per app plan licenses one user to run a defined set of apps. A per user plan licenses one person to run unlimited apps. The break point usually sits around three apps per person.
Pay as you go bills app usage to an Azure subscription by active user per app per month. It removes upfront seat commitments. It also removes the budget ceiling, so it needs a metering alert. The pay as you go documentation sets out the meters.
Compare the per app plan, the per user plan, and pay as you go against your real maker and runner counts. The wrong default here scales across thousands of seats.
Power Platform plan comparison for a 2026 buyer
| Plan | Meter | Best fit | Watch out for |
|---|---|---|---|
| Per app | User per app set | Wide audience, few apps | Counts climb as app count grows |
| Per user | Named user | Makers and power users | Dormant seats after a project ends |
| Pay as you go | Active user per app | Spiky or pilot usage | No budget ceiling without alerts |
| Seeded in M365 | Included rights | Standard connector apps | Breaks the moment a premium connector is added |
Automation and agents carry their own meters. Power Automate splits into per user and per flow plans, and Copilot Studio bills message capacity packs. Review the Power Automate pricing before you assume the M365 seed covers a flow.
Most overruns are not list price. They are metered extras that a maker triggers without a purchase order. Three areas account for the bulk of the drift.
The moment an app touches a premium or custom connector, the seeded M365 rights stop applying. Every runner of that app now needs a paid plan. One connector can convert a free app into a four figure monthly line.
The standard partner pitch is that Power Platform is nearly free because Microsoft 365 already seeds it, so you should roll it out wide and license later. We disagree. In most estates we reviewed, the seeded rights covered standard connectors only, and the first premium connector silently moved hundreds of runners onto paid plans nobody had budgeted. The buyer side move is to govern connectors and Dataverse capacity from day one, treat every premium connector as a purchasing decision, and license against measured active usage rather than optimistic adoption forecasts. Govern first, then scale.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Power Platform is not expensive because of its seat price. It is expensive because nobody owns the connector and capacity decisions until the invoice arrives.
Start with measured usage, not the org chart. The Power Platform admin center shows who actually runs each app, and that data sets the plan mix.
Set a managed environment policy and a connector allow list before the next purchase. Microsoft documents the controls in its managed environments guidance, and they pay for themselves the first time they block an unbudgeted premium connector.
Power Platform is licensed through per app plans, per user plans, and pay as you go billing to Azure. Per app covers a defined app set for one user, per user covers unlimited apps for one person, and pay as you go meters active use. Microsoft 365 also seeds limited rights for standard connectors only.
A per app plan licenses one user to run one defined set of apps, while a per user plan licenses one person to run unlimited apps. Per app suits narrow apps with a wide audience, and per user suits makers and power users who run many apps each.
Yes. Premium and custom connectors fall outside the seeded Microsoft 365 rights, so every user who runs an app touching one needs a paid Power Apps or Power Automate plan. A single premium connector can convert a free app into a paid one across its whole audience.
Dataverse capacity is the database, file, and log storage Power Platform apps consume. Each tenant gets a base entitlement plus a small allowance per paid seat, and usage above that pools is billed per gigabyte. Storage overages are a common and overlooked source of cost growth.
No. Microsoft 365 seeds limited Power Apps and Power Automate rights restricted to standard connectors and inside the context of Microsoft 365 apps. The moment an app uses a premium connector, custom connector, or Dataverse, it requires a paid Power Platform license.
Pay as you go bills app usage to an Azure subscription by active user per app per month, with no upfront seat purchase. It is useful for pilots and spiky usage, but it has no budget ceiling, so it needs metering alerts to avoid an unplanned Azure invoice.
Start with active usage data from the Power Platform admin center, match each runner to the cheapest plan that covers their apps, reclaim dormant per user seats, and pool Dataverse capacity before buying packs. Governance on connectors and environments prevents the next overrun.
Managed environments, a connector allow list, and data loss prevention policies are the main controls. They let an administrator block unbudgeted premium connectors and restrict where apps can run, which turns connector adoption back into a purchasing decision rather than a surprise.
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.
