Power Apps Licensing Explained: Premium, Per App, Pay-As-You-Go and Microsoft 365

Power Apps licensing becomes much easier when you answer two questions in order:

1. What capabilities does the app use?
2. Which people will run it, and how often?

Do not choose a plan from the app's screen count or the maker's licence. Users consume the app and its connections, and their entitlement must cover that use.

This guide was fact-checked against Microsoft Learn on 15 August 2026. Prices below are Microsoft's public US list prices shown on that date. Verify the live Power Apps pricing page, your region, tax and commercial agreement before buying.

The short answer

Situation	Likely starting entitlement	Critical check
App extends Microsoft 365 and uses only standard connectors	Power Apps rights included with an eligible Microsoft 365 licence	Confirm every connector is standard and the environment/governance model does not introduce premium rights
One person runs many premium custom apps	Power Apps Premium	It is assigned per user, not per tenant
A defined group runs one premium app	Power Apps per app	One licence covers one user, one app, in one environment; stack licences for more apps
Usage is sparse or unpredictable	Power Apps pay-as-you-go	Azure subscription, environment linkage and $10 active user/app/month meter
One maker is learning or building a proof of concept	Power Apps Developer Plan	Development/test environment only; no production entitlement
App runs in a Managed Environment	Qualifying standalone licence or supported pay-as-you-go	Microsoft 365 seeded rights alone do not cover active use there

There is no reliable “free versus paid” shortcut. A simple-looking app can require premium rights because of one SQL, Dataverse, custom connector or on-premises connection.

What Power Apps rights in Microsoft 365 cover

Eligible Microsoft 365 plans include seeded Power Apps capabilities for extending Microsoft 365.

Microsoft's current Power Platform licensing overview says those rights include creating, running and sharing apps, using Microsoft 365 data and connecting to cloud services through standard connectors.

They do not include:

• premium connectors;
• custom connectors;
• on-premises data through a gateway; or
• general full Dataverse rights for custom apps.

Some Microsoft 365 products expose a limited Dataverse service plan for that Microsoft application. Microsoft explicitly says those limited capabilities cannot be used as a general right to run custom apps or flows against other data.

A common standard-connector scenario

An internal canvas app reads and updates a SharePoint list and is used by employees who already have eligible Microsoft 365 licences. If every connector remains standard and no premium environment/governance condition applies, the seeded rights may be enough.

Do not stop at “the data is in Microsoft 365”. Check each connector in the app and each flow the app invokes. A single premium connector can change the requirement for the relevant users.

Power Apps Premium

Microsoft's current Power Platform licensing FAQ lists Power Apps Premium at $20 per user/month, or $12 per user/month with 2,000+ new user licences.

It entitles the licensed user to build, modernise and run unlimited custom applications and access unlimited websites within the plan's terms.

“Unlimited” is not an organisation-wide promise. It means the licensed user is not licensed app-by-app. Capacity, request limits, environment policy, connector terms and other service limits still exist.

Premium is a sensible starting point when a person uses several premium apps, is a regular maker who also runs them, or needs broad premium capability across business scenarios.

Power Apps per app

Microsoft lists Power Apps per app at $5 per user/app/month.

Each per-app licence gives one named user rights to one app—canvas and/or model-driven—within one environment for a specific business scenario. The entitlement is stackable: a user who needs three separate apps may need three per-app licences unless Premium or another qualifying right is more appropriate.

The licence follows the user/app entitlement, not the number of screens or data tables. Ten screens inside one app do not become ten app licences. Two separately launched apps are not automatically one licence because they support the same department.

Per app often fits a defined solution with a stable user population, especially when most of those people use only that premium app.

Power Apps pay-as-you-go

Pay-as-you-go links a Power Platform environment to an Azure subscription and meters use.

Microsoft's current pay-as-you-go meter charges $10 per unique active user/app/month for Power Apps. A person is active when they open the app at least once in the month; repeat access to the same app in that month is not counted again. Users already covered by qualifying Power Apps per-user or Dynamics rights are excluded from that meter.

Pay-as-you-go can suit:

• seasonal apps;
• pilots with uncertain adoption;
• occasional external or internal use; and
• workloads where buying a licence for every possible user would materially exceed observed activity.

It is not automatically cheaper. At the checked list prices, one user opening one app in a month is $10 on the meter versus $5 for an assigned per-app licence. The operational advantage is avoiding advance licence assignment for uncertain users, not a universal lower unit price.

Model at least three scenarios: expected, high and low monthly active users. Include Azure ownership, cost alerts, Dataverse capacity and any other enabled meters in the operational plan.

Power Apps Developer Plan

The Power Apps Developer Plan gives an individual a developer environment with premium capabilities for development and test.

Microsoft documents that apps can be shared in that environment for development/testing, and coworkers can be added in certain maker/admin roles. It also says the environment is not for production use. A paid plan is required to deploy or run a production solution.

Use it to learn, prototype, build in solutions and validate an approach. Do not use it as a free production department environment or tell a team that test sharing is a production licence.

Developer environments also have capacity and inactivity rules. Export the solution to an appropriately governed environment as part of the production path.

Trials are temporary evaluation rights

A Power Apps trial is useful for validating premium functionality and a production-style scenario for a limited period. It is not a licensing strategy.

Before a trial ends:

1. inventory the app and its dependencies;
2. identify every user and environment;
3. choose the long-term entitlement;
4. assign or configure it; and
5. test as a non-maker user.

A successful trial proves the design can work. It does not prove the final licence has been purchased or assigned.

Managed Environments change the entitlement check

Managed Environments add governance capabilities, but active use carries a licensing boundary.

Microsoft's Managed Environments licensing guidance says active users require a qualifying standalone Power Apps, Power Automate, Copilot Studio, Power Pages or Dynamics entitlement, or a supported pay-as-you-go meter.

Do not assume a user covered by Microsoft 365 standard-connector rights can run the same app in a Managed Environment without another check. Decide the governance model before calculating price.

The Developer Plan also does not include Managed Environment use rights for running assets. A maker running their own app in a managed developer environment can need a premium entitlement in addition to the Developer Plan.

Guest users are still users

Sharing a canvas app with a Microsoft Entra B2B guest does not remove the licensing requirement.

Microsoft's licensing FAQ says a guest needs a Power Apps licence through the host tenant or the guest's home tenant, subject to the scenario. When Dataverse is the data source, the guest's licence must align with the tenant where that Dataverse data resides.

Guest access also requires:

• Entra B2B collaboration settings;
• app sharing;
• access to each underlying data source;
• appropriate connector rights; and
• testing in the resource tenant.

“The guest accepted the invitation” is identity evidence, not proof of app/data/licence access.

Dynamics 365 rights are in-context rights

Some Dynamics 365 licences include Power Apps use rights so users can extend and customise the licensed Dynamics application.

Do not treat a Dynamics entitlement as a general Power Apps Premium licence for unrelated standalone applications. Check the current Dynamics 365 Licensing Guide and whether the custom app is genuinely in the context of the licensed Dynamics application.

Flows used by an app need their own check

An app can call Power Automate flows, but that relationship does not make every flow free or correctly licensed.

Inventory:

• instant flows started by an app user;
• automated flows associated with the app;
• premium/custom connectors in those flows;
• child flows;
• service accounts or process licences; and
• unattended desktop automation.

Use the current Microsoft licensing FAQ for the precise flow pattern. Do not infer flow rights from the app maker's licence.

How to choose with real numbers

Create a licence inventory before asking procurement for a quote.

1. List the apps and environments

Record app ID, environment, owner, production status, user groups, launch route and whether the environment is managed.

2. Inventory every dependency

List connectors, Dataverse, gateways, custom connectors, embedded apps, flows, AI Builder, Power Pages and external-user requirements.

3. Count people by behaviour

Separate:

• regular multi-app users;
• users of one premium app;
• occasional/seasonal users;
• makers and administrators; and
• guests.

4. Compare plans, not just list prices

For each cohort compare:

• Premium users × negotiated Premium price;
• per-app user/app assignments × negotiated per-app price; and
• expected unique active user/app months × pay-as-you-go meter.

Include administration, Azure cost ownership, capacity and the cost of people being unable to work when an entitlement is missing.

5. Prove the chosen design

Test with representative non-owner users in the production environment. Check the app, data, flows and premium prompts. Review licence assignment and environment analytics after the test.

A small worked comparison

Suppose 120 employees need one premium inspection app every month.

At the public prices checked on 15 August 2026:

• per app: 120 × $5 = $600/month;
• pay-as-you-go, if all 120 are active: 120 × $10 = $1,200/month; and
• Premium: 120 × $20 = $2,400/month before volume/contract pricing.

Per app looks strongest for that deliberately simplified one-app cohort.

Now suppose only 12 of 120 possible users open it in a typical month. Pay-as-you-go would meter about $120 for that month, and assignment overhead may fall. But a peak month with all 120 users returns to $1,200.

This example excludes tax, negotiated discounts, other meters, capacity and every product change after the checked date. It demonstrates the method, not a quotation.

The recommendation

• Stay with eligible Microsoft 365 seeded rights when the app genuinely uses standard capabilities in the permitted context.
• Use per app for a stable group using one premium app.
• Use Premium for people who use several premium apps or need broad premium maker/user rights.
• Use pay-as-you-go when active use is sparse or uncertain and Azure-backed metering is operationally acceptable.
• Use Developer Plan for development/test only.

Then re-check the complete solution whenever someone adds a connector, moves environment, enables Managed Environments, introduces guests or changes a flow.

For practical build and governance help, join the Power Apps Mastery Space.

Frequently asked questions

Is Power Apps included with Microsoft 365?

Eligible Microsoft 365 plans include seeded rights for apps using Microsoft 365 data and standard connectors. Premium/custom connectors, on-premises data and full custom Dataverse scenarios require another entitlement.

What is the difference between Power Apps Premium and per app?

Premium licenses a named user to run unlimited custom apps within the plan's terms. Per app licenses one named user for one app in one environment and can be stacked for additional apps.

Is Power Apps pay-as-you-go cheaper than per app?

Not automatically. Microsoft currently lists $10 per active user/app/month for the meter and $5 per user/app/month for per app. Pay-as-you-go can win when only a small fraction of possible users are active, but model peak months and operations.

Can I run a production app on the Power Apps Developer Plan?

No. Microsoft says the Developer Plan is for development and test in a developer environment. Sharing for testing is possible, but paid rights are required for production deployment/use.

Do guest users need Power Apps licences?

Yes, when the app scenario requires Power Apps rights. The qualifying licence can depend on the host/home tenant and data source; Dataverse guest licensing must align with the tenant where the data is located.