Power Apps Licensing: Per App vs Per User — The Decision That Costs Enterprises Millions

What Microsoft 365 Actually Covers — and Where the Compliance Line Is

Every enterprise assumes its Microsoft 365 licences cover Power Apps usage entirely. This assumption is both widespread and dangerous. Every M365 plan except F1 includes Power Apps Basic, which covers canvas apps connecting to a curated set of standard connectors: SharePoint, Teams, Outlook, OneDrive, and a limited roster of common data sources. The moment a user connects to a premium connector — Dataverse, Salesforce, SQL Server, SAP, ServiceNow, any Azure service, or a custom API — a premium Power Apps licence becomes mandatory.

This boundary is where most enterprise compliance failures begin. The trigger is not theoretical; it is auditable through Microsoft's telemetry data. Premium connector usage is logged at the service level. During a standard compliance audit, Microsoft's licensing team reviews these logs against your licensing inventory. When they find premium connector invocations without corresponding per-app or per-user premium Power Apps licences, the enterprise has a compliance gap.

The boundary extends further than many IT teams realise. Read-only access to premium data sources does not exempt users from premium licensing. If a user opens a canvas app that reads from a Dataverse table, accesses Salesforce records, or queries a SQL Server database, a premium licence is required. The access mode — read, write, or execute — is irrelevant. Observation alone triggers the requirement.

April 1, 2025 marked the hard enforcement date for premium connector licensing. Microsoft's grace period ended. Prior to this date, organisations could operate premium connectors in flows with looser compliance. Now, enforcement is immediate and automated. Any flow invoking a premium connector must have all users routed through that flow properly licensed, or the flow fails or is audited retroactively.

Dataverse, the common denominator in many Power Platform environments, creates a false sense of coverage. Every Power Platform tenant receives 1GB of Dataverse database storage and 2GB of file storage by default. This allocation is sufficient for trials and proof-of-concept applications. It is catastrophically insufficient for production multi-user applications. A single production app serving 100 users consuming even modest data volumes (order records, customer contact histories, project tracking) will exhaust this allocation within three to six months of launch.

Per App vs Per User — The Break-Even Math That Determines Your Budget

The pricing structure is deceptively simple but the deployment decision is complex. Per App licensing costs $5 per user per application per month. This price point is the right choice for organisations where users need exactly 1–3 specific applications and nothing more. Per User licensing costs $20 per user per month for standard environments, or $12 per user per month when purchased as part of an Enterprise Agreement with 2,000 or more seats.

The crossover point is critical: if a user needs 4 or more applications, Per User licensing is cheaper at the standard rate ($20/month covers unlimited apps versus 4 × $5 = $20). At the EA rate of $12/month, even 3 applications ($15 under Per App) makes Per User more economical. This mathematical inflection point is where most organisations make their first mistake: they provision Per App licences for power users who should be on Per User, or vice versa.

The Per App licence discontinuation timeline is now firm. As of January 2026, Microsoft is removing Per App licensing from the licensing guide for new non-EA and non-CSP (Cloud Solution Provider) customers. Existing customers can continue purchasing new Per App licences only through their EA agreements. MPSA (Microsoft Products and Services Agreement) customers have no renewal rights beyond their current agreement term. This sunset is critical context for any new licensing decision made in 2025 or 2026: if you commit to Per App, you are committing to a model that may not be available for renewal in two to three years.

Hybrid strategies exist and are often optimal. Position power users (those needing 5 or more applications) on Per User licensing. Position limited users (those needing 1–2 specific applications) on Per App licensing if you are an EA customer; otherwise, route them to Per User. Pay-as-you-go models remain available at $10 per user per application per month via Azure subscription, viable primarily for pilot programmes and seasonal or variable usage below 500 active monthly users.

The math changes when you layer in Dataverse and premium storage overages. Per App licences include 50MB of Dataverse database storage and 400MB of file storage per user. Per User licences include 250MB and 2GB respectively. For a production application with 50 users storing customer records, transaction logs, and file attachments, the Per App entitlement (50MB × 50 users = 2.5GB database) is consumed within the first quarter. Overages cost approximately $40 per GB per month for database and $2.40 per GB per month for file storage. That single overage can cost $40–$80/month per excess GB, rapidly inverting the cost-benefit of Per App licensing.

Premium Connectors and Dataverse — The Hidden Cost Vectors That Appear in Audits

Premium connector licensing is the single biggest source of unexpected Power Apps cost in enterprises. The mechanics are invisible to most IT organisations until the audit letter arrives. A developer in a line-of-business team builds a Power Automate flow connecting to Salesforce. The flow retrieves prospect records and updates them based on a trigger from Teams. Every user who invokes that flow requires a premium Power Apps licence. If IT provisioned those licences in advance, there is no gap. If IT did not anticipate the connector usage — which is common — the first audit uncovers the discrepancy.

Our advisory work has surfaced premium connector true-ups in the range of $200K–$500K annually in large EA environments. These charges arise from flows built without prior licensing planning, users routed through premium-connector flows without corresponding licences, and connector usage that escalated from proof-of-concept to production without a corresponding licensing adjustment. The audit triggers a true-up invoice covering 12–18 months of retroactive usage.

Dataverse is the second vector. Dataverse capacity overages are expensive and grow quickly. Per App licences include 50MB of database storage and 400MB of file storage per user. A production application with 100 users on Per App licences receives 5GB of combined Dataverse allocation (100 × 50MB). A typical CRM or operational database (customer records, transactions, attachments) exhausts this within 90 days. Overages at $40/GB/month for database storage and $2.40/GB/month for file storage accumulate rapidly. A 50GB overage in database storage alone costs $2,000 per month in direct overages, independent of licensing.

Shared account multiplexing is another vector that audits catch. Some organisations attempt to route multiple employees through a single licensed account to "share" a premium entitlement. This violates licence terms. Microsoft's telemetry flags concurrent access patterns, and audits identify this practice. The remediation is either full licensing for all users or removal of the accounts from the shared flow.

Embedded applications in Teams or SharePoint portals amplify the compliance risk. When a Power App is embedded in a Teams channel or SharePoint site, every member of that channel or site who accesses the app requires a licence. Many organisations miss this — they embed an app expecting only designated users to interact with it, but broad channel membership means broad licensing exposure. A single embedded app in a company-wide channel with 5,000 members creates a 5,000-seat licensing obligation. Audits identify these embedded instances and the licences required to cover them.

Negotiating Power Apps in an Enterprise Agreement Renewal — The Tactics That Unlock Discounts

Power Apps is often treated as a secondary priority in EA renewal conversations. Microsoft's internal sales teams focus on M365, Azure, and Dynamics — the high-revenue products. Power Platform receives tactical attention at best. This misalignment is buyer leverage.

The pricing structure in an EA is fixed: Per User licences at 2,000+ seats drop to $12/month (a 40% reduction from the $20 list price). But the discount is negotiable. Our experience in large enterprise renewals reveals that Power Apps commitments can be traded against better discounts on higher-value products. Here is the tactical approach:

First, audit your environment before renewal. Document the number of active applications, the user base touching each app, premium connector dependencies, and current Dataverse storage utilisation. An enterprise that enters renewal with clean data negotiates from strength. Without it, Microsoft's telemetry governs the conversation.

Second, understand Microsoft's fiscal calendar. Microsoft's fiscal year ends June 30 (not December 31, not May 31). Q4 of Microsoft FY — April through June — is the peak discount window. Renewals closed in this window receive better concessions than those outside it. If your EA renewal is due in March, April, or May, you have tactical timing advantage. Use it.

Third, quantify your Power Apps footprint and position it as a trade-off lever. If your organisation has 10,000 M365 seats and currently uses Power Apps across 3,000 of those seats, you have a significant lever. Frame it as: "We can commit to Per User Power Apps licences for 3,000 seats on a 3-year term, but we need better pricing on [higher-value product X]." Three-year commitments unlock better rates than annual. 3-year Per User commitments at 3,000 seats, when coupled with a broader EA concession, often attract 5–15% baseline discounts for mid-market enterprises and 30–40% discounts for large enterprises with 2,000+ seats and competitive pressure.

Fourth, address the Per App discontinuation. If your organisation currently uses Per App licences, the January 2026 discontinuation for new non-EA customers is now factual context. Use this to negotiate a three-year commitment at a fixed Per User rate, protecting your budget against future list-price increases. Microsoft prefers predictable multi-year commitments to annual renegotiations.

Fifth, document your Dataverse capacity requirements and negotiate capacity inclusions as part of your commitment. Standard Per User licences include 250MB database + 2GB file per user. If your applications require more (production CRM systems typically do), negotiate included overages or capped overage pricing as part of the EA. Capping overage rates at $30/GB database and $1.50/GB file (versus list rates) can save $100K+ annually if you operate large applications.

The negotiation timing and structure matter. Microsoft's sales teams operate on FY targets, creating incentive misalignment in Q3 (January–March). Closures in Q4 (April–June) attract better pricing. Position your renewal for maximum timing advantage. A three-year commitment closed in May locks in better rates than a one-year commitment closed in February.

Converting the Break-Even Analysis Into a Decision Framework

The decision framework is straightforward once you have the data. First, categorise your user base: power users (5+ applications), standard users (2–4 applications), and light users (1 application). For power users, Per User is always correct. For light users, Per App is correct if you are an EA customer; otherwise, Per User. For standard users, calculate the marginal cost: is the user closer to 2 or 4 apps? If closer to 4, move to Per User. If closer to 2, keep them on Per App.

Second, overlay Dataverse storage. For any application that is production and multi-user, add storage overage risk to the Per App cost. A 50MB/user allocation is tight for data-heavy applications. Most lose money on overages within six months.

Third, build in the premium connector risk. For every flow that uses a premium connector, ensure all upstream users are properly licensed. Embed this check into your flow approval process: before deploying a flow with a premium connector to production, verify that all users who will invoke it have premium licences assigned.

Fourth, schedule your EA renewal for Q4 (April–June) and prepare your commitment request three months in advance. Use the audit data and break-even analysis to make a confident ask: "We commit to X Per User seats at [target discount] on a 3-year term." Microsoft's sales teams respond to clear, quantified asks backed by data.

Finally, document your decision and communicate it across IT, finance, and line-of-business teams. Power Apps licensing is a distributed decision — developers, end users, and architects all make choices that affect your licensing posture. A documented policy prevents drift.