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

What Is Microsoft Power Platform and Why Does Licensing Matter So Much?

Microsoft Power Platform is a suite of five low-code and no-code tools: Power Apps (custom application development), Power Automate (workflow and robotic process automation), Power BI (business intelligence and analytics), Power Pages (external-facing web portals), and Copilot Studio (AI agent and chatbot development). Together they form the primary vehicle through which Microsoft is expanding its footprint beyond the core productivity suite into operational business processes.

For licensing purposes, each of the five components has its own pricing model, its own entitlement boundary within Microsoft 365 subscriptions, and its own set of cost triggers. The complexity does not come from any single product being difficult to understand in isolation. It comes from the interaction between seeded entitlements in M365, premium connector triggers, Dataverse as a shared consumption resource, and the growing number of AI and automation capabilities that are now available only via paid add-ons or higher SKU tiers.

In our experience working with large enterprises across EMEA and North America, Power Platform has the fastest-growing licence cost exposure in the Microsoft portfolio. Organisations that deployed Power Apps and Power Automate under the assumption that their E3 or E5 subscriptions covered enterprise usage have been surprised — sometimes at True-Up — by six-figure licence adjustments. Understanding where the seeded entitlement ends and paid licensing begins is not optional. It is the foundation of every sound Power Platform deployment.

The Five Components and Their Licensing Frameworks

1. Power Apps: From Seeded to Premium

Power Apps allows business users and developers to build canvas apps, model-driven apps, and dataflows. The licensing model is structured around two fundamental tiers: the seeded entitlement included with Microsoft 365, and standalone paid licences for apps that exceed the seeded boundary.

Every user holding a Microsoft 365 E1, E3, or E5 licence — or equivalent Business tiers — has access to a version of Power Apps described as "Power Apps for Microsoft 365." This seeded tier allows users to run canvas apps that connect exclusively to Microsoft 365 data sources: SharePoint, Teams, Exchange, OneDrive, and a limited set of standard connectors. The critical restriction is that the moment an app connects to any premium connector, Dataverse, a custom connector, or an on-premises data gateway, every user of that app requires a standalone paid Power Apps licence.

The paid options as of 2026 are: Power Apps Premium at $20 per user per month, which grants a single user the right to run unlimited apps including those using premium connectors and Dataverse. The Per App plan ($5/user/app) was retired from new purchases on January 2, 2026, though Enterprise Agreement customers who already have the SKU can continue renewing, and CSP customers have an extended window to purchase and renew. Pay-as-you-go billing via Azure is available at $10 per active user per app per month for workloads with infrequent or unpredictable usage patterns.

The Per App retirement has a meaningful strategic implication for enterprise planning. Organisations that ran a handful of targeted apps under the Per App model and paid $5 per user per app now face a step-change to $20 per user for Premium if they want to expand. For organisations with many targeted single-app use cases, the Per App model was cost-effective. Microsoft's decision to retire it reflects its preference for the higher-value Premium SKU that drives Dataverse adoption.

2. Power Automate: Workflow, RPA, and Process Automation

Power Automate enables users to build automated workflows connecting Microsoft and third-party services. Like Power Apps, it has a seeded tier within M365 subscriptions that covers flows using only standard connectors and Microsoft 365 data sources. The moment a flow connects to a premium connector — SQL Server, Dataverse, HTTP actions, Azure services, Salesforce, SAP, ServiceNow, or any other premium-designated connector — the flow creator and, in many configurations, the flow users require a standalone licence.

Power Automate Premium, formerly called the Per User plan, costs approximately $15 per user per month and provides a single user with the ability to create and run unlimited cloud flows using premium connectors and attend RPA sessions. Power Automate Process, formerly Per Flow, costs approximately $150 per flow per month and licences a single flow for unlimited users and unlimited runs. For unattended RPA, the Process licence at $150 per bot per month is the required vehicle, with an optional Hosted Process add-on for Microsoft-managed infrastructure.

One consistently misunderstood area is the relationship between M365 E5 and Power Automate. E5 does not include premium connector access for Power Automate. The seeded entitlement ceiling in E5 is identical to that in E3 — standard connectors only. This is a common source of compliance exposure when E5 buyers assume the premium price tag extends to premium Power Automate capabilities.

3. Power BI: The Fabric Transition and Capacity Economics

Power BI has undergone the most significant licensing restructuring of any Power Platform component in recent years, culminating in the migration from the P-SKU capacity model to Microsoft Fabric F-SKUs.

The basic tier, Power BI Pro at $10 per user per month, allows individual users to create and share reports and dashboards through the Power BI service. Power BI Pro is included within Microsoft 365 E5, making it one of the genuinely valuable inclusions in the E5 SKU. For organisations on E3 or below, Pro must be purchased as a standalone add-on. Power BI Premium Per User (PPU) at $20 per user per month adds paginated reports, AI capabilities, advanced data modelling, and XMLA endpoint access, without requiring a tenant-level capacity licence.

The historic Power BI Premium P-SKUs — P1 through P5 at monthly capacity prices from approximately $4,995 to $81,000 — are being retired in favour of Microsoft Fabric F-SKUs. Fabric is Microsoft's unified analytics platform that extends beyond Power BI to encompass data engineering, data science, data warehousing, real-time intelligence, and integration workloads. Fabric F-SKUs run from F2 at approximately $263 per month to F2048 at over $260,000 per month, with the standard enterprise capacity equivalent of a P1 mapping roughly to F64 at approximately $4,995 per month.

The Fabric migration introduces a pause and resume capability that P-SKUs did not offer, meaning organisations can schedule capacity to run only during active usage hours — a significant cost optimisation lever for organisations with predictable reporting windows. Fabric also enables non-Power-BI workloads to run on the same capacity, potentially consolidating multiple licensing costs into a single Fabric SKU.

4. Power Pages: External Users and Portal Licensing

Power Pages, formerly Power Apps portals, enables organisations to build externally-facing websites connecting to Dataverse data. It is licensed differently from the core Power Apps user model because it serves external audiences — customers, partners, suppliers — who cannot be assumed to hold M365 licences.

Power Pages licensing is capacity-based and consumption-driven. Authenticated external users require a per-user licence at approximately $200 per 100 users per month or approximately $2 per user per month for higher volumes. Anonymous external users are licensed on a per-session basis, currently around $3 per 100 sessions per month. There is also a pay-as-you-go option via Azure for organisations with variable portal traffic.

The economics of Power Pages can become significant quickly for customer-facing deployments with large user populations or high anonymous traffic volumes. Internal portals for employees or contractors who already hold M365 licences are covered by the employee's Power Apps entitlement, which simplifies the model for inward-facing use cases.

5. Copilot Studio: The Session-Based AI Licensing Model

Copilot Studio is Microsoft's platform for building custom AI agents and chatbots. It allows organisations to extend Microsoft 365 Copilot with proprietary knowledge bases, connect agents to external data sources, and automate multi-step workflows via conversational AI. The licensing model for Copilot Studio is session-based and tenant-level.

A Copilot Studio licence at $200 per month provides the tenant with 25,000 Copilot credits, which is the new common currency for Copilot Studio interactions. Under the March 2026 licensing guide, message-based billing has transitioned to Copilot Credits to provide more flexibility across different capability types. The tenant-level model means a single Copilot Studio licence covers multiple agents and multiple users within that tenant, though heavy usage organisations will need to purchase additional credit packs.

For enterprises already paying for M365 Copilot at $30 per user per month — or for those who have moved to Microsoft 365 E7 where Copilot is bundled — Copilot Studio is the logical extension layer. However, the session consumption model requires careful governance to avoid unexpected cost escalation as internal chatbot adoption grows beyond pilot use cases.

The Seeded Entitlement Trap: Where Most Enterprise Exposure Originates

The single most common source of Power Platform compliance exposure in enterprise environments is the misunderstanding of what "included with Microsoft 365" actually means in practice. Microsoft's marketing emphasises that Power Apps and Power Automate are included in E3 and E5. This is technically accurate. The seeded entitlement is real. But its scope is defined by connector classification, and that classification can change — and frequently does — at Microsoft's discretion.

The seeded entitlement covers apps and flows that use standard connectors only. Standard connectors include SharePoint Online, Teams, Exchange, OneDrive for Business, Forms, Planner, and a subset of other Microsoft services. The full list of standard versus premium connectors is published in Microsoft's documentation and updated regularly. A connector that was standard one quarter may be reclassified as premium in a subsequent product update — and when that happens, every app or flow that relied on it as a seeded entitlement immediately requires standalone licensing for all its users.

The premium connector trigger is particularly dangerous in three scenarios that we see repeatedly in enterprise environments. The first is the Dataverse expansion: an app is built on SharePoint (seeded), performs well, and then a developer migrates data to Dataverse for better performance and relational capabilities. The instant the Dataverse connector is added, every user of the app requires Power Apps Premium. For a popular internal app with 500 users, that is $10,000 per month in immediate additional licence cost. The second is the integration scenario: a Power Automate flow connects to an internal system via a custom connector or HTTP action, both of which are premium. The flow creator and users all require Power Automate Premium. The third is the partner connector scenario: an organisation uses a third-party connector — Salesforce, ServiceNow, SAP, Workday — that is classified as premium. Any app or flow touching these systems is immediately outside the seeded entitlement.

Dataverse: The Storage Engine That Drives Cost Escalation

Dataverse is Microsoft's cloud-based relational database that serves as the data backbone for Power Apps model-driven apps, Dynamics 365, and many Power Platform integrations. Understanding the Dataverse cost model is essential because it is an additive cost on top of per-user licensing — and it operates as a shared tenant resource rather than a per-app allocation.

Every tenant with qualifying Power Platform or Dynamics 365 licences receives a base Dataverse allocation: 10 GB of database capacity plus 2 GB of file capacity at the tenant level, with additional per-user allocations of 250 MB database and 2 GB file capacity for each qualifying licence. Beyond the included allocation, additional Dataverse capacity is priced at approximately $40 per GB per month for database storage and $2 per GB per month for file storage.

The $40 per GB database rate is substantial. A Dataverse environment that accumulates 100 GB of database data — not an unreasonable amount for an enterprise application with rich transactional records — adds $4,000 per month in storage costs on top of the per-user licence fees for the application's users. Without governance controls on which teams can create Dataverse environments and which applications can write large datasets, this cost can escalate rapidly and unpredictably.

Microsoft increased default Dataverse storage entitlements on December 1, 2025, with increases ranging from 39 to 200 percent for database and file capacity. This reduces the immediate overage risk for organisations that were operating close to their previous allocation, but does not eliminate the underlying management requirement. The correct approach is to deploy the Microsoft Power Platform Centre of Excellence starter kit — Microsoft's own governance framework — and implement environment lifecycle policies that control environment sprawl and monitor storage consumption before overages accumulate.

AI Builder Credits: A Time-Limited Inclusion

AI Builder is the Power Platform's machine learning capability layer, enabling makers to add intelligent features — form processing, object detection, prediction models, text classification — to Power Apps and Power Automate without data science expertise. It is currently included with certain Power Platform licences as a pool of complimentary credits allocated at the tenant level.

Microsoft has announced that complimentary AI Builder credits will be removed from all qualifying licences on November 1, 2026. Organisations that currently rely on AI Builder capabilities as part of their Power Platform deployments — and are not separately purchasing AI Builder capacity — need to plan for this transition. After November 2026, AI Builder usage will require a dedicated AI Builder credit purchase: available in prepaid packs or as a pay-as-you-go meter through Azure.

The implications vary by deployment. Organisations with light AI Builder usage — a few form-processing flows or a single prediction model — may find the cost of a base capacity pack manageable. Organisations that have built significant intelligent automation pipelines on top of the complimentary credit allowance face a more material cost increase. A consumption audit should be completed before the November 2026 deadline to size the actual credit requirement and negotiate appropriate capacity pricing.

The M365 SKU Stack and Its Power Platform Implications

The Power Platform licensing picture cannot be understood in isolation from the broader M365 SKU stack. Microsoft's current commercial tier progression is E1 → E3 → E5 → E7, with E7 representing the new top SKU positioned above E5. Microsoft field teams are actively driving E5 customers toward E7 at renewal, and the E7 value proposition centres heavily on AI, security, and Copilot capabilities.

From a Power Platform perspective, the key SKU boundaries are as follows. E1 includes the seeded Power Platform entitlements — standard connector apps and flows — at the same level as E3. E3 adds Dataverse usage rights for certain model-driven scenarios when combined with qualifying Dynamics 365 licences, but does not independently unlock premium connector access. E5 includes Power BI Pro, adds advanced analytics capabilities, and includes premium compliance and security features relevant to Purview and Dataverse data governance, but does not unlock Power Apps Premium or Power Automate Premium. E7, the new top tier, bundles M365 Copilot ($30/user/month standalone) directly into the SKU alongside advanced AI, security, and compliance capabilities. For organisations considering E7, the Copilot inclusion alone can justify the incremental price versus E5 at scale, and Copilot Studio integration becomes more cost-effective when the underlying M365 Copilot deployment is already established.

The practical implication for Power Platform buyers is that no M365 SKU — including E7 — eliminates the need for standalone Power Apps Premium, Power Automate Premium, or Power Pages licences. The E7 uplift reduces the incremental cost of M365 Copilot and Copilot Studio but does not change the premium connector licensing boundary for core Power Platform workloads.

EA Negotiation Strategy for Power Platform

Power Platform licences are typically included in Enterprise Agreement scope, and like all EA-covered online services, they are subject to the negotiation dynamics that define EA renewal windows. Understanding how to position Power Platform in an EA negotiation requires distinguishing between the commercial levers available and the structural changes Microsoft has made to its EA pricing architecture.

The most significant structural change affecting Power Platform negotiation is the elimination of volume tiers for online services from November 2025 onward. Under the legacy EA model, organisations above certain seat count thresholds received automatic level-based discounts (Level A through Level D). Those discounts are now gone for cloud services, meaning whether an organisation has 300 seats or 30,000, the starting price for online services is Level A list price. Large enterprises that previously sat at Level D and received 8–15% automatic discounts now need to negotiate those discounts explicitly as part of their EA terms.

For Power Platform specifically, the effective EA negotiation strategies in 2026 centre on four levers. First, commitment timing: Microsoft's fiscal year ends June 30, making Q4 (April through June) the highest-leverage window for buyers. Microsoft field reps have maximum incentive to close and discount in Q4, and organisations with EA renewals in this window should use that leverage aggressively. Second, portfolio bundling: committing to a broader set of Power Platform components in a single EA — combining Power Apps Premium, Power Automate Premium, and Copilot Studio — creates bundling negotiation leverage that individual SKU purchases do not. Third, 3-year commits: Power Platform licences on 3-year commits attract better discount rates than annual terms, though at the cost of flexibility if usage patterns change. Fourth, True-Up timing: organisations with True-Up dates approaching should conduct a consumption audit before the True-Up window to avoid paying for over-reported usage — and to ensure they can demonstrate licence efficiency rather than licence expansion.

EA standard discounts in 2026 run at 10–20% off list price. The historic discount range of 15–25% that characterised EA negotiations before Microsoft's cloud-first shift is no longer the baseline expectation. NCE (New Commerce Experience) annual commits offer up to 5% discount off list price; NCE monthly commits have no discount at all. The EA remains the most commercially favourable vehicle for large enterprise Power Platform deployments, and Microsoft's preference is to move buyers toward MCA (Microsoft Customer Agreement), where buyer leverage is structurally lower. Resisting the MCA migration and maintaining EA commercial protections is therefore a meaningful negotiation objective in its own right.

Governance: The Non-Licensing Dimension That Determines Licensing Outcomes

No Power Platform licensing strategy succeeds without a governance framework. The technical structure of Power Platform — where any licensed user with a Premium SKU can create environments, build flows, and deploy apps — means that licensing cost growth is closely correlated with governance maturity. Organisations that allow unrestricted environment creation and app development without lifecycle policies consistently see Dataverse storage overage, premium connector sprawl, and large True-Up adjustments that reflect actual usage rather than planned deployment.

The foundational governance layer is the Power Platform Centre of Excellence (CoE) starter kit, Microsoft's own toolkit for Power Platform governance. The CoE kit provides admin and maker portals, environment request workflows, app lifecycle tracking, and telemetry dashboards that give the IT function visibility over who is building what, which connectors are in use, and what the storage consumption trajectory looks like. Deploying the CoE starter kit before significant Power Platform adoption is the single most valuable governance investment available.

Beyond the CoE kit, effective governance requires clear policies on three dimensions: environment lifecycle (who can create new environments, how long they persist, what the archival and deletion process is), connector policy (which premium connectors are approved for use in governed production environments versus experimentation environments), and Dataverse data management (retention policies, storage quotas by environment, and review cycles for large datasets). Organisations that have implemented all three dimensions consistently achieve lower Power Platform per-user costs than those that have treated governance as a post-deployment problem.

Licence Audit: Finding the 30–50% Redundancy

In our experience across hundreds of Power Platform licence reviews, the average enterprise discovers 30–50% licence redundancy when it conducts a structured audit. The redundancy falls into predictable categories. Overly broad Premium allocation: Power Apps Premium licences assigned to users who have never launched an app beyond the seeded entitlement tier. This is the most common category and occurs when IT allocates Premium licences department-wide for a small-scale deployment to avoid compliance risk. Per-user versus Per-process mismatch: high-volume, low-user workflows that would be more cost-effective on the Process plan ($150/flow/month) are instead running on Premium user licences with 100 or more users assigned. Orphaned Power BI licences: Pro licences assigned to users who consume reports exclusively through embedded viewers or shared workspaces that are covered by a capacity licence, making their individual Pro licence redundant. Unmigrated Per App licences: legacy Per App assignments for use cases that are now served by a Premium licence the same user already holds.

The audit process itself requires read access to the Microsoft 365 Admin Center, Power Platform Admin Center, and Azure consumption telemetry for pay-as-you-go workloads. The Entra ID sign-in logs provide the most reliable usage signal — they distinguish between users who authenticated to a Power Platform service in the last 90 days and those who hold a licence without corresponding usage activity. The latter population is the primary target for licence right-sizing.

The 10 Power Platform Licensing Priorities for Enterprise Buyers

Drawing on 500-plus licensing engagements across enterprise Microsoft environments, these are the ten priorities every organisation should address when managing Power Platform licence spend.

1. Map every deployed app to its connector tier. Know which apps are operating within the seeded entitlement and which require Premium licences. Build and maintain a live connector inventory rather than relying on assumptions from deployment time.

2. Audit licence assignment against actual usage. Run a 90-day sign-in report from Entra ID before every True-Up to identify unused Premium, PPU, and Pro licences. Right-size before Microsoft counts.

3. Build Dataverse storage monitoring into your platform operations. Set alerts at 80% of included allocation in every environment. Storage overages at $40/GB/month accumulate faster than most teams expect.

4. Deploy the CoE starter kit before broad enablement. Governance infrastructure is harder to retrofit than to build from the start. The CoE kit is free and provides the visibility layer needed to manage costs at scale.

5. Evaluate Fabric F-SKUs against your Power BI Premium P-SKU at renewal. The pause and resume capability alone can reduce effective capacity costs by 30–40% for organisations with predictable analytics windows.

6. Plan for AI Builder credit removal by November 2026. Run a consumption audit of current AI Builder usage across all environments now to size the credit requirement before the complimentary allocation is removed.

7. Understand the Per App retirement implications for your roadmap. If you were planning to expand deployments under the Per App model, that option is now closed for new EA customers. Evaluate whether Pay-as-you-go via Azure is a viable alternative for targeted single-app scenarios.

8. Negotiate Power Platform as a portfolio in your EA, not as individual SKUs. Bundle Power Apps Premium, Power Automate Premium, and Copilot Studio commitments to create negotiation leverage. Piecemeal purchases leave discount potential on the table.

9. Resist MCA migration if your EA provides stronger commercial protections. Microsoft's preference is MCA. The EA's legacy commercial terms — particularly around price lock periods and True-Up mechanics — are often more favourable to buyers than MCA equivalents.

10. Use Q4 (April–June) as your primary negotiation window. Microsoft's fiscal year ends June 30. Field reps in Q4 have the highest incentive to close and discount. If your EA renewal does not fall in Q4, consider whether a restructured renewal date is worth negotiating as a commercial objective in its own right.

Conclusion: Power Platform Is a Strategic Licensing Relationship, Not a Line Item

Microsoft Power Platform has moved from an adjunct to the core M365 suite into a primary enterprise application platform in its own right. The five components — Power Apps, Power Automate, Power BI, Power Pages, and Copilot Studio — collectively represent one of the fastest-growing licence cost categories in enterprise software, and one of the areas with the greatest gap between what organisations believe they are paying for and what they are actually deployed and exposed against.

Getting Power Platform licensing right requires the same discipline applied to any complex enterprise software relationship: a structured inventory of what is deployed, a clear map of cost triggers and entitlement boundaries, a governance framework that prevents uncontrolled cost accumulation, and a procurement strategy that treats the portfolio as a negotiation object rather than a catalogue of individual transactions.

Redress Compliance operates exclusively on the buyer side. We do not have a vendor relationship with Microsoft. Our Power Platform licence optimisation service includes a full connector and entitlement audit, Dataverse storage analysis, Fabric migration modelling for Power BI deployments, AI Builder consumption baseline before the November 2026 credit removal, and EA negotiation support for the next renewal cycle. If your Power Platform estate has grown significantly in the last 18 months, a structured review before your next True-Up or renewal is the highest-return investment available in your Microsoft cost management programme.

In one engagement, a financial services firm with 8,000 Microsoft 365 E3 seats discovered that 1,200 employees had been assigned Power Apps Premium licences for a single internal app that connected only to SharePoint — within the seeded entitlement boundary. Redress reclassified the deployment correctly and removed the redundant licences. The annual saving was $288,000. The engagement fee was under 3% of the exposure.