LowCodeStacks™
Sign in

Power Apps licensing explained: Premium, per app, pay-as-you-go and the Microsoft 365 trap

Which licence a Power Apps user actually needs, what the Microsoft 365 rights really cover, what changed with the per app plan — and the February 2027 enforcement date that will lock unlicensed users out.

Governance & adminQuick reference4 min read

Checked against Microsoft Learn · 5 sourcesPosted by the Maker DeskHow we write guides

Power Apps licensing is the most asked, least understood question in the platform — and the answers changed again this year: the per app plan left the price list for new customers, and Microsoft set a hard enforcement date for areas it had treated leniently. This is the current state, checked against Microsoft Learn on 17 October 2026.

What Microsoft 365 already gives you

Many Microsoft 365 licences include limited Power Apps rights, intended for apps that use Microsoft 365 data and standard connectors — SharePoint, Outlook, Teams and the rest of the standard list. Two traps hide in that sentence:

  • SQL Server, Azure connectors and Dynamics 365 connectors are premium, even though they feel like everyday plumbing. An app on SQL Server needs premium licensing for every user.
  • Some Microsoft 365 licences show a Dataverse service plan in the admin center. It exists for Microsoft 365's own features — it does not entitle users to run standalone custom apps, premium flows or agents.

What makes an app premium

A user needs a premium licence when the app uses premium, on-premises or custom connectors — which includes every app built on Dataverse — and, from February 2027, whenever the app runs in a managed environment or is a model-driven app (see the enforcement date).

The three premium models

ModelWhat it coversListed price (Microsoft's licensing FAQ, October 2026)
Power Apps PremiumPer user: unlimited apps and Power Pages websites$20/user/month, $12 with 2,000+ new licences
Power Apps per appPer user, per app: one app or one website; stackable$5/user/app/month — no longer sold to new customers through some channels since January 2, 2026
Pay-as-you-goBilled through Azure per unique user who opened the app that month; no upfront commitmentAzure meter

Note

Prices change; treat the numbers as the state on the check date and confirm on Microsoft's pricing page before budgeting.

Rules of thumb Microsoft's own guidance supports:

Do

  • Premium for people living in several apps daily.
  • Pay-as-you-go for widely shared apps with infrequent, unpredictable use — and to measure real adoption before committing to licences.
  • Dynamics 365 enterprise licences already carry Power Apps rights within the context of the licensed Dynamics application.

Don't

  • Don't plan new budgets around the per app plan without confirming your purchasing channel still offers it.
  • Don't treat the free Developer Plan as production hosting — it never was, and its unmanaged environments are being deleted from January 15, 2027 anyway.

The February 2027 enforcement date

Microsoft states that premium licensing requirements were applied leniently in some areas, and that leniency ends: starting February 2027, users without an appropriate premium licence can't open the app in these cases:

  • apps in managed environments,
  • model-driven apps,
  • custom apps used outside a Dynamics 365 environment context.

The requirement itself isn't new — only the enforcement is. To find who's exposed, download the Power Apps licensing reports in the Power Platform admin center (Licensing > Power Apps), which show per-user licences purchased, assigned and actually used, per app licence allocations and pay-as-you-go plans.

Getting ahead of the enforcement
  1. Download the licensing report
  2. List users without premium rights
  3. Decide Premium, per app stock or pay-as-you-go
  4. Assign before February 2027

Sources

Was this helpful?

Comments

No comments yet. Share what worked for you.

Sign in to comment. Comments show under a display name you choose, never your email.