Power Apps prices on two plans and a layer of capacity that buyers consistently misread. The per app plan licenses a single application for a single user. The per user plan licenses an individual to run unlimited applications. Underneath both sits the seeded entitlement that ships inside many M365 subscriptions, which covers apps built only on the standard connectors and the standard data layer. The moment an app reaches a premium connector, the Dataverse data layer, or a custom connector, the seeded rights stop applying and a paid Power Apps license is required for every user of that app. Organizations discover this only when an audit or a renewal forces a reconciliation, because the platform lets the apps run long before the licensing catches up. Power Apps is where citizen development quietly outruns the entitlement that was supposed to cover it.
Power Apps licenses through two paid plans, a seeded entitlement inside M365, and a Dataverse capacity layer. The line that governs the bill is the boundary between standard and premium capability, because crossing it converts a seeded app into one that requires a paid license per user.
The two paid plans serve different adoption shapes. The per app plan covers one user running one application and suits the targeted rollout. The per user plan covers one user running any number of applications and suits the heavy maker or the user surrounded by many internal apps.
Many M365 subscriptions seed the right to build and run Power Apps on standard connectors only. Premium connectors, custom connectors, and the Dataverse data layer fall outside the seeded rights and require a paid plan for every user of the app. Dataverse also carries its own capacity that bills separately at scale.
Power Apps produces three recurring exposures. The first is assuming the seeded M365 rights cover apps that have crossed into premium territory. The second is choosing the wrong plan for the adoption shape. The third is letting Dataverse capacity overflow the included pool without anyone watching the meter.
An app starts on standard connectors and grows a premium connector over time. The platform keeps it running, but the seeded M365 rights no longer cover it. Every user of that app now needs a paid plan that nobody bought. The shortfall sits invisible until an audit maps the connectors against the licenses and surfaces the gap.
A user surrounded by many internal apps is cheaper on the per user plan, while a user with one targeted tool is cheaper per app. Organizations standardize on one plan for simplicity and overpay the population that fits the other. The mix is rarely modeled against the real app to user mapping that the platform already records.
Dataverse database and file capacity comes with an included pool that grows with paid licenses. As apps accumulate data, the pool overflows and the overage bills separately. Without a steward watching the meter, the capacity charge climbs unnoticed and becomes a recurring line that the original app business cases never accounted for.
The Power Apps bill responds to three levers. The connector audit establishes which apps truly need a paid license and which sit safely inside the seeded rights. The plan optimization places each user on the cheaper of the two plans. The Dataverse governance keeps capacity inside the included pool.
Every app in the tenant is inventoried against the connectors it uses. Apps on standard connectors stay on the seeded rights at no incremental cost. Apps that have crossed into premium territory are flagged, and the choice becomes whether to license the users or to refactor the app back onto standard connectors where the business case allows.
The clean connector map then anchors the EA renewal so the Power Platform line reflects the apps that genuinely require paid plans.
We map every paid user against the number of apps they run and place each on the cheaper of the per app and per user plans. The heavy makers move to per user, the single app users stay per app, and the blended rate drops.
Dataverse capacity is then governed against the included pool, with cleanup of orphaned tables and oversized environments so the storage stays inside the entitlement rather than spilling into overage.
Power Apps negotiates inside the Power Platform envelope of the broader Microsoft agreement. Microsoft treats the platform as a strategic growth bet, which gives a buyer expanding adoption real leverage on the plan rates and the capacity terms.
Power Platform carries adoption targets that Microsoft account teams are measured against. A buyer scaling Power Apps holds leverage to negotiate the per app and per user rates, the Dataverse capacity pricing, and multi year protection on both. The expansion is the concession currency. Committing to the platform without a structured ask leaves discount on the table that the account team was prepared to give to drive the adoption number.
An unreconciled estate where premium apps run on seeded rights is a liability the buyer carries into the negotiation. Microsoft can surface the shortfall and price the remediation at list. A buyer who runs the connector audit first, clears the exposure on its own terms, and arrives with a clean baseline negotiates the expansion from strength rather than defending a compliance gap the vendor controls.
The Power Apps engagement is a connector and app inventory, a plan and capacity optimization, and the integration of the clean baseline into the Power Platform negotiation. The output is a platform priced at the apps that genuinely require paid plans, with the exposure cleared on the buyer's terms.
We inventory every Power Apps application in the tenant, map each against the connectors and the data layer it uses, and separate the apps covered by seeded M365 rights from the apps that require paid plans. We quantify the licensing gap and identify which premium apps justify a license and which can be refactored back to standard connectors. The output is a defensible picture of what the platform actually requires.
We place every paid user on the cheaper plan, govern Dataverse capacity inside the included pool, clear the seeded overreach before it becomes an audit finding, and fold the clean baseline into the Power Platform negotiation. We negotiate the plan rates against Microsoft's adoption posture and lock multi year protection. The output is a Power Apps position priced at real use and defensible through the term.
The Power Apps diagnostic inventories every app against its connectors, separates seeded rights from paid requirements, places each user on the cheaper plan, governs Dataverse capacity, and brings the clean baseline into the Power Platform negotiation. The result is a platform line priced at the apps that genuinely need a license, with the exposure cleared on your terms.