Power Apps Premium or Per App: which license for which application

The Per-App license is worthwhile when a small number of employees each use a single, clearly defined app, while a user-based license makes sense as soon as a user needs multiple apps or access to premium connectors, on-premises data sources, or a full Dataverse environment. Which option is cheaper in any given case depends on the exact number of users per app and should always be compared against Microsoft's current pricing list. Status: August 2026.

What exactly does a Per-App license cover?

According to Microsoft's official documentation on Per-App plans a Per-App license entitles a user to operate a single app or portal in a specific environment. The license is not assigned directly to individuals, but allocated as capacity within an environment in the Power Platform Admin Center and automatically assigned to the respective user when the app is shared. Important for calculation: if someone uses the same app in two environments like test and production, they consume two licenses according to the example calculation in Microsoft's documentation, because allocation is done per environment.

How many apps does a single license cover?

This has changed historically. Until the end of September 2021, an app pass granted access to two apps and one portal. Since October 2021, each license only covers one app or portal to simplify the model. Existing customers with contracts from before October 2021 retain three app passes per license for their contract duration and thus continue to have access to two apps and one portal. Anyone purchasing new today must calculate more strictly than older contracts would suggest.

Where does the free Power Apps basic offering end?

The basic offering included in Microsoft 365, \"Power Apps for Microsoft 365,\" allows according to Microsoft's licensing overview for the Power Platform the creation, execution, and sharing of apps as well as the connection to Microsoft 365 data and standard connectors. What is explicitly missing from this overview: access to on-premises data sources and premium or custom connectors. This is exactly where the decision for a paid license comes in, whether Per App or a user-based full version. Without one of these two, every app remains limited to Microsoft 365 built-in capabilities.

When is Per App worthwhile, when is a user-based license better?

Three scenarios as they typically occur in SMEs:

• Single department app: Ten employees in warehouse logistics use exclusively a stock app. Here a Per-App allocation to the respective environment is sufficient because no one needs a second app.
• Power users with multiple apps: A controller uses a travel expense app, an approval app, and a reporting app in parallel. As soon as a single user needs more than one or two apps, the calculation almost always tips in favor of user-based licensing because otherwise multiple Per-App allocations are needed for the same person.
• App with premium connector: An app that accesses an on-premises database via an On-Premises Data Gateway or uses a premium connector requires a paid license in any case, regardless of the number of users, because the free basic offering does not include this access according to Microsoft's documentation.

A note on Power Automate: A Per-App allocation alone does not entitle you, according to Microsoft, to create or own your own flows with premium features. For that, an additional Per-User license for Power Apps or Power Automate is required, unless the flow is tightly coupled to an app. If you want to calculate this licensing landscape for your own operations, you can find support in a Power Automate licensing consultation.

Frequently asked questions about Power Apps Premium and Per App

Can I mix Per-App and user-based licenses?

Yes, this is actually the normal case in practice. Individual environments or departments run on Per-App capacity, while power users with multiple apps receive a user-based license. According to Microsoft, both license types can be managed in parallel within the same organization.

Does a Per-App license count for multiple environments?

No. Capacity is allocated per environment, and a user who uses the same app in two separate environments like test and production consumes two licenses according to Microsoft's documentation example calculation.

What happens if I reduce the Per-App capacity of an environment to zero?

Users already created in Dataverse are not automatically deactivated by this, but they can no longer start apps in this environment because no capacity is allocated. Microsoft explicitly advises administrators to also remove the roles of affected users in this case.

Do I really need a paid license for simple approval apps?

Not necessarily, as long as the app works exclusively with Microsoft 365 data and standard connectors. As soon as a premium connector, an on-premises data source, or a custom Dataverse table outside of standard integration comes into play, a paid license is required according to Microsoft's licensing overview.