Microsoft Power Platform Licence Sprawl: Uncontrolled Usage, Cost Drivers & Governance Control Strategy
Power Apps and Power Automate democratise app development and workflow automation — and create a licence sprawl problem that typically costs enterprises 40–60% more than budgeted. This paper maps the sprawl pattern, identifies the six licensing traps that accelerate costs, and provides a five-step governance framework that enterprises have used to recover control and reduce Power Platform spend.
Executive Summary
Microsoft Power Platform — Power Apps, Power Automate, Power BI, and Power Pages — is marketed as a democratised, low-code application development and automation environment. This narrative is commercially attractive: it promises that business users can build business-critical applications without IT overhead, and that automation can be embedded without expensive coding investment.
In practice, Power Platform licensing sprawl is the fastest-growing uncontrolled cost in the Microsoft M365 portfolio. Redress Compliance's Microsoft practice has reviewed 150+ enterprise Power Platform deployments and found that unmanaged Power Apps environments consistently deliver spending 40–60% above budget by month 18.
Month 1: Business users build their first Power App using M365 seeded entitlements at zero incremental cost. Month 6: Six power apps have grown to 40 apps, spanning engineering, finance, and operations. Premium connectors and Dataverse dependencies appear. Month 12: £18,000–28,000/month in Power Apps, Power Automate, and Power BI costs are locked into operations. By month 18, the deployment has grown organically to £25,000–40,000/month with zero governance, zero chargeback accountability, and three strategic apps considered too critical to interrupt.
This paper examines the true cost drivers of Power Platform sprawl, maps the six licensing traps that accelerate costs, and provides a proven five-step governance framework that has delivered 40–55% cost recovery at enterprises of 2,000–10,000 users.
What Power Platform Sprawl Looks Like
Power Platform sprawl is not immediately visible. Unlike M365 E5 licensing, which appears as a clear per-user cost, Power Platform costs accrue through a combination of per-user licenses, per-app overages, premium connector premiums, Dataverse storage, and automation action units. No single dashboard connects all these costs to actual business usage.
The Typical Sprawl Pattern
Phase 1: Proof of Concept (Month 0–3). A finance team or operations team discovers Power Apps. They build a simple three-table application that replaces a manual monthly reconciliation process. The app runs under M365 standard entitlements (Power Apps per user is included in M365 with limited connectors). Total incremental cost: £0. Perceived value: eliminates 20 hours of manual work per month.
Phase 2: Organic Expansion (Month 3–9). Word spreads. Engineering requests a form to capture field defect data. Operations requests an inventory tracker. Sales requests an opportunity management layer on top of Salesforce. Each app requires premium connectors (£5–15/user/month beyond standard), or requires Dataverse storage because standard connectors no longer meet requirements. Standard Power Apps per-user licenses become insufficient. The organisation upgrades 60–80 users to Power Apps Premium at £17/user/month. Dataverse storage rolls from 2GB to 8GB at £2.50/GB/month. Total incremental cost: £8,000–15,000/month.
Phase 3: Critical Dependency (Month 9–18). The original finance reconciliation app is now a critical daily process. The inventory tracker is feeding procurement decisions. The operations defect logger is feeding into SLAs. Removing these apps would break business processes. Meanwhile, Power Automate flows have proliferated (often free connectors, sometimes premium). Power BI dashboards are deployed (£9–15/user/month per-user or per-app). Dataverse usage is approaching governance limits. Users are requesting features that require mobile apps (Power Apps mobile licensing), which adds another cost layer. Total incremental cost: £25,000–40,000/month.
Cost Drivers: Why Sprawl Accelerates
Power Platform costs accelerate in three ways: per-user proliferation, connector premium cascades, and Dataverse storage runway. Each is defensible in isolation, but together they create exponential cost growth.
Cost Driver 1: Per-User License Proliferation
Power Apps per-user licensing costs £8–22/user/month depending on the tier and region. A team of 12 building apps requires different licensing than a team of 120 using those apps. Organisations typically address this by upgrading user populations rather than segmenting by app, resulting in 2–3x more licensed users than necessary.
Cost Driver 2: Premium Connector Premium
Standard connectors (SharePoint, Teams, Dataverse, Office 365) are available in base Power Apps licenses. Premium connectors (SQL Server, Salesforce, SAP, Oracle, ServiceNow) require either Power Apps Premium licenses or Power Automate premium action units. As apps grow, premium connector dependencies become unavoidable, and costs escalate £4–8 per licensed user per month.
Cost Driver 3: Dataverse Storage Runway
Dataverse provides structured data management for Power Apps and costs £2.50/GB/month. Organisations that start with 2–4GB often reach 8–16GB within 18 months through historical data retention, archive tables, and audit logging. This is a variable cost with no usage-based reduction mechanism.
| Cost Component | Per-User Cost | Typical Scale | Total Monthly Cost |
|---|---|---|---|
| Power Apps Per-User (Premium) | £17–22/user | 80 users | £1,360–1,760 |
| Power Automate (Premium connectors) | £6–12/user | 80 users | £480–960 |
| Dataverse Storage (GB/month) | £2.50/GB | 10 GB | £25 |
| Power BI (if deployed) | £9–15/user | 20 users | £180–300 |
| TOTAL (80 user estate) | £32–49 per user/month | 80 users | £2,000–3,000 |
Power Platform Licensing Models Explained
Microsoft Power Platform licensing changed substantially in 2026 and continues to be one of the most complex areas of the M365 portfolio. Understanding the differences between entitlements is critical for cost control.
Power Apps Licensing Tiers
Seeded Entitlements (Base M365): Microsoft 365 E3 and E5 users receive limited Power Apps capacity — 2,000 Power Apps runtime requests per user per month and access to standard connectors. No premium connectors, no Dataverse environment isolation, no per-app licensing.
Power Apps Per-User License (Premium): Approximately £17–22/user/month, enables unlimited Power Apps runtime requests, access to premium connectors, and per-app licensing within environments. This is the tier enterprises move to when standard seeded entitlements are exhausted.
Power Apps Per-App License (Retired in 2026): Previously available as a cheaper alternative (approximately £5–8/app/month), this SKU has been retired from new purchases in EA and CSP channels. Existing customers retain this option, but new deployments must move to per-user licensing.
Power Automate Licensing
Power Automate licensing is action-based rather than user-based. Standard connectors and certain premium connectors (Outlook, SharePoint) are included in base M365 E3 and E5. Flows using premium connectors (SQL, Salesforce, Oracle, SAP) require either per-user Power Automate Premium licenses or consumption-based pay-per-action billing. Organisations typically move to per-user licensing when premium connector flows exceed 50–100 per deployment.
The retirement of Power Apps Per-App licensing in 2026 is significant: organisations that were leveraging per-app licensing to manage costs for isolated applications must now move to per-user licensing, typically resulting in a 40–80% cost increase for that deployment segment. If your environment uses per-app licensing, you should model the per-user equivalent cost before your next EA renewal.
Six Licensing Traps That Inflate Costs
These six patterns appear repeatedly in enterprise Power Platform deployments reviewed by Redress Compliance:
60% of users need basic Power Apps access; 30% need premium connectors for occasional integration; 10% need continuous premium connector access. Organisations typically license all 100% at premium tiers to avoid managing mixed licenses, resulting in 30–40% overspend.
Dataverse grows through historical data retention, audit logs, and app testing tables that are never purged. Storage reaches 8–16GB within 18 months at £2.50/GB/month — a cost that could be halved through basic data retention policies.
SQL Server and Salesforce premium connectors are necessary. Many others (SharePoint, Teams, Dataverse) are available through standard connectors. Apps that could use standard connectors instead of premium are typically not refactored, resulting in unnecessary per-user licensing costs.
Organisations may have per-user licensed users running automated flows, while also purchasing per-action cloud flows for other automations. Consolidating on one model (typically per-user above 30 flows) reduces overhead costs.
The retirement of per-app licensing requires migration to per-user licensing. Many organisations complete this migration without modelling the cost impact, resulting in a 40–80% cost increase that appears on renewal invoices as a surprise.
Power BI per-user licenses cost £9–15/month. Many dashboard consumers only need read access, which can be provided more cost-effectively through Power BI Embedded or Power BI Premium capacity. Organisations often license users individually rather than evaluating capacity licensing.
Governance Framework: The 5-Step Control Strategy
Redress has deployed this five-step governance framework at 40+ enterprise clients, delivering 40–55% cost recovery while improving governance and reducing operational risk. The framework is designed to be implemented over 90–180 days alongside ongoing M365 operations.
Step 1: Environment and App Inventory (Days 0–30)
Establish a complete picture of Power Platform deployment: how many environments, how many apps per environment, which apps are in production vs. testing, which apps have active users, which apps are abandoned. This step typically involves exporting data from the Power Platform Admin Centre, querying Dataverse for unused apps, and interviewing app owners. Most enterprises discover 30–50% of apps are either abandoned, in testing, or have no active users.
Step 2: Cost Attribution and Chargeback Model (Days 30–60)
Build a chargeback model that attributes Power Platform licensing costs to business units, departments, or cost centres. Most organisations find that 20% of business units drive 80% of Power Platform spend. Once chargeback is transparent, cost awareness typically drives a 15–25% reduction in new app requests and feature expansion.
Step 3: Licensing Tier Optimisation (Days 60–90)
Segment users by actual licensing requirements. Identify which users need per-user premium licenses vs. which can operate on seeded entitlements plus case-by-case premium connector purchasing. Downgrade unnecessary premium licenses. This step typically recovers 20–35% of licensing costs.
Step 4: Dataverse and Storage Optimisation (Days 90–120)
Implement data retention policies, archive old transaction data, purge test and audit tables, and configure Dataverse compression where available. Organisations typically reduce Dataverse storage by 40–60%, recovering £400–1,200/month per 10GB of storage.
Step 5: Ongoing Governance and Monitoring (Days 120+)
Establish monthly governance reviews using the Power Platform Admin Centre Environment Governance Dashboard (introduced March 2026) to monitor app adoption, identify abandoned environments, and enforce policy compliance. Set cost thresholds that trigger alerts for cost overruns.
Governance Tools and Visibility
Microsoft has introduced significantly improved governance tools for Power Platform in 2026, with the Environment Governance Dashboard providing real-time monitoring of application usage, data connections, and performance metrics across all Power Platform environments.
Power Platform Admin Centre Enhancements (March 2026)
The new Environment Governance Dashboard provides:
- Real-time inventory of all Power Apps, Power Automate flows, and Dataverse environments
- Active usage metrics showing which applications have users and which are dormant
- Premium connector tracking and cost attribution
- Data connection and security conformance reporting
- Dataverse storage and consumption forecasting
Compliance Notifications (June 2026 onwards): Starting June 2026, users in Power Apps who are using Managed Environments without an appropriate license will receive notifications to help ensure licensing compliance. This will auto-enforce licensing correctness at the point of use.
Cost Management Integration
Power Platform costs are now visible in Azure Cost Management and Billing for E5 and EMS customers. This enables cost tracking at the app, environment, and department level using Azure's native cost management tools.
Case Study: Mid-Market Recovery
A UK-based services firm with 3,200 employees engaged Redress Compliance after discovering their Power Platform spend had grown from £4,000/month (budgeted) to £32,000/month (actual) in 18 months. The organisation had no visibility into which apps were being used, and no chargeback accountability for Power Platform costs.
Initial State
- 480 users licensed for Power Apps Premium (£17/user/month) = £8,160/month
- Power Automate premium action pack overage = £4,200/month
- Dataverse storage at 18GB (£2.50/GB/month) = £45/month
- Power BI per-user licenses (120 users) = £1,440/month
- Unattributed and unmeasured costs = £18,000/month (vendor miscalculation and usage creep)
- Total: £31,845/month (£382,140/year)
Redress Approach
Conducted a full environment audit using the Power Platform Admin Centre. Discovered that 380 of 480 premium-licensed users had not used Power Apps in 60+ days. Of 184 apps in the deployment, 67 were inactive or test apps with zero active users. Dataverse storage included 6GB of historical testing data. Implemented the five-step governance framework.
Outcome (120 Days)
- Downgraded 180 inactive users from Premium to seeded entitlements = £3,060/month saving
- Consolidated premium connectors to 80 users only = £2,040/month saving
- Reduced Dataverse to 7GB through archive policies = £27.50/month saving
- Moved 80 Power BI consumers to Embedded model = £560/month saving
- Corrected vendor billing errors and usage creep = £8,200/month saving
- New total: £17,917/month (£215,004/year)
- Net saving: £14,928/month, or £179,136/year (53% reduction)
The organisation also gained governance visibility through the new Environment Governance Dashboard, implemented a chargeback model to departments, and reduced app sprawl requests by 40% through cost transparency.
Implementation Roadmap
Export all Power Platform environments, apps, flows, and users from Power Platform Admin Centre. Map active users to licensing assignments. Identify inactive apps and test environments.
Create a chargeback model mapping Power Platform costs to business units. Model the cost impact of downgrading inactive users and consolidating premium connectors.
Execute user downgradings, consolidate premium connector licensing, and evaluate Power BI capacity licensing models. Communicate cost savings to business unit owners.
Implement data retention policies, archive historical data, purge test tables, and configure storage monitoring. Set monthly storage review processes.
Establish monthly Power Platform governance reviews using the Environment Governance Dashboard. Set cost thresholds and chargeback reporting. Review and approve new app requests against chargeback budgets.
About Redress Compliance
Redress Compliance is a Gartner-recognised, 100% buyer-side enterprise software licensing advisory firm. We have no commercial relationships with any software vendor — our only client is the enterprise buyer.
Our Microsoft licensing practice has completed 200+ Microsoft advisory engagements including Power Platform audits, governance implementations, and licensing strategy reviews across EMEA and North America. We typically engage to address uncontrolled Power Platform sprawl 9–12 months before license renewal, allowing sufficient time for governance implementation and cost recovery before contract renegotiation.
Microsoft Licensing Knowledge Hub · All White Papers · Enterprise Spend Navigator Newsletter