Microsoft Licensing
Power Apps per app plan, priced right.
Tie cost to the apps people actually run. Here is how the per app plan compares to per user, and when each one wins.
Tie cost to the apps people actually run. Here is how the per app plan compares to per user, and when each one wins.
The Power Apps per app plan ties cost to a single app per user, which beats the per user plan whenever most of your people run one or two workflows rather than a full portfolio.
This guide is for platform owners and procurement leads sizing a Power Apps rollout. Read it with the Microsoft licensing guide and the Microsoft Practice page before you commit seat counts.
The per app plan grants a user the right to run one app, or a defined small set, against premium connectors and Dataverse. It is metered per user per app per month.
One app can be a canvas app, a model driven app, or a portal, with the premium connectors that app needs. The license follows the user assigned to that app, not the whole platform.
The decision turns on apps per user. Below the break even, per app is cheaper. Above it, the per user plan pays back through unlimited access.
Per app vs per user decision grid
| Apps per user | Better plan | Why |
|---|---|---|
| 1 app | Per app | Lowest cost per seat |
| 2 apps | Per app, usually | Two per app fees often beat per user |
| 3+ apps | Per user | Unlimited access pays back |
Microsoft has changed entry minimums over the years, so confirm the current floor before sizing. The official terms sit on the Power Apps pricing page.
Build a simple map of users to apps, then license against it. The default mistake is putting everyone on the per user plan for convenience.
The per app plan licenses a single user to run one app, or a small set, rather than the full Power Platform. It is priced per user per app per month and suits targeted rollouts where users need one workflow, not a portfolio.
The per user plan gives one user unlimited apps for a higher monthly fee. The per app plan is cheaper per seat but only covers a defined app. Break even depends on how many apps each user really needs.
Choose per app when most users touch one or two apps. It keeps cost tied to actual use. Once a user needs three or more apps, the per user plan usually wins on total cost.
Microsoft has adjusted entry minimums over time, so confirm the current floor before you size a deal. Historically the per app plan had a low entry point that made small pilots affordable.
Yes. Both the per app and per user plans unlock premium connectors, Dataverse, and custom connectors that the seeded Microsoft 365 Power Apps use rights do not include.
Map each user to the apps they actually open, then license to that. Estates that default everyone to the per user plan routinely overpay when most users only run a single workflow.
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.
Most Power Apps overspend comes from licensing a portfolio to users who only ever open one workflow.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
SKU changes, price moves, and renewal levers for buyers. No vendor spin.
