Why Power Platform Licensing Is More Complex Than It Appears
Microsoft retired Power Apps per-app licensing for new customers on January 2, 2026. If your organisation is still on per-app licences, migration to per-user is mandatory at renewal — and organisations with three or more apps per user will pay less on per-user than they did on per-app. That date is one of several changes that have made Power Platform licensing materially more expensive for organisations that have not reviewed their position since 2024. Across 500+ Power Platform licensing engagements, Redress Compliance finds a consistent 30–50% overspend driven by seeded licence misclassification, unplanned Dataverse consumption, and uncapped per-flow billing.
Power Platform now includes Power Apps, Power Automate, Power BI, Copilot Studio, and underlying Dataverse infrastructure. Each component operates on different pricing mechanics: per-user subscriptions, per-app models, per-flow licensing, per-session consumption, and capacity-based tiers. Worse, Microsoft's bundling with Microsoft 365 creates a false sense of coverage that trips up procurement and technical teams alike.
This guide walks you through the exact pricing structure, identifies which costs are most commonly underestimated, and shows you where negotiation leverage exists in 2026. We've worked with over 500 enterprise organizations on Power Platform licensing strategy. The patterns are consistent: early engagement with vendor negotiations, understanding seeded license limitations, and planning for Dataverse scale are the three highest-impact levers for cost control.
The Power Platform Licensing Stack — What Each Component Costs
Understanding each component's pricing is the foundation for any intelligent licensing strategy. These are not optional modules—most organizations need most of them. The key is matching usage patterns to the right licensing tier.
Power Apps: Per-User vs. Seeded M365 Rights
Power Apps per-user pricing is $20/month per user. This is the headline SKU. It grants one user unlimited access to all Power Apps your organization builds, as well as premium connector access and Dataverse capacity. A per-user license is appropriate when you have many makers and model-driven apps that require premium connectors like SAP, Salesforce, and SQL Server.
Power Apps also offers a per-app model at $5/user/app, but Microsoft retired this licensing option for new customers effective January 2, 2026. If you're still on per-app licensing, migration to per-user is now mandatory at renewal. Organizations with 3+ apps per user will find per-user dramatically more cost-effective. Many teams will actually spend less money on per-user than they did on per-app licensing once the calculation is done.
Here's the trap: Microsoft 365 E3 and E5 licenses include limited Power Apps rights at no additional cost. These are called "seeded licenses." The critical limitation is that seeded licenses do NOT include premium connectors. If your organization uses canvas apps that connect to Salesforce, Dynamics 365, SQL databases, or external SaaS platforms, you need paid Power Apps licenses, not seeded ones. Seeded licenses support only standard connectors like SharePoint, Teams, and Excel Online.
E3 users get the equivalent of Power Apps Essential licenses (capped at 2 apps per month creation limit). E5 users get more generous seeded rights. But neither includes premium connectors. If you have premium connector requirements, you need the paid Power Apps per-user license at $20/month regardless of M365 tier.
Power Automate: Premium vs. Process Tiers
Power Automate pricing split into two tracks in recent years. Power Automate Premium (formerly called Per User) costs approximately $15/user/month. This grants one user unlimited cloud flows, premium connectors, and desktop flows (RPA capabilities). Premium is appropriate for teams where many people need to build automation across a wide range of systems.
Power Automate Process (formerly Per Flow) costs approximately $150/flow/month and allows unlimited users to trigger the flow. A "flow" is a specific automation—for example, a workflow that approves purchase requests or syncs data between systems. The per-flow model works best when you have a small number of critical automations used by many people. One $150/flow license covers unlimited execution and unlimited users.
Most organizations undershooting cost modeling make this mistake: they assume their seeded M365 rights include Flow licensing. They do—but with severe limitations. Seeded cloud flows are limited to standard connectors and exclude desktop flows. Premium connector access requires paid Flow licenses. If your automation touches Salesforce, Workday, Oracle, or any external SaaS system, you need paid Flow licensing.
The per-flow vs. per-user decision hinges on two factors: (1) how many makers you have, and (2) which systems they need to automate. If you have 8 makers but only 3 critical automations connecting premium systems, per-flow ($450/month for three flows) will cost less than per-user ($120/month for 8 users). If you have 6 makers across 12 critical flows, per-user ($90/month) outperforms per-flow ($1,800/month).
Power BI: Pro, Premium Per User, and Premium Per Capacity
Power BI Pro licenses cost approximately $10/user/month. Each Pro user can create, publish, and share dashboards and reports. For organizations with fewer than 50 analytical users, Pro is typically the right fit. Total cost for 50 Pro users is roughly $500/month or $6,000/year.
Power BI Premium Per User (PPU) licenses cost approximately $20/user/month. PPU is positioned as a bridge product for organizations that outgrow Pro but don't want to commit to full capacity licensing. PPU includes unlimited paginated reports, better refresh rates, and higher compute capacity. The breakeven point is roughly 10-15 users: below that, Pro is cheaper; above that, premium becomes economical.
Power BI Premium Per Capacity starts at approximately $4,995/month for P1 capacity. Capacity licensing is designed for organizations with 300+ analytical users or extreme reporting complexity. Premium capacity gives you dedicated infrastructure, unlimited concurrent users, and advanced features like AI integration. Organizations with 500+ BI users typically find capacity licensing the most cost-effective.
A hidden cost within Power BI is premium capacity for larger deployments. If you commit to Power BI at scale without proper usage forecasting, you may find yourself paying for more capacity than you actually consume. Many organizations discover mid-contract that they overpurchased capacity and are locked in for 12 months.
"Power Platform licensing mistakes cost organizations 30-50% more annually than necessary. The biggest single error is assuming seeded M365 rights cover premium connectors. They never do."
Copilot Studio: Session-Based Pricing Model
Copilot Studio pricing is consumption-based and charged per session. Pricing starts at approximately $200/month for 25,000 sessions. A "session" is one interaction with a Copilot—a question asked, an answer received. This is fundamentally different from the per-user model used by other Power Platform components.
Copilot Studio is relatively new to the Power Platform lineup (released 2024) and pricing is still evolving. Organizations deploying customer-facing chatbots often underestimate session volume. A moderately popular chatbot handling 100 customer interactions per day generates 36,500 annual sessions. Budget roughly $200-400/month for light internal chatbot use, and $800-2,000+/month for high-volume customer-facing deployment.
The Seeded License Trap — What M365 Does and Doesn't Include
One of the most expensive licensing errors we encounter is overly optimistic interpretation of what M365 licenses include. Here's the exact breakdown for E3, E5, and E7.
M365 E3 seeded Power Platform rights: Each E3 license includes cloud flows and canvas apps with standard connectors only. No premium connectors. No Power BI. No Power Automate desktop flows. Limited to 2 Power Apps per month creation limit. No Dataverse capacity allocation.
M365 E5 seeded Power Platform rights: Each E5 license includes the same cloud flows and canvas apps, but with a higher creation rate (no monthly limit). E5 users get more generous Power BI rights—specifically, Power BI Pro is included for all E5 users at no additional cost. Premium Automate connectors are still not included. Dataverse capacity is still not included.
M365 E7 seeded Power Platform rights: E7 is the newest Microsoft 365 tier (released 2024) positioned above E5. E7 bundles AI capabilities previously sold as add-ons, including Microsoft Copilot at $30/user/month. E7 includes the same seeded Power Apps and Automate rights as E5, plus Power BI Pro for all users. Like E5, premium connectors require paid licensing.
The pattern is clear: Microsoft's "bundled" Power Platform access through M365 is deliberately limited to standard connectors. Any time your Power Apps or Power Automate touch Salesforce, Dynamics 365, SAP, Workday, SQL Server, Oracle, or any other external system, you need paid licensing. The seeded rights only work for internal, low-code scenarios using SharePoint, Teams, and Excel as data sources.
Dataverse: The Hidden Cost Layer
Dataverse is Microsoft's cloud database service that underpins much of Power Platform. It's also where many CIOs discover unexpected bills.
Dataverse capacity comes bundled with most Power Platform licenses at varying amounts. A Power Apps per-user license includes 1 GB of database storage. A Power Automate Premium license includes no Dataverse capacity. Dataverse storage beyond the bundled allocations costs approximately $1/GB/month. For organizations with large data platforms, this adds up quickly.
Here's the hidden cost: most Power Platform deployments grow beyond initial capacity estimates. A single Power Platform solution managing customer data, order processing, and operational metrics can easily require 50-100 GB within 18 months. At $1/GB/month, that's $600-1,200/month in Dataverse overage costs by year two. Many teams don't discover this cost until they've already committed users to the platform.
Dataverse file storage (for documents, attachments, etc.) is separate from database storage and is billed at roughly $0.50/GB/month. Large-scale document management workflows can trigger significant file storage bills on top of database charges.
Best practice: audit your Dataverse actual usage at 3, 6, and 12 months post-deployment. Organizations that treat this as a "set it and forget it" cost encounter budget surprises at renewal.
Choosing the Right Licensing Model: Decision Framework
Once you understand each component's pricing, the next step is matching your organizational requirements to the right licensing tier. This isn't a one-size-fits-all decision.
Per-User Scenarios
Choose per-user licensing when: (1) you have 5+ makers building Power Apps or Power Automate flows, (2) these makers need access to premium connectors, and (3) they're building across many different apps/flows. The per-user model gives them unlimited app and flow creation for one flat monthly fee.
For Power Automate specifically, per-user becomes attractive when you have distributed automation across the organization—different teams owning different flows. If your IT department owns all flows centrally, per-flow licensing may be cheaper.
Per-Flow or Per-App Scenarios
Choose per-flow or per-app licensing when you have a limited number of high-value automations or applications that are heavily used across the company. Examples: a critical order-to-cash flow used by 500 people, or a vendor management app used across procurement. One per-flow license covering unlimited users and unlimited triggers is more cost-effective than licensing 100+ users.
For Power Apps, remember that the per-app model is being retired. Migrations are mandatory at contract renewal. Per-user will likely become your only option.
Capacity Planning for Power BI
Power BI capacity planning is the most math-intensive Power Platform decision. Start by counting actual analytical users—people who need to view, not create, dashboards. If you have fewer than 10 analytical users, Power BI Pro is correct. Between 10-50 users, Pro is still appropriate but watch for complexity (paginated reports, advanced refresh needs). Between 50-300 users, evaluate Premium Per User. Above 300 users, premium capacity becomes cost-advantaged.
This math changes if you have many paginated reports or very high refresh frequency requirements. Those features drive earlier adoption of premium capacity.
Power Platform in the E3/E5/E7 Context
Power Platform licensing doesn't exist in isolation—it sits within the broader M365 buying decision. Organizations are currently deciding between E3, E5, and E7 tier, and those decisions impact Power Platform costs significantly.
E5 includes Power BI Pro for all users. E3 does not. If you have 500 users and are comparing E3 vs. E5, the E5 decision saves you 500 × $10/month = $5,000/month on Power BI alone if you would otherwise buy Pro licenses. E5 premium support, threat intelligence, and advanced security features add value beyond Power Platform, but BI is a real differentiator.
E7 is the new premium tier bundles AI capabilities that were previously sold as add-ons. Microsoft Copilot Pro costs $30/user/month when purchased standalone, but is included in E7 at no incremental cost. If you're evaluating E5 vs. E7, this is a meaningful cost comparison.
For most CIOs, the E3-to-E5 decision is driven by security and compliance requirements, not Power Platform. But if you're on E3 and deploying Power BI at scale, E5 becomes more economical. If you're on E5 and deploying Power Apps plus Power Automate across the organization, paid licensing (not seeded rights) is still mandatory if you need premium connectors.
Eight Common Power Platform Licensing Mistakes
Mistake 1: Assuming seeded M365 licenses cover premium connectors. They never do. Seeded Power Apps and Automate are limited to standard connectors. Any Salesforce, Dynamics, SAP, or external system integration requires paid licensing.
Mistake 2: Underestimating Dataverse storage requirements. Pilot implementations use 2-5 GB. Production systems consume 10x that. Budget for growth and monitor storage quarterly.
Mistake 3: Choosing per-flow licensing without calculating the flow count. Organizations with 15+ critical flows usually find per-user licensing cheaper. Model the math before committing.
Mistake 4: Mixing makers with insufficient Power Apps licensing. Your most productive teams need per-user licensing. Restricting them to seeded rights slows innovation and drives workarounds.
Mistake 5: Deploying Power BI Pro to everyone without usage analysis. Most organizations have 20-30% of their user base that truly needs BI access. Restrict Pro licensing to active users only.
Mistake 6: Buying Power BI Premium capacity without 12+ month forecasting. Capacity commitments are expensive and inflexible. Overprovisioning wastes budget. Underprovisioning creates performance complaints.
Mistake 7: Ignoring Copilot Studio's session-based pricing. A popular chatbot can generate 50,000+ sessions/month faster than expected. Monitor usage monthly.
Mistake 8: Treating Power Platform as free because M365 is already budgeted. Seeded rights are extremely limited. Most enterprise deployments require significant paid licensing investment.
Need clarity on your Power Platform licensing footprint?
Our licensing audits identify overspend and optimization opportunities specific to your deployment.
Get Started
EA Negotiation Strategy for Power Platform
Most organizations negotiate Power Platform licensing as an add-on to Microsoft 365 renewal. This is a strategic error. Power Platform deserves its own negotiation focus because discount structures are different and leverage windows are distinct.
Current Discount Reality
Historical EA discounts for Microsoft 365 were 15-25% depending on commitment level and organization size. Power Platform discounts have lagged behind. Current EA discounts for Power Platform range from 10-20%, with most medium-sized organizations landing in the 12-15% range.
This is lower than M365 discounts because Power Platform adoption is newer and Microsoft still has significant growth targets. As Power Platform matures, we expect discounts to converge with M365 levels, but that's not yet the case.
The 10-20% discount range is negotiable upward if you package Power Platform with a multi-year M365 commitment. Organizations committing 3+ years to M365 and bundling Power Platform licensing often secure 15-18% discounts on the Power Platform component.
Q4 Leverage Window
Microsoft's fiscal year runs October-September. Microsoft fiscal Q4 is April-June 2026—the current window. Q4 is the highest-leverage purchasing window because sales teams face year-end quota pressure and have maximum authority to discount. If you're planning a Power Platform license commitment, Q4 (now) is the window to negotiate.
Historically, Q4 discounts can be 2-3% better than other quarters. On a $500,000+ Power Platform commitment, that difference is meaningful. If your renewal falls in Q1-Q3, consider timing your purchase to fall in Q4 (April-June) if contract terms allow.
Bundling Power Platform with M365 Renewal
Your strongest negotiation position comes from packaging Power Platform growth with a broader M365 commitment. If you're negotiating M365 renewal and can simultaneously commit to 200 Power Apps per-user licenses and 100 Power Automate Premium licenses, you create a much larger deal size that justifies deeper discounts.
Vendors want to grow wallet share. Bundling demonstrates growth and gives them room to discount more aggressively than they would on Power Platform alone.
Seven Priority Recommendations for CIOs
1. Audit seeded license usage first. Before buying paid Power Apps or Automate licenses, inventory what your organization is actually building. Separate the apps/flows that use standard connectors only (eligible for seeded rights) from those requiring premium connectors (requiring paid licenses). You'll often find that 30-40% of your deployment uses seeded rights appropriately.
2. Forecast Dataverse storage at scale. Most pilots consume 5 GB. Most 12-month production implementations consume 40-80 GB. Build a 18-month Dataverse storage forecast into your licensing model. At $1/GB/month, 50 GB of overages costs $600/month by year two.
3. Centralize Power Platform governance. Organizations without strong governance often distribute licensing decisions to individual business units, leading to inefficient skew toward per-user licensing when per-flow would be cheaper. Establish a Power Platform steering committee to review licensing tiers quarterly.
4. Monitor premium connector usage. Many seeded licenses attempt to work with premium connectors and fail. Use usage analytics to identify failed connector attempts, then proactively license the users who need them. This prevents shadow IT workarounds.
5. Evaluate E5 vs. E3 based on Power BI inclusion. If you're deploying Power BI at scale (50+ users), E5's included Power BI Pro makes the tier shift from E3 economical on BI costs alone, independent of E5's security features.
6. Reserve M365 E7 budget for Copilot readiness. E7 is new and pricing may evolve. If your organization is considering E7, budget for it now but don't rush to migrate. Wait 6-12 months for pricing to stabilize and for your AI strategy to mature.
7. Negotiate Power Platform during M365 renewal, not separately. Power Platform licensing has lower discount ceilings than M365. Bundle them in a single negotiation to create a larger deal size and justify better terms.
Ready to optimize your Microsoft licensing?
Redress has guided 500+ organizations through Power Platform and M365 licensing strategy.
Microsoft Licensing Advisory
How Redress Compliance Helps
Redress Compliance has spent 15+ years analyzing Microsoft licensing for enterprise organizations. Our team has completed over 500 Power Platform licensing engagements and negotiated hundreds of millions in software agreements.
We help CIOs by: (1) auditing your current Power Platform deployment against optimal licensing, identifying overspend and under-licensing simultaneously; (2) modeling future-state licensing scenarios across different usage patterns so you can make informed purchasing decisions; (3) preparing negotiation strategy and positioning for vendor conversations, including market benchmarking and discount guidance; (4) managing contract language and compliance terms to prevent surprise true-ups at audit time.
Our approach is anchored in data: we review your usage logs, interview technical teams about planned deployments, and stress-test your licensing model against reasonable growth scenarios. The typical engagement identifies 25-45% cost optimization opportunities without sacrificing functionality.
In one engagement, a global manufacturing group had been paying for Power Apps per-user licences across 4,200 employees. An audit revealed that 2,800 of those users had only ever accessed canvas apps using standard connectors — no premium connectors, no Dataverse writes. Downgrading those users to seeded M365 E3 rights reduced annual Power Platform spend by $840,000. The engagement fee was under 5% of the first-year saving. For further Microsoft licensing resources, visit our Microsoft knowledge hub.
Start with a Microsoft EA advisory specialists engagement to understand your current footprint and optimisation potential. We'll provide a roadmap and pricing strategy specific to your organisation's Power Platform deployment.
FF
Fredrik Filipsson
Co-Founder, Redress Compliance
Fredrik Filipsson is a Co-Founder of Redress Compliance and a specialist in Microsoft Enterprise Agreement negotiation, EA True-Up strategy, and M365 licensing optimisation. He has led 200+ Microsoft EA engagements across EMEA and North America, working exclusively on the buyer side. Redress Compliance is Gartner recognised and has completed 500+ enterprise software licensing engagements.
Connect on LinkedIn →