Spoke / Power Platform
Microsoft Power Apps licensing guide.
Power Apps starts cheap. It ends expensive. The licensing model has five entry points and three escalation traps. This guide sets out the buyer side framework for every one.
Power Apps starts cheap. It ends expensive. The licensing model has five entry points and three escalation traps. This guide sets out the buyer side framework for every one.
Power Apps licensing is simple at the door and complex once apps are in production. The buyer side framework keeps the cost honest.
Power Apps sits inside Microsoft Power Platform alongside Power Automate, Power BI, and Power Pages. Licensing across the four products interlocks, and Power Apps is where the most expensive surprises land.
Microsoft positions Power Apps as the citizen developer platform. The pricing model is built to start small and scale fast, and the scaling curve catches most enterprise estates off guard.
What follows is the buyer side framework. The licensing model, the five entry points, the three escalation traps, the Dataverse limits, the citizen developer dynamic, and the governance posture.
Power Apps is licensed per user, per app, by consumption, or by inclusion in another Microsoft plan.
Canvas apps, model driven apps, portals, the developer tools, and the underlying Dataverse data platform. Each surface meters differently.
Standard connectors come with the included Power Apps entitlements. Premium connectors require a paid Power Apps SKU on every user accessing the app.
Power Platform environments are separate tenants for development, test, and production. Some environments incur capacity costs. Sandbox and trial environments are typically free.
Pick the wrong entry point and the cost curve runs away.
Five dollars per user per app per month. Best for small focused apps with limited user counts.
Around twenty dollars per user per month. Unlimited apps per licensed user.
Metered per active monthly user per app. Billed to a credit card or an Azure subscription.
M365 E3 and E5 include limited Power Apps rights. Standard connectors only, narrow Dataverse limits, and no premium features.
Dynamics 365 plans include rights to build apps that extend Dynamics. Custom apps unrelated to the Dynamics entity still need a Power Apps license.
Power Apps entry points compared.
| Plan | Price | Apps | Best Fit | Trap |
|---|---|---|---|---|
| Per app | $5 / user / app / mo | Per app | Small focused apps | Multiple apps escalate fast |
| Per user | $20 / user / mo | Unlimited | Power user populations | Heavy at low utilization |
| Pay as you go | Metered | Per session | Variable usage | Surprise bills |
| M365 included | Bundled | Standard only | Light internal apps | Premium connector reclassification |
| D365 included | Bundled with Dynamics | Dynamics extension only | Dynamics adjacent apps | Custom apps still need Power Apps SKU |
The licensing scales smoothly until one of three traps fires.
A standard connector is reclassified as premium by Microsoft. Every user accessing the app now needs a paid Power Apps SKU. The change can land overnight.
Apps cross the included Dataverse storage. Additional capacity is sold by the gigabyte at premium rates compared to Azure SQL or Cosmos.
A successful citizen developer app expands. New tables, new users, new integrations. The license model needs to be re evaluated quarterly to stay accurate.
Dataverse is the underlying data platform. The included capacity is small.
Each Power Apps per user license grants a small database, file, and log capacity allotment. Each per app license is much smaller.
Additional database, file, and log capacity is sold separately. Database capacity is the most expensive line.
Apps can use Azure SQL, Cosmos, or Dataverse for Teams to reduce premium Dataverse load. The architecture decision drives cost more than the licensing decision.
Power Apps does not have a pricing problem. It has a scope problem. Governance is the answer to scope.
Citizen developer programs ship apps fast. Cost follows.
Business unit launches Power Apps initiative. Apps proliferate. Premium connectors land. License count escalates outside procurement view.
Surprise Power Apps add on lines in the quarterly Microsoft billing review. New environments appearing in the admin centre. Premium connector usage rising.
Environment governance, connector approval workflow, capacity monitoring, and quarterly app inventory.
A governance posture from day one is the only sustainable defense.
Joint forum across IT, procurement, and business. Quarterly review of app inventory, license posture, and capacity.
Standard connectors approved by default. Premium connectors require business case and license budget. Custom connectors require IT review.
Power Platform admin centre, plus a custom dashboard for license consumption, environment count, and Dataverse capacity.
Power Apps builds user facing applications. Power Automate runs background workflows. Licensing is separate but interlinked through Dataverse and connector mix.
Microsoft publishes the list and updates it. Common premium connectors include SQL Server, Salesforce, ServiceNow, Oracle, and most enterprise systems. Standard connectors cover Microsoft 365 services and a handful of public APIs.
No. Any user accessing an app that uses a premium connector must hold a Power Apps per user or per app license.
Limit Dataverse use to data that has to live there. Push other data to Azure SQL or Cosmos. Monitor capacity and clean up unused tables and environments quarterly.
Rarely for production apps. It is useful for prototypes and burst usage. Sustained production usage almost always costs more on Pay as you go than on per app or per user plans.
Inside the broader Power Platform line. The EA negotiation should set unit prices, capacity, and the premium connector posture for the term.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Power Apps is a free trial dressed as a platform. The trial ends when the citizen developer ships something useful.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Monthly briefings on Microsoft EA, MACC, Copilot, Power Platform, and the buyer side benchmarks across the Microsoft estate.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
