Microsoft Power Platform Licensing Deep Dive:
Power Apps, Automate, Power BI & Hidden Costs

Microsoft Power Platform Licensing: The Complexity Microsoft Doesn't Explain

Microsoft Power Platform licensing has become one of the most technically complex areas in enterprise M365 procurement. With four distinct products (Power Apps, Power Automate, Power BI, Power Pages), each carrying multiple licence models, per-app vs per-user choices, connector tiers, and premium add-ons, organisations routinely either overspend on unused capacity or unknowingly deploy unlicensed premium connectors. Microsoft's licensing guide for Power Platform runs to over 60 pages — and it changes at least twice a year. This guide distils the critical decision points for 2026.

The starting point for understanding Power Platform licensing is knowing what M365 plans already include at no additional cost. Microsoft 365 E1, E3, and E5 include Power Apps for Microsoft 365 (formerly Office 365) — a restricted tier that allows running apps built on Microsoft 365 data sources only (SharePoint, Teams, Exchange, OneDrive). This is adequate for internal productivity apps that do not connect to external systems. The moment an app connects to a premium connector — Salesforce, SAP, Dataverse, SQL Server, or any custom API — the user requires a paid Power Apps licence.

Power Apps Licensing: Per-User vs Per-App vs Pay-As-You-Go

Power Apps offers three paid licence models. Power Apps per-user ($20/user/month) grants unlimited app creation and usage for a single user across any apps, including premium connectors and Dataverse. Power Apps per-app ($5/user/app/month) allows a user to access one specific app with premium capabilities. Pay-as-you-go ($10 per active user/app/month, charged through Azure) works for apps with infrequent or unpredictable usage patterns. The per-app model is Microsoft's most aggressively sold option — but it is frequently the worst value for organisations with more than two or three premium apps per user population.

The breakeven calculation is straightforward: if any user accesses three or more premium apps, per-user ($20) is cheaper than per-app ($15). Organisations that started with per-app licences for a pilot deployment frequently find themselves with 10–15 apps in production and a licence cost three to four times what per-user would have cost. Microsoft's account teams rarely volunteer this analysis. Our Microsoft 365 E3 vs E5 comparison covers how E5 relates to Power Platform entitlements — important context if you're evaluating whether E5 justifies its premium over E3 for your organisation.

Power Automate: Premium Connectors, RPA, and the Per-Flow Trap

Power Automate (formerly Microsoft Flow) follows a similar structure. Microsoft 365 plans include Power Automate for Microsoft 365 — flows that use only standard connectors and Microsoft 365 data sources. Premium connectors require either Power Automate Premium ($15/user/month) or Power Automate Process ($150/bot/month for RPA attended and unattended). The "premium connector" category is broad: it includes SQL Server, SharePoint on-premises, Salesforce, SAP, Azure DevOps, and over 900 others. An IT team building automations that touch any on-premises or external system will immediately hit the premium tier requirement.

Power Automate RPA (Robotic Process Automation) — specifically, attended and unattended bots that automate UI-based processes — requires the Process licence at $150/bot/month. Unattended RPA, where bots run without human interaction, requires a hosted machine (additional cost) or the organisation's own Windows VM. Organisations comparing Power Automate RPA against UiPath, Automation Anywhere, or Blue Prism should conduct a proper TCO analysis: Power Automate RPA is cheaper at low scale but the per-bot cost model becomes expensive above 20–30 bots. Our Microsoft Intune licensing guide illustrates a comparable pattern — Microsoft's "included" offerings often cover 80% of requirements while the remaining 20% carries premium pricing disproportionate to its value.

Power BI Licensing: Pro, Premium Per User, and Premium Capacity

Power BI licensing operates on three tiers with fundamentally different delivery models. Power BI Pro ($10/user/month) allows an individual user to create and share content within the Pro tier — but both the creator and all consumers of shared dashboards must hold Pro licences. Power BI Premium Per User (PPU, $20/user/month) adds paginated reports, AI-powered insights, automatic aggregations, and larger dataset size limits. Power BI Premium Capacity (P-SKUs, starting at approximately $4,995/month for P1) allows sharing published reports with any licensed M365 user — including those without Pro or PPU licences.

The Premium Capacity economics only become favourable above approximately 500 report consumers. Below that threshold, per-user Pro or PPU is almost always cheaper. Above 500 consumers, Premium Capacity eliminates the need for the majority of users to hold individual Power BI licences, delivering significant per-user savings at scale. The most common Power BI overspend pattern: organisations purchasing PPU ($20/user) for users who only consume reports and would be fully served by Pro ($10/user) — or by Premium Capacity if the organisation is large enough. Download our Power Platform Sprawl Assessment for the framework our advisors use to audit Power BI licence assignments across enterprise tenants.

Dataverse Storage Costs: The Hidden Power Platform Expense

Dataverse (formerly Common Data Service) is the underlying database for Power Apps, Power Automate, and Dynamics 365. Every M365 tenant includes a base Dataverse storage allocation: 10GB database capacity plus 2GB file capacity per tenant, plus 250MB database and 2GB file per user for qualifying licences. The moment an organisation builds apps that store data in Dataverse beyond these allocations, additional storage is charged at $40/GB/month for database capacity and $2/GB/month for file capacity. At enterprise scale — where Dataverse tables accumulate years of transactional data — storage costs can exceed licence costs entirely.

The mitigation strategy is a combination of data archival policies (exporting aged records to Azure Data Lake at $0.023/GB/month), right-sizing Dataverse usage versus alternative data stores, and negotiating storage capacity commitments within EA pricing. Microsoft account teams routinely underestimate storage projections for new Dataverse deployments — this is not accidental. To understand how Microsoft Teams Rooms licensing and other M365 add-ons interact with your overall EA economics, our advisors model the full M365 cost stack rather than evaluating individual products in isolation. To book a Power Platform cost review, contact our team for a 48-hour analysis of your current tenant usage and licence optimisation opportunities.