Power Apps Per-User vs Per-App Licensing: Which Saves More

The Two Power Apps Licensing Models Explained

Microsoft offers two primary licensing paths for Power Apps: per-user and per-app. The per-user plan grants a single user unlimited access to run any number of apps across unlimited environments. The per-app plan assigns a user access to one specific app (or portal) within a single environment. On paper, the choice seems straightforward. In practice, the total cost depends on how many apps each user actually touches, how your organisation structures its environments, and whether you already have entitlements bundled with your Microsoft 365 E3 or E5 licences.

As of early 2026, per-user pricing sits at approximately $20 per user per month, while per-app licensing runs at roughly $5 per user per app per month. These are list prices; enterprise buyers negotiating through a Microsoft Enterprise Agreement can typically secure discounts of 15 to 30 percent depending on commitment volume and strategic positioning. The critical insight most procurement teams miss is that these discounts are negotiable, and the break-even maths changes significantly when you factor in volume commitments.

Break-Even Analysis: When Per-User Wins

The crossover point between per-user and per-app is simple arithmetic: if a user needs four or more apps, per-user is cheaper. At $5 per app, four apps equals $20, matching the per-user price. Beyond four apps, per-user saves money with every additional app. But the real complexity emerges when you examine your user population segment by segment. Most enterprises have a small cohort of power users (IT, operations, central teams) who run five to ten apps, and a much larger population of occasional users who access one or two apps quarterly.

We have seen organisations waste 40 to 60 percent of their Power Apps budget by putting all users on per-user plans simply because it was administratively simpler. A Microsoft licensing advisory engagement typically starts by mapping actual app usage per user, then segmenting the population to assign the right licence type to each cohort. The savings from this exercise alone often exceed the cost of the advisory.

One Fortune 500 manufacturing client we worked with had 8,000 Power Apps users on per-user plans. After segmentation analysis, only 1,200 genuinely needed unlimited access. Switching the remaining 6,800 to per-app plans (averaging 1.4 apps per user) reduced their annual Power Apps spend by $1.1M. That is not a rounding error; that is a headcount.

Hidden Costs in Per-App Licensing

Per-app licensing introduces operational overhead that many IT teams underestimate. Each per-app licence is tied to a specific environment, which means that if you move an app between environments during a reorganisation or migration, you may need to reassign licences. Microsoft's licence mobility rules for Power Apps are not as flexible as those for Microsoft 365 seat licences, and the administrative burden of tracking per-app assignments across hundreds of apps can absorb significant IT resource time.

Additionally, per-app plans do not include the Dataverse capacity that comes bundled with per-user plans. Per-user plans include 250MB of Dataverse database capacity and 2GB of file capacity per user. Per-app plans include only 50MB of database and 400MB of file capacity per app pass. For data-intensive applications, you may find yourself purchasing additional Dataverse capacity add-ons, which erode the apparent cost advantage of per-app licensing. The Power Platform licensing pillar guide covers Dataverse capacity planning in detail.

The Seeded App Entitlements Most Teams Overlook

Before purchasing any standalone Power Apps plan, verify what your existing Microsoft 365 and Dynamics 365 licences already include. Microsoft 365 E3 and E5 plans include limited Power Apps capabilities for customisation and extension of Microsoft 365 data sources (SharePoint, Teams, Excel). These "seeded" entitlements allow users to run apps that connect exclusively to Microsoft 365 connectors and Dataverse for Teams. If your app connects to a premium connector (SQL Server, SAP, Salesforce, or any custom connector), you need a standalone Power Apps plan.

Dynamics 365 licences include more generous Power Apps entitlements. A Dynamics 365 user can run unlimited canvas and model-driven apps within Dynamics environments without additional Power Apps licensing. We regularly find organisations where 20 to 30 percent of their Power Apps users already have Dynamics 365 licences and are paying for redundant Power Apps seats. This is one of the most common areas of duplicate spend in the Microsoft stack.

Pay-As-You-Go: The Third Option

Microsoft introduced a pay-as-you-go option for Power Apps in late 2023, billed through an Azure subscription at $10 per active user per app per month. There is no upfront commitment, making it ideal for seasonal apps, proof-of-concept deployments, or apps with unpredictable usage patterns. The catch is cost: at $10, it is double the per-app plan price and only makes sense if usage is genuinely sporadic. We advise clients to use pay-as-you-go for apps in their first 90 days of deployment, then switch to per-app or per-user once usage patterns stabilise.

Pay-as-you-go also ties Power Apps billing to your Azure cost governance framework, which can be either a benefit (consolidated FinOps visibility) or a risk (unexpected charges if an app goes viral internally). Set Azure cost alerts at the resource group level to prevent surprises.

Negotiation Tactics for Power Apps Licensing

Power Apps licences are negotiated as part of your broader Microsoft Enterprise Agreement. That means Power Apps pricing is influenced by your total Microsoft spend, your Azure commit-to-consume (MACC) position, and whether you are adding or reducing Dynamics 365 seats in the same renewal cycle. The most effective lever we use in EA discount negotiations is treating Power Apps as a bundled concession: Microsoft is far more willing to discount Power Apps pricing when it is packaged with a larger Azure or M365 commitment.

Another tactic that works consistently: request true-up flexibility. Standard EA terms require annual reconciliation of Power Apps per-user counts. Negotiating quarterly true-down rights (the ability to reduce licence counts mid-year) can save significant money in organisations where Power Apps adoption is still ramping. Microsoft resists this but will grant it when the overall deal value justifies it. The EA true-up guide explains how to structure these terms.

Our Recommendation: The Hybrid Approach

For most enterprises, the optimal strategy is a hybrid: per-user licences for your core power users (typically 15 to 25 percent of your user base), per-app licences for the majority who use one to three apps, and pay-as-you-go for pilot and seasonal applications. This hybrid model requires an initial investment in usage analysis and ongoing licence management, but the savings compound year over year.

The organisations that get this wrong tend to make the same mistake: they choose one model for administrative simplicity and overpay by 30 to 50 percent. The organisations that get it right treat Power Apps licensing as a dynamic allocation problem, reassessing quarterly and adjusting allocations based on actual usage data from the Power Platform admin centre.

If your Power Apps estate has grown beyond 500 users, or if your annual spend exceeds $150,000, a structured licensing review will almost certainly pay for itself. Our Microsoft advisory practice has conducted over 80 Power Platform optimisation engagements, and the median savings rate is 34 percent of prior spend.