Power Apps licensing has a reputation for being complicated — but almost all of the confusion comes from one question: do you license the person, the app, or the usage? Get that right and the pricing is simple. This guide walks through every Power Apps plan for 2026, what each one really includes, the Dataverse and connector costs hiding underneath, and how to pick the cheapest option that still does the job.

Microsoft has streamlined Power Apps into a small set of choices: Power Apps Premium (per user), pay-as-you-go (metered through Azure), and the “seeded” Power Apps rights included with Microsoft 365 and Dynamics 365. Underneath every paid plan sits Dataverse and premium connectors — the two things you are really paying to unlock. Understand those and the whole model falls into place.

What you’re actually paying for

Every Power App is free to build in Power Apps Studio. The licence decides what your app is allowed to connect to and run on:

• Standard connectors (SharePoint, Outlook, Excel, Teams, OneDrive) are available even with the Power Apps rights seeded into Microsoft 365.
• Premium connectors (SQL Server, Dataverse, Salesforce, custom/HTTP APIs, on-premises data gateway) require a paid Power Apps plan.
• Dataverse — Microsoft’s secure, scalable business database — is the biggest reason to go premium. If your app stores real business data, you want Dataverse, and that means a paid plan.

How Power Apps licensing actually works

Like the rest of the Power Platform, Power Apps licensing is easier once you stop thinking in product names and think in three questions:

1. Who uses it? A known, regular group of users points to per-user Premium. An unknown or occasional audience points to pay-as-you-go.
2. What does it connect to? Microsoft 365 data only → possibly free (seeded). Dataverse, SQL, or custom APIs → paid plan required.
3. How much data, and how important is it? Real business data that must be secure, related, and auditable belongs in Dataverse — which is included in the paid plans but carries its own storage entitlements.

Answer those three and you’ve effectively chosen your plan. Everything else — storage top-ups, AI Builder, portals — is an add-on layered on top of that core decision.

The Power Apps plans at a glance

Power Apps Premium: $20/user/month

Power Apps Premium is the flagship per-user plan. For $20 per user per month, a licensed user can run unlimited custom apps, use every premium connector, and build on Dataverse. It’s the right choice when you have a known group of people using apps regularly — a field team, a finance department, an operations crew.

The value is simplicity: one predictable price per person, no metering, no surprises on the Azure bill. If a user relies on custom apps every day, Premium is almost always the cheapest and calmest option. Premium also includes an allocation of Dataverse storage and access to run model-driven apps (not just canvas apps), which matter as your solutions mature into proper business systems rather than simple forms.

Canvas vs model-driven apps

Premium covers both app types. Canvas apps give you a blank, pixel-level design surface — ideal for task-focused mobile and tablet apps. Model-driven apps are generated from your Dataverse data model and give you a consistent, data-first interface at scale — the same technology Dynamics 365 CE is built on. Serious internal systems usually end up model-driven, which is another reason data-heavy apps gravitate to Premium.

Pay-as-you-go: billed through Azure

Pay-as-you-go flips the model. Instead of committing to per-user seats, you link Power Apps to an Azure subscription and pay only for active users per app, per month. Nobody who doesn’t open the app that month costs you anything.

This is ideal for apps with unpredictable or occasional audiences — a once-a-year open-enrolment app, a seasonal inspection tool, or a pilot where you don’t yet know adoption. The trade-off is variable billing: heavy, consistent usage is usually cheaper on Premium seats than on pay-as-you-go. Because it’s metered through Azure, pay-as-you-go also needs an Azure subscription and a little governance so a popular app doesn’t produce a surprise bill — set spend alerts and review active-user counts monthly.

“What happened to the per-app plan?”

If you researched Power Apps a couple of years ago, you’ll remember a per-app plan — a cheaper licence that let a user run one or two specific apps rather than unlimited apps. Microsoft has since simplified the line-up, consolidating toward the per-user Premium plan and the metered pay-as-you-go model. The practical upshot is that today’s decision is cleaner: regular user → Premium; occasional user → pay-as-you-go. If you still hold legacy per-app licences, plan their transition at renewal so you’re not caught out by the change, and model whether Premium or pay-as-you-go is the better landing spot for those users.

“Seeded” Power Apps rights in Microsoft 365 & Dynamics 365

Many organisations already own Power Apps rights without realising it. Most Microsoft 365 plans include the ability to build and run apps that use standard connectors — approvals, SharePoint-backed forms, Teams apps. And Dynamics 365 licences include Power Apps rights within the context of that Dynamics application: you can extend and customise your Dynamics apps without buying a separate Power Apps licence, as long as you stay within that application’s context (its tables and use case). Step outside — a standalone app using unrelated data — and you need a Power Apps plan.

Before buying anything, audit what your existing licences already grant. It’s common to find you only need to top up a handful of genuine power users while the rest of the organisation is already covered.

Dataverse & storage costs

Dataverse is the secure, relational database that makes Power Apps enterprise-grade — role-based security, relationships, business rules, auditing and scalability that SharePoint lists can’t match. Paid Power Apps plans include a default allocation of Dataverse capacity, split into database, file, and log storage, plus a per-user increment for each Premium seat. Large solutions can exceed the default entitlement, at which point you buy additional capacity.

The practical point: Dataverse is rarely a cost problem for small and mid-size apps, but for data-heavy systems you should size your storage need as part of the licensing decision rather than discovering it later. Good data-model design (avoiding needless duplication, archiving old records) keeps you inside your entitlement longer.

Standard vs premium connectors: the line that decides your licence

Connectors are how Power Apps talks to data and services, and Microsoft splits them into two classes that map directly onto licensing:

If you can list the connectors an app needs, you can immediately tell whether it’s free (seeded) or requires a paid plan. This is the fastest licensing check we run on any new app request.

Power Apps plan comparison

Which Power Apps plan should you buy?

Worked example: licensing an app for 120 users

Add-ons: AI Builder, Copilot and Power Pages

Three things sit alongside the core Power Apps plans and occasionally affect your budget:

• AI Builder — prebuilt and custom AI models (document processing, prediction, object detection) that run on a capacity of “AI credits.” Some allocation comes with paid Power Platform plans; heavy use needs an add-on capacity. If your app reads invoices or classifies images, budget for this.
• Copilot in Power Apps — the AI that helps makers build apps and helps users interact with them in natural language is increasingly built into the platform. Advanced, capacity-backed AI features can carry their own requirements, so treat AI-heavy roadmaps as a licensing question, not just a feature toggle.
• Power Pages — external-facing websites (formerly Power Apps portals) are licensed separately from internal apps, typically by authenticated or anonymous users. If you need to expose an app to customers or partners outside your tenant, that’s Power Pages, not a standard Power Apps seat.

None of these are needed for a typical internal app on day one, but each can become a line item as your solution grows — so it’s worth knowing they exist before they surprise you.

Licence cost is only part of the total cost

One honest caveat: the monthly licence is rarely the biggest number in a Power Apps project. The larger costs are usually design and build, data migration, integration with existing systems, and change management to get people actually using the app. A $20/user licence attached to a poorly designed app that nobody adopts is far more expensive — in wasted effort — than a slightly pricier licence on an app that saves each user an hour a day. When we advise on licensing, we always frame it against this total cost of ownership: the goal isn’t the cheapest licence, it’s the best return on the whole investment.

Governance: keeping Power Apps costs under control

• Right-size per app, not per organisation. Some apps deserve Premium seats; others belong on pay-as-you-go. A blanket policy over-spends on one and under-serves the other.
• Set Azure spend alerts on pay-as-you-go. Metered billing is only a risk if it’s unmonitored — a simple budget alert removes the surprise.
• Reclaim seats from inactive makers and users. Premium licences assigned to people who no longer use their apps are pure waste; review quarterly.
• Establish a Centre of Excellence. Microsoft’s free CoE Starter Kit gives you visibility of every app, its owner, and its connectors — essential for controlling sprawl, security and cost as adoption grows.

Costly Power Apps licensing mistakes

• Buying Premium for occasional users. If people use an app a few times a year, pay-as-you-go usually costs far less.
• Ignoring seeded rights. M365 and Dynamics 365 already include Power Apps rights — don’t double-buy.
• Using SharePoint as a database to “save money.” Complex apps outgrow SharePoint fast; Dataverse on Premium is often cheaper once you count the rework.
• Forgetting the Dynamics context limit. Extending Dynamics is included; a standalone app on unrelated data is not — plan the boundary.
• No governance. Ungoverned pay-as-you-go and app sprawl create both cost and security risk.

How PraviMinds helps

We design Power Platform solutions and the licensing model underneath them — auditing your existing Microsoft 365 and Dynamics 365 entitlements, choosing Premium vs pay-as-you-go per app, sizing Dataverse, and putting governance in place so costs stay predictable as you scale. Because we build the apps as well as advise on licensing, our recommendations are grounded in how your solution will really be used. If you’re planning a Power Apps rollout, we’ll help you license it right the first time.

Frequently asked questions