Editorial photograph of a development team reviewing a low code application dashboard on a large screen
Guide · Microsoft · Power Platform

Microsoft Power Apps licensing in 2026. What it really costs.

Power Apps ships in two paid plans, a pay as you go meter, and seeded rights inside Microsoft 365 and Dynamics 365. The plan you pick changes cost per user by a wide margin.

Get the EA Renewal Playbook Microsoft Hub
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Power Apps licensing looks simple until premium connectors, Dataverse capacity, and seeded use rights collide. This guide maps every model to real per user cost.

Key takeaways

  • Two paid plans: the per app plan covers one app, the premium plan covers unlimited apps per user.
  • Seeded rights: Microsoft 365 and Dynamics 365 include limited Power Apps use inside their own apps only.
  • Pay as you go: an Azure meter bills per app per active user each month with no upfront commitment.
  • Dataverse is the hidden cost: storage and premium connectors drive most surprise overages.
  • Governance first: unmanaged maker sprawl is the top reason Power Apps spend runs ahead of value.
  • Levers exist: right sizing plans and consolidating environments cut spend without blocking makers.

How is Power Apps licensed in 2026?

Power Apps sells through two standalone plans plus a pay as you go meter. Microsoft publishes the current rates on its Power Apps pricing page.

The per app plan licenses one user to run one application. The premium plan licenses one user to run unlimited applications and includes broader Dataverse rights.

  • Per app plan: one user, one app, lowest entry price.
  • Premium plan: one user, unlimited apps, full premium connector and Dataverse access.
  • Pay as you go: billed through an Azure subscription per app per active user.

Which Power Apps rights come free with Microsoft 365?

Microsoft 365 and Office 365 plans include seeded Power Apps rights, but only to customize and extend the Microsoft 365 apps themselves. The Power Platform licensing FAQ sets the boundary, and the Microsoft 365 service description confirms it.

Seeded rights use standard connectors only. The moment an app touches a premium connector or custom Dataverse table, it needs a paid plan.

When does a seeded user need a paid Power Apps license?

A seeded user crosses into paid territory the moment an app uses a premium feature. The trigger is the connector and the data source, not the number of users.

Three triggers force a paid plan.

  • Premium connectors: SQL Server, Azure services, custom connectors, and most systems outside Microsoft.
  • Custom Dataverse tables: any table beyond the seeded Microsoft 365 entities.
  • Standalone apps: any app that runs outside the Microsoft 365 app context.

Do Dynamics 365 licenses include Power Apps?

Dynamics 365 enterprise licenses include Power Apps rights to extend the Dynamics application within the same environment. Apps built outside that scope need their own Power Apps license.

Why does Dataverse drive most Power Apps overages?

Dataverse is the database under Power Apps, and its capacity model is the most common source of surprise cost. Storage splits into database, file, and log capacity, each metered separately.

Microsoft documents the entitlements and overage rates in the Dataverse capacity documentation.

How is Dataverse capacity calculated?

Each tenant gets a base entitlement plus per license accruals. Once consumption passes the pooled entitlement, overage bills monthly. Large file columns and audit logs are the usual culprits.

  • Database capacity: structured table rows and indexes.
  • File capacity: attachments and large columns.
  • Log capacity: auditing and change tracking.

What do premium connectors add to the bill?

Premium connectors do not carry a separate fee, but they force the user onto a premium or per app plan. On large estates that reclassification is the single biggest line item.

What does Power Apps really cost per user?

Real cost per user depends on plan mix, Dataverse consumption, and how many makers actually build versus consume. The table below shows the typical buyer view.

How do you model the cheapest compliant mix?

Map every app to its connectors and data sources first. Assign seeded users where the app stays standard, per app where a user needs one premium app, and premium only for true multi app makers.

Power Apps licensing models compared

ModelScopeBest forWatch out for
Per app planOne app per userTargeted single app rolloutsCost climbs once a user needs two or more apps
Premium planUnlimited apps per userHeavy makers and broad portfoliosOverpaying for light or occasional users
Pay as you goPer active user per appPilots and variable demandUnbudgeted spikes without spend alerts
Seeded in Microsoft 365Standard connectors onlyExtending Microsoft 365 appsPremium connector use voids the seeding

What buyer side moves cut Power Apps spend?

Power Apps spend responds to design and governance more than to discounting. The biggest savings come from removing premium triggers that were never needed.

  • Redesign to standard connectors where a premium source was used out of habit.
  • Consolidate environments to expose duplicate apps and unused Dataverse capacity.
  • Set capacity and spend alerts so overages never arrive as a surprise.
  • Right size plan mix at each renewal against real maker activity.

How does governance protect the budget?

A managed environment strategy with data loss prevention policies stops makers from quietly attaching premium connectors. Governance is the control that keeps seeded users seeded.

Can Power Apps pricing be negotiated in an EA?

Yes. Power Platform sits inside the Microsoft Enterprise Agreement and is negotiable at renewal. Read terms against the published rates and the official Power Platform licensing guide before you commit volume.

Where the common advice on Power Apps licensing is wrong

The standard Microsoft partner pitch is that every maker should sit on the premium plan because it is simple and future proof. We disagree. In roughly 25 of 35 Power Apps estates Fredrik Filipsson reviewed, more than a third of premium seats ran a single app that used only standard connectors. Those users belonged on seeded rights or a per app plan at a fraction of the cost. The buyer side move is to license to the app and the connector, not to the maker title. Simplicity sold by the reseller is usually budget left on the table.

Editorial photograph of a business analyst building a Power Apps screen at a workstation
Most Power Apps cost lives below the canvas, in Dataverse capacity and the connectors each screen quietly calls.
1 in 3
Premium seats we found overlicensed
10 to 20%
Typical Dataverse overage when unmanaged
30 to 40
Power Platform engagements reviewed

Source: Redress Compliance advisory engagement file, 2024 to 2025.

License Power Apps to the app and the connector, not to the maker. The seat is rarely where the money goes.

What to do next

  1. Inventory every Power App and tag its connectors and data sources.
  2. Flag apps using premium connectors that could revert to standard.
  3. Map each user to the cheapest compliant model: seeded, per app, or premium.
  4. Set Dataverse capacity and pay as you go spend alerts.
  5. Consolidate redundant environments and retire duplicate apps.
  6. Benchmark Power Platform terms before the next EA renewal.
  7. Run the Microsoft 365 license optimizer to size the full estate.

Frequently asked questions

Is there a free version of Power Apps?

Power Apps offers a free developer plan for individual learning and a trial of paid plans. Production apps for business users require a paid plan or seeded rights inside Microsoft 365.

What is the difference between the per app and premium plans?

The per app plan licenses one user to run one application. The premium plan licenses one user to run unlimited applications with full premium connector and Dataverse rights.

Do Microsoft 365 licenses include Power Apps?

Microsoft 365 includes seeded Power Apps rights to extend the Microsoft 365 apps using standard connectors only. Standalone apps or premium connectors require a paid plan.

What triggers a premium Power Apps license?

Three triggers force a paid plan: using a premium or custom connector, creating custom Dataverse tables, or running an app outside the Microsoft 365 app context.

Why is my Dataverse bill higher than expected?

Dataverse meters database, file, and log capacity separately. Audit logs and large file columns drive most overages. Set a capacity alert before consumption passes the pooled entitlement.

Is pay as you go cheaper than a plan?

Pay as you go is cheaper for variable or low usage because it bills only active users each month. For steady heavy use, a named plan is usually cheaper per user.

Can Power Apps be included in a Microsoft EA?

Yes. Power Platform is part of the Microsoft Enterprise Agreement and is negotiable at renewal. Volume commitments should be priced against real maker activity.

How do you reduce Power Apps licensing cost?

Redesign apps to standard connectors where possible, consolidate environments, right size plan mix against activity, and set capacity and spend alerts to stop overages.

Size your Power Platform and Microsoft 365 estate in under five minutes.
Open the 365 Optimizer →
More Reading

More from this practice.

Microsoft Hub →
Power Platform licensing guide
Microsoft
Power Platform Licensing Guide
How Power Apps, Power Automate, and Power BI license together.
9 min read
Dynamics 365 licensing guide
Microsoft
Dynamics 365 Licensing Complete Guide
App modules, team member rights, and dual use across the estate.
11 min read
Microsoft licensing guide 2026
Microsoft
Microsoft Licensing Guide 2026
The full buyer view across EA, CSP, and cloud agreements.
12 min read
Microsoft 365 license types compared
Microsoft
Microsoft 365 License Types Compared
E3, E5, F3, and Business plans side by side.
10 min read
Editorial photograph of an enterprise boardroom set for a vendor negotiation

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay Microsoft for the next three years.

Buyer side intelligence, every two weeks.

Microsoft licensing moves, benchmark ranges, and renewal levers. No vendor spin.