Power Apps licensing for small business: what running an app costs per user, per month

Two different questions get asked with the same words. What does it cost to have an app built is a one-time, scope-driven number, and we work that one through separately in what a Power Apps development project costs. What does it cost to run that app every month afterwards is a Microsoft price list question with a small number of correct answers. Everything below is the second question.

All list prices here were read from Microsoft's own pages on 14 September 2026 and are quoted with the source linked. They move. Microsoft Made Easy publishes no prices for Microsoft licences of its own, does not resell them and is not a Cloud Solution Provider — you buy in your own tenant or through whoever bills you today, and we advise on what to buy.

Start with the entitlement you are already paying for

Every Microsoft 365 seat carries seeded Power Apps rights, and they go further than most teams assume. Microsoft's Power Platform licensing FAQ (opens in new tab) answers the question “how many apps can I run with Microsoft 365 plans” with: there is no limit on the number of applications, and customers can continue to run standalone apps to extend and customize Microsoft 365 using standard connectors.

That is the sentence that should shape a small-business budget. A field inspection app, a purchase-request form, a site visit log and an onboarding checklist — four apps, all reading and writing SharePoint lists, all used by everyone with a mailbox — add nothing to the monthly bill. The constraint was never how many apps you build. It is what each app touches.

The two lines that end the free tier

The first line is the connector. The same FAQ lists the connectors reclassified as premium — SQL Server, the Azure family, Dynamics 365, Service Bus and Event Hubs among them — and states that a standalone Power Apps or Power Automate plan licence is required to access all premium, on-premises and custom connectors. An app that reads a SQL database in your server closet, or reaches a line-of-business system through the on-premises data gateway, is a paid app from the day it ships.

The second line is the data platform, and it is the one that catches small teams out. Dataverse is a licensed capability, so choosing it as an app's backend makes that app a paid app for every person who opens it. That single consequence is often decisive, and it belongs in the backend decision rather than after it — we compare the two options properly in Dataverse vs SharePoint lists for Power Apps, and if the answer is Dataverse, our Microsoft Dataverse consulting services model the tables and the capacity together.

Nothing else moves the needle for a company this size. Model-driven apps and Power Pages sit on the paid side because they are Dataverse-backed by definition. AI Builder and Copilot features are metered separately. Everything a canvas app does against Microsoft 365 data is already covered.

The plans, side by side, with the prices read today

Four ways a small business pays for Power Apps. The Premium figures come from Microsoft's Power Apps pricing page (opens in new tab), the per app figure from the licensing FAQ cited above, and the meter rate from Microsoft's pay-as-you-go meters documentation (opens in new tab) — all read on 14 September 2026.

One row on that pricing page is deliberately not in the table: a $12.00 per user per month tier that requires a minimum of 2,000 new user licences. It is quoted in a lot of blog posts about small-business pricing, and no company reading this page will ever qualify for it.

Per app or per user? The break-even, and the plan that quietly closed

This used to be the central question, and for many buyers it is now settled by availability rather than by arithmetic. Microsoft's per app end-of-sale notice (opens in new tab) states that effective January 2, 2026 the Power Apps per app SKU is no longer available for purchase by new customers. The channel detail is what matters to a small business: existing and new CSP customers are not impacted and can continue to purchase, use and renew; Enterprise Agreement customers see no disruption and can renew; MPSA customers lose the offer at the end of their agreement and get a 60-day window to move. Meanwhile Microsoft's admin licensing FAQ still documents the plan at $5 per user per app per month. Both things are true at once, which is why the third-party guides ranking for this search contradict each other.

So the practical sequence is: ask whoever bills you whether per app is still on your paper. If you buy through a CSP partner, it probably is. If you are buying direct, or your agreement is MPSA, plan on Premium or the meter and do not build a budget on a number you cannot purchase.

Where the choice still exists, the arithmetic is simple and worth doing on the back of an envelope. Per app licences are stackable, so four of them for one person cost the same as one Premium seat — the break-even is four apps per person. Below four paid apps each, per app wins; at four it is a tie and Premium buys you headroom; above four, Premium is cheaper and simpler to administer. Against the pay-as-you-go meter, the break-even is two: a person who opens two metered apps in a month has already cost more than a Premium seat would. The meter's real advantage is not the rate, it is that a user who opens nothing costs nothing that month.

What this looks like for a real-sized company

Illustrative scenarios — not clients. A 60-person contractor runs three canvas apps on SharePoint lists: daily logs, a safety checklist, a materials request. Every user already holds a Microsoft 365 seat. The incremental Power Apps licence cost is zero, and it stays zero however many more list-backed apps they build.

Same company, one change: the daily log app needs to read job costs from an on-premises SQL Server through the gateway. That app is now premium, and everyone who opens it needs cover. Forty field staff at the Premium list price is a materially different renewal from zero — and the cheapest fix is often architectural rather than commercial. Staging the SQL data into a SharePoint list on a schedule, or restricting the premium app to the eight people who genuinely need live cost data while the other thirty-two keep the free app, are both legitimate answers that a licensing page alone would never surface.

Third variation: a 120-person distributor with a Dataverse-backed quality app opened by twelve inspectors daily and by roughly thirty others a few times a year. Twelve Premium seats plus the meter for the occasional users is usually cheaper than forty-two seats, because the meter only counts the months someone actually opens the app. That split is administrable, but it needs an environment linked to an Azure subscription and someone watching the usage report — which is governance work, not a purchasing decision.

The costs that appear after go-live

Three recurring items do not show up in the plan comparison, and all three surprise people. Dataverse storage is the first: each Premium licence accrues a modest pooled allowance to the tenant — 250 MB of database and 2 GB of file capacity per seat — and beyond the pool, Microsoft's pricing page listed the Dataverse database capacity add-on at $40.00 per GB per month on 14 September 2026. Apps that store photos or scanned documents reach that line far faster than apps that store rows.

Guests and external users are the second. A guest running a shared canvas app needs the same licence a staff member would, assigned in either their home tenant or yours. An app shared with subcontractors or clients is a licensing decision before it is a design decision, and Power Pages is usually the right shape for genuinely external audiences instead.

Licence drift is the third and the most expensive over time: seats assigned to people who have left, seats bought for a pilot that never scaled, add-ons duplicating something a bundle already includes. That is the same estate-wide problem we review in Microsoft 365 license optimization, and Power Platform seats drift faster than most because they are bought in ones and twos by whoever needed the app first. Keeping an inventory of every app, its owner and its licence position is part of Power Platform governance — and it is the cheapest control on this page, because it costs nothing and catches the seats nobody cancelled.

How to settle this in an afternoon

Four steps, in order. First, list every app and write down its data sources — not its purpose, its connectors. Second, mark each app free or paid by the two lines above: premium or custom connector, or Dataverse. Third, for each paid app, count the people who open it and how often, because that count, not headcount, is what you are buying. Fourth, ask your billing channel what it can actually sell you before you compare plans, since the per app answer now depends on the paper you buy under.

Licensing is the recurring half of a Power Apps decision; the build is the one-time half. Our Power Apps consulting scopes state the licence position for every app up front — covered by your existing Microsoft 365 rights, or needing a paid seat, and for how many people — so nothing about the renewal is a surprise. The same renewal usually covers automation and reporting too, and those two price on completely different logic: read Power Automate licensing for small business for the flow side and Power BI licensing for small business for the reporting side rather than assuming the three products work the same way. Every engagement is a fixed fee agreed in writing before any work starts — see how the fixed-fee process works.