The Low-Code Platform with Enterprise-Scale Licensing Complexity. What Starts as "Anyone Can Build an App" Becomes "Everyone Needs a Licence" Faster Than You Think. This guide maps the entire Power Apps licensing landscape: what is included, what costs extra, the Per App vs Per User decision, the governance framework that prevents licensing sprawl, and the negotiation strategies for managing Power Apps costs within the EA.
This guide is part of the Microsoft Knowledge Hub. For the comprehensive reference, see the Microsoft Licensing Guide 2026. For the broader Power Platform strategy, see the CIO Playbook for Power Platform Licensing. For M365 plan entitlements, see Microsoft 365 E3 vs E5 vs F3.
Power Apps licensing operates across three layers that determine what a user can build, what data sources they can connect to, and what the enterprise pays. Understanding these three layers is the foundation for every licensing decision.
Every Microsoft 365 licence (E1, E3, E5, F1, F3, Business Basic, Business Standard, Business Premium) includes limited Power Apps entitlements at no additional cost. These seeded entitlements allow users to create and run canvas apps that use standard connectors and Microsoft 365 data sources (SharePoint, Excel, OneDrive, Outlook, Teams). Dynamics 365 licences include broader Power Apps entitlements that allow running apps within the Dynamics 365 environment.
What the seeded entitlement does NOT include: Access to premium connectors (SQL Server, Dataverse, HTTP, Azure services, Salesforce, SAP, ServiceNow, Oracle, and many more). Access to the full Dataverse environment (the production-grade relational data platform). Access to on-premises data gateways. Access to custom connectors that use premium connection types. Model-driven apps (which require Dataverse and therefore a standalone licence). AI Builder credits. Power Pages (external-facing portals).
This is where most organisations encounter their first Power Apps licensing surprise. A business user builds a useful app in Power Apps using their M365 seeded entitlement. It connects to SharePoint, which is a standard connector. Then they add a connection to a SQL Server database to pull real-time inventory data. The moment they add that SQL Server connection, the app now uses a premium connector, and every user who runs the app needs a standalone Power Apps licence (Per App or Per User). The builder may not even realise the licensing implication has changed. The IT team discovers it when the SQL Server connector begins prompting users for a licence, or worse, at the next audit reconciliation.
The Per App plan grants a single user the right to run a single app (or a single portal) that uses premium features. If the user needs to run 3 premium apps, they need 3 Per App licences, or a Per User licence (which is more cost-effective at that point).
When to use Per App: The Per App plan is optimal when a specific app needs premium features but most users only need access to that one premium app. A warehouse management app used by 200 warehouse workers who use no other premium Power Apps costs $1,000/month on Per App vs $4,000/month on Per User. The savings are dramatic when the user population is large but the premium app count per user is low (1-2 apps).
The Per User plan grants a single user the right to create and run unlimited Power Apps (canvas and model-driven) with full access to premium connectors, Dataverse, custom connectors, and on-premises data gateways.
When to use Per User: The Per User plan is optimal when a user needs access to 3 or more premium apps (at which point 3 x $5 = $15, approaching the $20 Per User threshold) or when the user is a power user who builds and runs multiple apps, uses Dataverse extensively, and connects to multiple premium data sources. IT departments, operations teams, and business analysts who use Power Apps as a core tool are typically Per User candidates.
The Per App vs Per User decision is a straightforward cost optimisation driven by the number of premium apps each user needs.
| Premium Apps Per User | Per App Cost | Per User Cost | Recommendation |
|---|---|---|---|
| 1-2 apps | $5-$10/user/month | $20/user/month | Per App is cheaper (50-75% savings) |
| 3 apps | $15/user/month | $20/user/month | Breakeven: Per User simpler to manage |
| 4+ apps | $20+/user/month | $20/user/month | Per User is cheaper and simpler |
The mixed model: The optimal approach for most enterprises is a mix of Per App and Per User licences. Power users (IT staff, operations analysts, citizen developers who build and run many apps) get Per User licences. Casual users (warehouse workers, field staff, retail employees who access 1-2 specific apps) get Per App licences. The segmentation mirrors the M365 E3/E5/F3 segmentation strategy: match the licence to the user's actual consumption pattern.
An enterprise has 500 Power Apps users. 50 power users need access to 5+ premium apps (Per User: 50 x $20 = $1,000/month). 450 casual users each access 1 specific premium app (Per App: 450 x $5 = $2,250/month). Total: $3,250/month. If the enterprise defaulted all 500 users to Per User: 500 x $20 = $10,000/month. The segmented approach saves $6,750/month ($81,000/year), a 67.5% reduction.
Dataverse is Microsoft's relational data platform that underpins model-driven apps, complex canvas apps, and the entire Power Platform data layer. It is also the licensing element that generates the most unexpected costs.
Dataverse capacity is measured in three dimensions: database capacity (structured data stored in Dataverse tables), file capacity (attachments, images, and files stored in Dataverse), and log capacity (audit logs, activity logs, and system logs). Each Power Apps licence contributes a capacity allocation to a tenant-wide pool.
| Licence Type | Database Capacity | File Capacity | Scope |
|---|---|---|---|
| M365 Seeded | ~1 GB | ~2 GB | Per tenant (shared, not per user) |
| Per App | 1 GB per licence | 250 MB per licence | Pooled at tenant level |
| Per User | 5 GB per licence | 2 GB per licence | Pooled at tenant level |
| D365 Base | 10 GB per tenant (base) | 20 GB per tenant (base) | Plus per-user increments by D365 type |
The capacity trap: The 1 GB tenant-wide Dataverse allocation from Microsoft 365 is sufficient for experimentation and simple apps with minimal data. The moment a production app stores meaningful data (thousands of records, file attachments, transaction history), the 1 GB is consumed. When the pool is exceeded, Microsoft charges for additional Dataverse capacity at approximately $40/GB/month for database and $2.40/GB/month for file storage. These overage charges accumulate quickly for data-intensive applications.
Managing Dataverse costs: The key is data architecture governance. Not every Power App needs Dataverse. Canvas apps that read and write to SharePoint lists, SQL Server databases, or Excel files do not consume Dataverse capacity (though they may require premium connectors if the data source is premium). Reserve Dataverse for apps that genuinely benefit from its capabilities: relational data modelling, row-level security, business rules, calculated fields, and integration with Dynamics 365 and model-driven apps.
Power Automate (Microsoft's workflow automation platform) is deeply intertwined with Power Apps licensing and is a frequent source of confusion.
What is NOT included: Standalone flows that run independently (scheduled automations, mailbox monitoring, processes not triggered by a Power App) require a separate Power Automate licence. Power Automate Per User (~$15/user/month) provides unlimited flows for the licensed user. Power Automate Per Flow (~$100/flow/month for 5 flows) licenses specific flows that can be used by unlimited users. The Per Flow model is optimal for organisation-wide automations (an approval workflow used by all employees) where licensing every user individually would be prohibitively expensive.
The boundary between "in the context of a Power App" and "standalone flow" is not always obvious. A flow triggered by a Power App button that then runs a complex multi-step automation touching multiple data sources: is that a Power App flow (covered) or a standalone automation (not covered)? Microsoft's guidance suggests the flow is covered if it is "in context of" the app, but enterprises should document the relationship between apps and flows to demonstrate compliance. For the broader Power Automate licensing analysis, see the Power Platform licensing strategy playbook.
Power Automate flows that use Robotic Process Automation (RPA) with desktop flows require a Power Automate Per User with Attended RPA licence (~$40/user/month) or an Unattended RPA add-on (~$150/bot/month). Premium connectors in flows follow the same rules as in Power Apps: flows using premium connectors require either a Power Automate Per User licence or a Per Flow licence. Flows built within Power Apps that use premium connectors are covered by the Power Apps licence, but standalone flows using premium connectors are not.
Power Apps' democratic appeal, "anyone can build an app", creates a governance challenge that directly affects licensing costs. Without governance, the following pattern repeats across every enterprise:
The ungoverned adoption trajectory: Month 1: A business user builds a useful app using M365 seeded entitlements and standard connectors. Cost: $0 incremental. Month 3: The app becomes popular, and the builder adds a SQL Server connection. Now every user needs premium licensing. Cost: $5-$20/user/month. Month 6: Other departments build similar apps, each connecting to premium data sources. 15 premium apps exist, used by 300 people. Cost: $1,500-$6,000/month. Month 12: Power Automate flows, Dataverse overages, RPA bots. Cost: $10,000-$25,000/month. Month 18: The CFO asks why the Power Platform line item went from zero to $300,000/year without a procurement decision.
Power Apps licensing purchased through the Enterprise Agreement benefits from volume pricing and bundling flexibility that standalone purchases cannot match.
Dynamics 365 licences include Power Apps use rights that extend beyond the M365 seeded entitlements, but the scope is specific and frequently misunderstood.
Dynamics 365 Enterprise licences (Sales Enterprise, Customer Service Enterprise, Finance, Supply Chain Management) include the right to create and run custom Power Apps that operate within the context of the Dynamics 365 application. This means canvas and model-driven apps that read from and write to Dynamics 365 (Dataverse) data, extend Dynamics 365 functionality, and are used by licensed D365 users are covered by the D365 licence. No separate Power Apps licence is needed for these users running these apps.
Power Apps that operate outside the Dynamics 365 context. An app built by a D365-licensed user that connects to an external SQL Server database for a non-D365 business process is not covered by the D365 licence and requires a separate Power Apps licence. Similarly, users who are not licensed for Dynamics 365 but need to run a Power App that accesses Dataverse data require their own Power Apps licence.
The practical implication: For enterprises with significant Dynamics 365 deployments, the D365 use rights can reduce the standalone Power Apps licence count substantially. Map which Power Apps operate within the D365 context (covered) and which operate independently (require standalone licences). This mapping prevents both under-licensing (running independent apps under D365 use rights) and over-licensing (purchasing standalone licences for apps already covered by D365). See Dynamics 365 licensing and renewals and common Dynamics 365 licensing mistakes.
Power Apps is the most deceptive licensing model in the Microsoft portfolio. Not because it is hidden. The pricing is published and the plans are documented. But because the journey from free to expensive is invisible. A business user builds an app. It works. Colleagues start using it. Someone adds a premium connector. Now 200 people need licences. Someone stores data in Dataverse. Now capacity charges apply. Someone builds a flow. Now Power Automate licensing enters the picture. Each step is individually reasonable. Cumulatively, the enterprise discovers a $200,000/year Power Platform spend that was never approved, never budgeted, and never governed. The fix is not to restrict Power Apps. The platform delivers genuine value. The fix is to govern it from day one: register premium apps, control environments, monitor capacity, and match licences to usage. Governed Power Apps is a productivity multiplier. Ungoverned Power Apps is a budget surprise.
A limited Power Apps entitlement is included in all Microsoft 365 plans. This seeded entitlement allows users to create and run canvas apps using standard connectors and Microsoft 365 data sources (SharePoint, Excel, OneDrive). However, apps that use premium connectors (SQL Server, Dataverse, HTTP, Azure services, Salesforce, SAP, and many others), model-driven apps, or apps that require full Dataverse need a separate standalone Power Apps licence (Per App at ~$5/user/app/month or Per User at ~$20/user/month).
Premium connectors are data source connections classified by Microsoft as premium, requiring a standalone Power Apps licence. Key premium connectors include SQL Server, Dataverse, HTTP/HTTP with Azure AD, Azure services (Blob Storage, Service Bus, etc.), Salesforce, SAP, ServiceNow, Oracle, and custom connectors using certain authentication types. The moment a Power App uses any premium connector, every user who runs that app needs a standalone licence, even if the rest of the app uses only standard connectors.
Use Per App ($5/user/app/month) when users access 1-2 premium apps. Use Per User ($20/user/month) when users access 4+ premium apps or are power users who build and run multiple apps. At 3 apps, the cost is similar ($15 Per App vs $20 Per User) and Per User is simpler to manage. The optimal approach for most enterprises is a mixed model: Per User for power users and Per App for casual users accessing specific apps.
Power Apps licences (Per App and Per User) include Power Automate use rights for flows that operate within the context of the licensed Power App. Standalone flows that run independently (scheduled automations, mailbox monitoring, processes not triggered by a Power App) require a separate Power Automate licence: Per User (~$15/user/month) or Per Flow (~$100/month for 5 flows). RPA (desktop flows) requires additional licensing.
Dataverse is Microsoft's relational data platform for the Power Platform. It provides structured data storage, row-level security, business rules, calculated fields, and integration with Dynamics 365. Model-driven apps require Dataverse. Canvas apps can use Dataverse but can also connect to SharePoint, SQL Server, Excel, or other data sources instead. You need Dataverse capacity when building model-driven apps or canvas apps that store data in Dataverse tables. Each Power Apps licence contributes capacity to a tenant-wide pool; overage is charged at ~$40/GB/month for database storage.
Not for Power Apps that operate within the Dynamics 365 context (apps that extend D365 functionality, read/write D365 Dataverse data, and are used by licensed D365 users). However, Power Apps that operate independently of Dynamics 365 (connecting to non-D365 data sources for non-D365 business processes) require separate Power Apps licences even for D365-licensed users. Map each app's context to determine whether the D365 use rights apply.