With the Per App Plan Gone, What Should Microsoft Power Apps Consulting Optimize?

A healthcare services company built a portfolio of Power Apps over four years: a field inspection app, a supply request app, an incident reporting app, a visitor log, and several department tools. It licensed most users through per app passes, because each person typically used one or two apps. When its MPSA agreement approaches renewal in 2026, the company learns that per app licenses will no longer be available through that channel. Its partner proposes building three new apps for the next phase, but nobody has calculated what the combined portfolio will cost under Premium or pay-as-you-go. Depending on the answer, the new apps could double the licensing bill or barely change it.

This decision is now common. With the per app plan leaving most new purchases, organizations must choose between per-user Premium licensing and consumption-based pay-as-you-go. The cheaper option depends on how many apps each user runs and how often. That means app design choices, such as whether to combine functions into one app or split them across several, now directly set licensing cost. Microsoft Power Apps consulting should start with portfolio and usage analysis, not just requirements.

What Changed With the Per App Plan

Microsoft's licensing update on Power Apps states that, effective January 2, 2026, the Power Apps per app SKU is no longer available for purchase by new customers. The impact differs by channel:

a. Enterprise Agreement customers already using the license can continue using and renewing it.

b. MPSA customers keep access until their agreement ends, then have a 60-day window to move to an alternative.

c. CSP customers can continue purchasing and renewing the per app subscription.

For new customers, and for existing customers in affected channels, the practical choices are Power Apps Premium or the pay-as-you-go per-app meter.

The Two Remaining Models

Power Apps Premium

Microsoft's Power Apps pricing lists Premium at $20 per user per month, paid yearly, with a volume price of $12 per user per month for organizations buying at least 2,000 licenses. Premium users can run unlimited apps and Power Pages sites, and include Dataverse capacity entitlements.

Pay-As-You-Go Per-App Meter

Microsoft's pay-as-you-go meters documentation describes the Power Apps per-app meter at $10 per active user, per app, per month, billed to an Azure subscription. An active user is someone who opens an app at least once in the month. Repeat use of the same app does not add cost, but a user who opens three apps counts three times. Users with Power Apps per-user licenses are not counted.

The Break-Even Math

The comparison is simple for a single user. Under pay-as-you-go, a user who opens one app in a month costs $10. A user who opens two apps costs $20, the same as Premium at list price. A user who opens three or more apps costs more than Premium.

Monthly patterns matter too. A user who opens an app only in some months costs nothing under pay-as-you-go in months without use, while Premium is paid every month. Seasonal apps, occasional-use tools, and apps for contractors or temporary staff often favor pay-as-you-go.

Organizations can mix models. Heavy users across many apps can receive Premium licenses, while occasional users of single apps are covered by pay-as-you-go. Users with Premium are excluded from the meter, so the two models work together.

Why Architecture Now Sets the Bill

Because pay-as-you-go counts each app separately, the way a solution is divided into apps directly affects cost:

i. Splitting one process into several apps can multiply pay-as-you-go charges for users who need all of them.

ii. Combining related functions into one app can reduce per-app charges, though it may make the app larger and harder to maintain.

iii. Adding a new app for a user group already on Premium adds no license cost.

iv. Adding a new app for a large occasional-user group on pay-as-you-go adds $10 per active user per month.

Model-driven apps, canvas apps, and embedded experiences also differ in how users access them. A consultant who designs without considering licensing can create an architecture that costs far more to run than an equally good alternative.

Portfolio Analysis in Microsoft Power Apps Consulting Services

Before designing new apps, Microsoft Power Apps consulting services should analyze the current state:

a. App inventory: every production app, its purpose, owner, and environment.

b. User inventory: who uses each app and how often, using Power Platform admin center analytics.

c. Usage patterns: apps per user, monthly active users, seasonality, and inactive apps.

d. Current licensing: per app passes, Premium licenses, Microsoft 365 entitlements, and Dynamics 365 licenses.

e. Cost modeling: total cost under Premium, pay-as-you-go, and mixed approaches.

f. Roadmap impact: how planned apps change the model.

This analysis often reveals savings immediately, such as retiring unused apps or moving heavy users to Premium.

Design Choices That Control Cost

Once the portfolio is understood, consultants can guide design:

i. Consolidate related functions where users need several of them together.

ii. Keep occasional-use apps separate where different user groups use them.

iii. Target Premium licensing for power users and makers.

iv. Use pay-as-you-go for broad, light, or seasonal usage.

v. Consider standard connectors where possible, since users with Microsoft 365 licenses running apps with only standard connectors are not counted in the meter.

vi. Retire unused apps that still carry license or meter cost.

These choices should be documented in the solution design with their licensing impact.

Dynamics 365 and Microsoft 365 Entitlements

Many users already hold licenses that include some Power Apps rights. Microsoft 365 plans allow users to run apps built on standard connectors within the context of Microsoft 365. Dynamics 365 licenses include rights to use custom apps that extend the Dynamics 365 application within the same environment. Users covered by these entitlements may not need Premium or pay-as-you-go at all for certain apps.

These entitlements have limits. An app that uses premium connectors, such as SQL Server, custom connectors, or Dataverse outside a Dynamics 365 context, usually requires Premium or the pay-as-you-go meter. Moving a single data source from SharePoint to Dataverse, or adding one premium connector, can change the license requirement for every user of an app. Good design decisions weigh the technical benefits of a premium data source against the licensing impact across the user base.

A licensing review should map each app to the entitlements its users already have. Microsoft Power Apps consulting services that skip this step risk recommending Premium licenses for users who are already covered, or building apps that unexpectedly push covered users into paid licensing.

Planning the Transition From Per App Licenses

Organizations losing per app licenses at renewal need a transition plan. The plan should identify the renewal or agreement end date, the users and apps currently covered by per app passes, the target model for each group, and the timing for linking environments to pay-as-you-go or assigning Premium licenses.

Testing the new model before the deadline avoids surprises. Enabling pay-as-you-go in a single environment for a month, with real usage, shows the actual bill and confirms that users are counted as expected. Communicating changes to app owners and users matters too, especially if some apps will be consolidated or retired as part of the move.

Finance teams also need visibility. Pay-as-you-go charges appear on the Azure invoice rather than the Microsoft 365 or Power Platform license bill, so budget owners should know where to look and how to allocate costs to departments.

Environment Strategy Matters

The pay-as-you-go meter applies to environments linked to an Azure subscription. Environment design therefore affects cost:

a. Grouping apps by licensing model into pay-as-you-go and prepaid environments.

b. Separating production from development so test usage does not create charges.

c. Monitoring meter usage through Azure Cost Management and Power Platform reports.

Microsoft notes that when an environment is enabled for pay-as-you-go, any app passes assigned to it are ignored. Planning the transition carefully avoids paying twice.

Governance for Ongoing Cost Control

Licensing cost changes as apps and usage grow. Governance should include:

i. Monthly cost reviews by environment and app.

ii. Approval rules for new apps that consider licensing impact.

iii. License assignment reviews to move heavy pay-as-you-go users to Premium.

iv. App retirement processes for unused apps.

Chargeback or showback so departments understand their costs.

Questions for Power Apps Consulting Services Partners

When evaluating power apps consulting services, organizations can ask:

a. Will the partner analyze the app portfolio and usage before designing new apps?

b. How will it compare Premium, pay-as-you-go, and mixed licensing models?

c. How does the proposed architecture affect licensing cost?

d. What environment strategy does it recommend for pay-as-you-go?

e. How will ongoing costs be monitored?

f. What is the plan for users losing per app licenses at renewal?

A partner that treats licensing as someone else's problem may deliver apps that work well but cost more than necessary.

A Representative Outcome

Return to the healthcare services company. Its consulting partner analyzes usage and finds that about 15% of users run three or more apps each month, while most use a single app occasionally. Several older apps have had no users in six months. The partner recommends Premium licenses for the heavy users, pay-as-you-go for everyone else, and retirement of unused apps. For the next phase, two of the three planned apps are combined into one because the same field staff use both functions.

The projected licensing cost after the MPSA agreement ends comes in below the previous per app spend, and the new apps launch with a clear cost model.

With the per app plan no longer available for most new purchases, Microsoft Power Apps consulting needs to address licensing and app design together. Reviewing usage first helps organizations choose the right mix of Premium and pay-as-you-go licenses while keeping costs under control. Before approving a new app, teams should understand who will use it, how often they will access it, and how that usage will affect licensing costs.