Microsoft Power Platform — encompassing Power Apps, Power Automate, Power BI, Power Pages, and Power Virtual Agents (now Microsoft Copilot Studio) — has grown into a $3B+ annual revenue business for Microsoft. For enterprise IT and procurement teams, it has also grown into a significant and often poorly governed licensing exposure. The combination of seeded entitlements (basic capabilities included in M365 licences), standalone licence tiers, pay-as-you-go consumption pricing, and Dataverse capacity add-ons creates a licensing model where costs can compound silently until they surface at EA renewal time or, worse, in a Microsoft True-Up.
Power Apps Licensing: Per-User vs Per-App
Power Apps is available under two primary standalone licensing models. The Power Apps Premium (formerly "Per User") plan provides a single user with access to unlimited Power Apps canvas apps and model-driven apps, plus Dataverse capacity entitlements. At list price, this is approximately $20/user/month. The Power Apps Per App plan provides a single user with access to a single Power App or portal, at approximately $5/user/month (or a block of 5 app passes for $150/month).
The seeded entitlement — the Power Apps capability included within M365 E3 and E5, and most other M365 plans — allows users to run canvas apps that connect to SharePoint, Teams, Excel, and other Microsoft 365 data sources without any additional licence. However, as soon as an app connects to a premium connector (Dataverse, Dynamics 365, non-Microsoft APIs with premium connectors, or certain Azure services), all users of that app require a Power Apps Premium or Per App licence. This premium connector trigger is the single most common source of unexpected Power Apps licence expansion in enterprise environments.
The Seeded Licence Trap: An enterprise's Power Platform champion builds a business process app on SharePoint data (seeded, free). The app becomes popular. Someone adds a Dataverse table for better performance. Instantly, all 500 users of the app need Power Apps Premium licences. At $20/user/month, that is $120K/year added to the Microsoft bill — discovered at True-Up. We see this pattern in the majority of enterprises with active Power Platform adoption.
Power Apps Per-User vs Per-App: The Break-Even
The Per-App model is economically superior when users need access to 1–3 apps. Beyond 4 apps, the Premium per-user plan becomes more cost-effective. Most enterprise governance frameworks use Per App licences for targeted departmental deployments and Premium licences for Power Platform developers or power users who build and run many applications. The key is establishing clear segmentation criteria before Microsoft's sales team pre-populates your EA renewal with Premium licences across your full M365 user population.
Power Automate Licensing
Power Automate (formerly Microsoft Flow) follows a similar pattern to Power Apps. The seeded entitlement in M365 provides basic automation running against Microsoft 365 data sources. The moment a flow accesses a premium connector — including Dataverse, SQL Server (direct connector), most third-party APIs, or runs attended/unattended robotic process automation (RPA) — additional licences are required.
Power Automate Premium (formerly "Per User") provides unlimited flow execution with premium connectors at approximately $15/user/month. Power Automate Process (formerly "Per Flow") provides an unlimited-user, unlimited-run licence for a single flow at approximately $150/month/flow. For high-volume, shared business process flows (invoice processing, employee onboarding, procurement approvals), the Per Flow model often delivers significantly better economics than Per User licensing when the flow serves many users but is a single, identifiable process.
| Licence | Coverage | List Price | Best For |
|---|---|---|---|
| M365 Seeded | Standard connectors only | $0 (included in M365) | Basic M365-only automation |
| Power Automate Premium | All premium connectors | ~$15/user/mo | Individual power users |
| Power Automate Process | Single flow, unlimited users | ~$150/flow/mo | Shared business process flows |
| Power Automate RPA | Attended/Unattended RPA | ~$40–$150/user or bot | RPA/desktop automation |
Power BI Licensing
Power BI has three commercial tiers relevant to enterprises. Power BI Pro ($10/user/month) enables report creation, sharing, and collaboration on reports and dashboards. Power BI Premium Per User ($20/user/month) adds AI-powered features, larger dataset limits, paginated reports, and deployment pipelines. Power BI Premium Per Capacity (P1 starting at approximately $4,995/month) provides a dedicated capacity node that can serve unlimited Pro users for consumption of reports published to Premium workspaces.
Power BI Pro is included in Microsoft 365 E5 and is available as an add-on to E3. The capacity pricing model (Premium Per Capacity) becomes economically compelling when your organisation has more than 500 active Power BI consumers who only need to view reports (not create them) — at that scale, a P1 capacity plus a smaller set of Pro licences for report authors outperforms per-user Pro licensing. The Microsoft Fabric licensing model (which subsumes Power BI Premium) adds further complexity for organisations adopting the broader Fabric data platform.
Dataverse Capacity: The Hidden Cost Layer
Microsoft Dataverse — the underlying database service for model-driven Power Apps, Dynamics 365, and complex automation scenarios — uses a capacity-based pricing model that is separate from per-user licences. Every tenant receives a baseline Dataverse storage allocation (included with qualifying M365 and Power Platform licences), and usage beyond that allocation is charged per GB per month.
Dataverse capacity comes in three types: database capacity (storage for Dataverse tables and data), file capacity (attachments, images, and large objects), and log capacity (change history and audit logs). The list price for additional capacity is approximately $40/GB/month for database capacity — a figure that becomes significant at scale. Enterprises adopting Dataverse as a platform for business applications, rather than a lightweight forms-and-workflow tool, frequently encounter Dataverse capacity costs that were not modelled in their initial Power Platform business case.
Governance Requirement: Dataverse capacity is a shared tenant resource. Without governance controls on who can create Dataverse environments and which apps can write large datasets, capacity consumption can grow unpredictably. Power Platform Centre of Excellence (CoE) starter kit deployment — Microsoft's own governance framework — is strongly recommended before significant Dataverse adoption. Advisory firms including Redress Compliance include Power Platform governance framework design in their Microsoft EA advisory work.
Power Platform in Enterprise Agreements
Power Platform licences are increasingly appearing in EA renewals as "recommended" additions to M365 suites. Microsoft's sales motion often involves proposing Power Apps Premium across the full user population as a standard component of an "empowered workforce" vision. At $20/user/month across 10,000 users, that is $2.4M per year for a capability that most of those users will never actively use with premium connectors.
The correct enterprise procurement posture is to treat Power Platform as a consumption-driven, governed platform with licensing that grows in proportion to actual adoption — not a uniform per-user allocation applied to the full M365 population. This requires three things: a Power Platform Centre of Excellence to govern environment and connector usage, a clear segmentation model distinguishing makers (who need Premium or Per User licences) from consumers (who may need Per App licences) from casual users (who need only the seeded entitlement), and a contractual framework in the EA that allows right-sized scaling as adoption grows.
For the broader Microsoft EA negotiation framework within which Power Platform is typically discussed, see our Complete Microsoft EA Guide. Our SaaS License Optimization practice covers Power Platform governance and licence right-sizing as part of Microsoft portfolio reviews. For context on how SaaS platforms beyond Microsoft handle similar metered licensing, our SAP BTP Licensing Guide provides useful cross-vendor comparison.
Practical Recommendations for Enterprise Power Platform Buyers
Before your next EA renewal, conduct a Power Platform licence audit: identify all users with Power Apps, Power Automate, and Power BI standalone licences; map those licences to actual app and flow usage; identify which flows and apps are using premium connectors; and quantify your Dataverse capacity utilisation against your paid allocation. In most enterprises, this exercise finds 30–50% licence redundancy — Pro licences for users who only consume reports, Premium licences for users who have never launched a Power App, and Per User licences for single-app use cases that Per App licences would cover at one-quarter of the cost.
The outcome of this audit becomes your negotiating position for the next EA cycle: you right-size the current commitment, establish governance to control organic growth, and negotiate a committed ramp structure that gives Microsoft predictable growth while giving you protection against runaway consumption costs. This is precisely the kind of structured commercial negotiation our Software Licensing Advisory practice delivers for Microsoft accounts with significant Power Platform exposure.