Microsoft's Power Platform has become the dominant low-code/no-code platform in enterprise IT. But the licensing model is among the most complex in the entire Microsoft ecosystem. Seeded entitlements bundled within M365 and D365 create an illusion of "free" access that evaporates the moment a user touches a premium connector or exceeds a usage threshold. This guide decodes Power Platform licensing within the EA, quantifies the most common over-spending patterns, and provides actionable strategies for reducing costs by 20 to 40% while maintaining full user access.
Power Platform licensing operates on two layers simultaneously. The first is seeded entitlements: limited capabilities included within M365 and D365 licences the organisation already owns. The second is standalone licensing: dedicated subscriptions that unlock full capabilities, premium connectors, and higher usage thresholds. The boundary between these two layers is where most organisations over-spend, either by purchasing standalone licences for users whose seeded entitlements are sufficient, or by failing to purchase standalone licences for users who have silently exceeded their seeded limits. The EA is the optimal vehicle for managing this complexity because it provides volume pricing, bundling opportunities, and negotiation leverage not available through CSP or MCA channels. For related guidance, see Power BI Licensing Guide, EA vs CSP Guide, and Microsoft EA Optimisation Service.
Power Platform licensing is uniquely challenging because it operates on two layers simultaneously. The first layer is seeded entitlements. The second layer is standalone licensing. Organisations that negotiate Power Platform as part of their broader EA strategy consistently achieve 20 to 40% lower costs than those that purchase Power Platform reactively.
| Product | What It Does | Seeded Access | Standalone Licensing |
|---|---|---|---|
| Power Apps | Low-code application development. Build custom apps connecting to organisational data sources (SharePoint, SQL Server, Dataverse, SAP, Salesforce, hundreds of connectors). | M365 includes basic apps using standard connectors and SharePoint data. | Required for premium connectors (Dataverse, SQL Server, HTTP, custom connectors), on-premises gateways. Per-app (~$5/user/app/month) or per-user (~$20/user/month for unlimited apps). |
| Power Automate | Workflow automation. Build automated flows connecting applications, synchronising data, automating processes. | M365 includes basic cloud flows with standard connectors. | Required for premium connectors, attended and unattended RPA, AI Builder, process mining. Per-user (~$15/month), per-user with RPA (~$40/month), unattended RPA (~$150/bot/month). |
| Power BI | Analytics and business intelligence. Operates independently but frequently bundled within EA negotiations. | Pro included in M365 E5. All other plans include Power BI Free only. | Pro (~$10/user/month), Premium Per User (~$20/user/month), Premium capacity (~$5,000+/month). See Power BI Licensing Guide. |
| Copilot Studio | AI agent and chatbot platform (formerly Power Virtual Agents). Build AI-powered conversational agents. | Limited access in certain M365 Copilot entitlements. | Based on messages consumed (~$200/month for 25,000 messages). Pricing still evolving, making EA negotiations the optimal time to lock in favourable rates. |
The single most important concept in Power Platform licensing is the distinction between seeded entitlements and standalone licences. Misunderstanding this boundary is the root cause of most Power Platform over-spending and under-licensing.
| Capability | Seeded in M365 | Seeded in D365 | Requires Standalone |
|---|---|---|---|
| Power Apps with standard connectors | Yes. Basic apps, SharePoint/Excel/Teams data. | Yes. Within D365 context. | Not required for basic scenarios. |
| Power Apps with premium connectors | No. | Yes. Within D365 context only. | Yes. Per-app or per-user plan. |
| Power Apps using Dataverse | No. | Yes. Limited capacity. | Yes. Per-app or per-user plan. |
| Power Apps with custom connectors | No. | Yes. Within D365 context only. | Yes. Per-app or per-user plan. |
| Power Apps with on-premises gateway | No. | No. | Yes. Per-app or per-user plan. |
| Power Automate cloud flows (standard) | Yes. Basic flows, limited runs. | Yes. Within D365 context. | Not required for basic scenarios. |
| Power Automate with premium connectors | No. | Yes. Within D365 context only. | Yes. Per-user plan. |
| Power Automate attended RPA | No. | No. | Yes. Per-user with attended RPA. |
| Power Automate unattended RPA | No. | No. | Yes. Unattended RPA add-on. |
| AI Builder credits | No. | Pooled capacity (limited). | Yes. Add-on capacity packs. |
| Copilot Studio messages | Limited in M365 Copilot. | Limited capacity. | Yes. Message packs. |
D365 licences include significantly broader Power Platform seeded entitlements than M365, but only within the context of extending the D365 application. A D365 Sales user can build a Power App that extends their sales workflow. But if the same user builds a Power App for an unrelated HR process, that app requires a standalone licence. The contextual boundary is poorly documented and frequently misunderstood, creating compliance risk. See M365 E3 vs E5 vs F3 Comparison for what each plan includes.
Premium connectors are the single largest source of unexpected Power Platform costs. Microsoft classifies data connectors into two categories: standard connectors (included in seeded entitlements) and premium connectors (requiring standalone licensing). The classification is not intuitive, and many connectors that organisations consider basic business requirements are classified as premium.
| Connector Category | Examples | Licensing Implication |
|---|---|---|
| Standard (included in M365) | SharePoint, Excel Online, Outlook 365, Microsoft Teams, OneDrive, Planner, To Do, Approvals, Office 365 Users, Notifications, limited third-party connectors (Twitter/X, RSS). | Any Power App or Power Automate flow using only standard connectors is covered by seeded M365 entitlement. No standalone licence required. |
| Premium (require standalone) | Dataverse, SQL Server, Azure SQL, Oracle Database, SAP, Salesforce, ServiceNow, HTTP (REST API calls), custom connectors, Azure Blob Storage, Azure Service Bus, Dynamics 365 (for non-D365 users), and hundreds of other enterprise data sources. | Any Power App or flow using even one premium connector requires every accessing user to have a standalone licence, even if 95% of the app uses standard connectors. |
A manufacturing company builds a Power App for 800 production floor workers to submit quality inspection reports. The app stores data in SharePoint (standard) and sends notifications via Teams (standard). A developer adds a feature that writes critical defects to SQL Server (premium connector). Suddenly, all 800 users require standalone licensing.
Without the SQL connector: zero additional cost, fully covered by M365 seeded entitlements.
With the SQL connector (per-user plan): 800 x $20/month = $16,000/month = $192,000/year.
With the SQL connector (per-app plan): 800 x $5/month = $4,000/month = $48,000/year.
The per-app plan saves $144,000 annually for this single-app scenario. Alternatively, rearchitecting the app to write to SharePoint and using a server-side process to sync to SQL eliminates the premium connector requirement entirely, reducing cost to zero. Architecture decisions directly determine licensing costs.
Power Apps standalone licensing offers two models with dramatically different cost profiles. Choosing the wrong model, or failing to negotiate the right model into the EA, is the second-largest source of Power Platform over-spending after premium connector miscalculation.
| Model | Cost | What You Get | Best For | EA Strategy |
|---|---|---|---|---|
| Per-User | ~$20/user/month. | One user gets access to unlimited Power Apps using premium connectors, Dataverse, custom connectors, on-premises gateways. | Power users accessing 4+ apps. Citizen developers, IT staff, department leads interacting with multiple Power Apps regularly. | Negotiate volume pricing for the smaller power-user population (typically 5 to 15% of Power Apps users). |
| Per-App | ~$5/user/app/month. | One user gets access to one specific Power App (or one portal) using premium connectors and Dataverse. | Users accessing 1 to 3 apps. Frontline workers, field technicians, single-app users. Saves 75% vs per-user for single-app deployments. | Negotiate volume pricing for the larger single-app population (typically 85 to 95% of users). 500+ per-app licences typically qualify for 10 to 25% EA discounts. |
The per-user plan breaks even versus per-app at four apps per user (4 x $5 = $20). Users accessing five or more apps are cheaper on per-user. Users accessing three or fewer are cheaper on per-app. Most organisations should negotiate both models into the EA: per-user for the smaller power-user population and per-app for the larger single-app population. Also negotiate conversion rights to adjust the mix during the EA term as usage patterns evolve. See Microsoft Contract Negotiation Service.
Power Automate licensing has expanded well beyond simple cloud flow automation. The platform now encompasses attended and unattended RPA, process mining, AI Builder integration, and process-based licensing. Each capability has its own licensing requirement.
| Licence Type | Cost | What It Covers | EA Negotiation Opportunity |
|---|---|---|---|
| Per-user (cloud flows) | ~$15/user/month. | One user creates and runs unlimited cloud flows using premium connectors. | Volume pricing for departments with heavy automation (finance, operations, HR). Typical EA discount: 10 to 20% on quantities exceeding 200 users. |
| Per-user with attended RPA | ~$40/user/month. | Adds attended desktop flows that automate legacy applications (screen scraping, form filling, data entry). | Bundle attended RPA users with cloud-only users for total volume pricing rather than purchasing each tier separately. |
| Unattended RPA add-on | ~$150/bot/month. | Desktop flows run without a user logged in. Each "bot" = one concurrent unattended run. | Highly negotiable at scale. Discounts of 20 to 35% achievable for 20+ bot commitments. |
| Process plan | Per flow/month. | Licences a specific automation for unlimited users. Suitable for org-wide automations (expense approvals, onboarding, compliance). | Evaluate whether process plans are cheaper than per-user for automations touching 500+ users. |
| Process mining | Add-on or included in certain tiers. | Analyses system logs to identify automation opportunities and inefficiencies. | Negotiate as part of overall Power Automate commitment. Bundling saves 15 to 25% vs standalone pricing. |
Beyond per-user and per-app licences, Power Platform generates capacity-based costs for Dataverse storage and AI Builder consumption that many organisations discover only after deployment. These capacity costs must be addressed in the EA to prevent budget overruns.
| Capacity Type | What It Is | Included Allocation | Overage Cost | EA Strategy |
|---|---|---|---|---|
| Dataverse: Database | Relational data in Dataverse tables. | Typically 250 MB per user licence (pooled). | ~$40/GB/month at list price. | Negotiate pooled capacity across organisation. Volume-based pricing for larger commitments. Annual true-ups rather than monthly overages. |
| Dataverse: File | Attachments, images, documents. | Typically 2 GB per user licence (pooled). | ~$2.50/GB/month at list price. | Include file capacity in organisational pool. Organisations with document-heavy apps exhaust file capacity first. |
| Dataverse: Log | Audit logs, activity records. | Included in file allocation. | ~$2.50/GB/month at list price. | Organisations with extensive audit requirements should model log growth separately. |
| AI Builder credits | Pre-built and custom AI models (document processing, text classification, object detection, prediction, sentiment analysis). | Base allocation with certain licences. | ~$500/month per 1 million credits. | Negotiate credit pools at committed-volume rates. High-volume document processing can exhaust base allocations quickly. |
Dataverse storage and AI Builder credits should be negotiated as part of the overall EA rather than purchased as reactive add-ons. Within the EA, negotiate pooled capacity across the organisation, volume-based pricing for larger commitments, and annual capacity true-ups rather than monthly overages (which carry premium pricing). Organisations that negotiate proactively typically pay 25 to 40% less per GB and per credit than those purchasing add-on packs after deployment. See Power BI Licensing Guide for related capacity planning.
The EA renewal is the single most important moment for Power Platform cost optimisation. Microsoft's standard pricing applies to individual purchases. EA-level bundling, volume commitments, and cross-product negotiation create pricing advantages not available through any other channel.
| Strategy | What to Do | Expected Savings |
|---|---|---|
| 1. Bundle with M365 and D365 | Never negotiate Power Platform in isolation. Use the M365 and D365 spend as leverage. "We will commit to E5 for 3,000 users, but Power Platform per-app pricing must be discounted 25% as part of the package." Microsoft account teams are authorised to offer deeper Power Platform discounts when tied to larger EA commitments. | 15 to 30% deeper discounts through cross-product leverage. |
| 2. Right-size per-user vs per-app mix | Analyse actual usage before negotiation. Identify power users (per-user candidates) vs single-app users (per-app candidates). Present Microsoft with a data-backed licence mix. This reduces the account team's ability to push higher-cost per-user licences for users who only need per-app. | Up to 75% savings on single-app user segments. |
| 3. Negotiate capacity pools | Instead of purchasing Dataverse storage and AI Builder credits as individual add-ons at list price, negotiate organisational capacity pools within the EA. Request pooled Dataverse capacity, annual commitments with reduced rates, and automatic alerts rather than immediate overage charges. | 25 to 40% less per GB and per credit vs add-on pricing. |
| 4. Lock in emerging product pricing | Copilot Studio, AI Builder, and emerging capabilities are in a pricing discovery phase. EA negotiations now can lock in favourable pricing before Microsoft standardises higher price points. Negotiate multi-year fixed pricing on message packs and credit pools. | 15 to 30% better pricing vs waiting for GA pricing. |
| 5. Include flexibility clauses | Negotiate the right to increase quantities mid-term at EA price (not list), convert between per-user and per-app at annual true-up, step-down provisions if adoption falls short, and reallocation rights across business units without Microsoft approval. | Protects against both over-commitment and under-commitment scenarios. |
| Mistake | What Happens | Cost Impact | Prevention |
|---|---|---|---|
| Per-user licences for single-app users | 300 users need one quality management app. IT provisions 300 per-user licences at $20/month instead of 300 per-app licences at $5/month. | $72,000/year instead of $18,000/year. $54,000/year wasted. | Segment users by app count before purchasing. Per-user is only justified when users access 4+ apps. |
| Ignoring seeded entitlements | Standalone licences purchased for users whose requirements are fully covered by M365 seeded access (standard connectors only). | 20 to 35% of "required" standalone licences are typically unnecessary. | Verify each app actually uses a premium connector before purchasing standalone licences. |
| No Dataverse capacity planning | Per-user and per-app quantities negotiated without modelling Dataverse storage. Six months later, capacity is exhausted. Additional storage purchased at list price. | 40 to 60% premium vs EA-negotiated rates. | Model Dataverse growth during EA negotiation. Include capacity pools in the agreement. |
| No governance over citizen development | Citizen developers build apps and flows using premium connectors without awareness of licensing implications. Hundreds of premium-connector apps created by users who assumed M365 covered everything. | Budget shock at EA renewal during licensing true-up. | Implement Power Platform CoE with DLP policies that block premium connectors without licence pre-approval. |
| Siloed negotiation across business units | Finance buys 50 per-user, operations buys 200 per-app, HR buys 30 per-user, all at standard pricing. Volume thresholds missed. | 10 to 25% higher cost vs consolidated EA commitment. | Centralise all Power Platform requirements into the EA negotiation. |
| Confusing D365 seeded rights with universal access | D365 users build Power Apps for unrelated business processes. Compliance exposure when audit reveals apps operating outside D365 context. | Standalone licences required for every out-of-context user. | Educate D365 users that seeded rights apply only within D365 application context. See MCA Explained. |
Effective governance prevents the uncontrolled licence sprawl that makes Power Platform one of the fastest-growing and most unpredictable cost centres in Microsoft estates.
| Governance Mechanism | How It Works | Licensing Impact |
|---|---|---|
| DLP policies for connector control | Use Power Platform admin centre to create Data Loss Prevention policies that classify connectors into "business," "non-business," and "blocked" groups. Block premium connectors by default in the default environment. Create dedicated environments with premium connectors enabled only for users with confirmed standalone licences. | Prevents accidental premium connector usage that triggers licensing obligations for entire user populations. |
| Environment strategy | Create separate environments for seeded-only usage (standard connectors, M365 data) and standalone-licensed usage (premium connectors, Dataverse). Users in the seeded environment need no standalone licence. Users in the premium environment are confirmed licence holders. | Clear licence assignment. Simplified compliance auditing and EA true-up reporting. |
| Usage monitoring and right-sizing | Deploy the Power Platform CoE Starter Kit to monitor app usage, flow execution, connector utilisation, and user activity. Use for quarterly licence reviews: identify users with standalone licences who have not accessed premium apps in 90+ days. | Typical organisations reclaim 15 to 25% of standalone licences through regular monitoring. |
| Chargeback and demand management | Allocate Power Platform costs to consuming business units. When department leaders see per-user costs ($20/month) vs per-app ($5/month), they make informed tier decisions. Require licence requests to specify app, connectors, user count, and business justification. | Motivates business units to select appropriate tier and return unused licences proactively. |
| Checklist Item | What to Do |
|---|---|
| Inventory all Power Apps and flows | Catalogue every app and flow, including connectors each uses (standard vs premium), user count, and whether users are on seeded or standalone licences. This reveals the actual licensing requirement, not the assumed requirement. |
| Segment users by licence need | Classify every user as seeded-only (standard connectors), per-app (1 to 2 premium-connector apps), or per-user (3+ premium-connector apps). This determines the optimal licence mix for the EA. |
| Model Dataverse capacity | Calculate current usage (database, file, log) and project growth over the 3-year EA term. Include capacity pools in the negotiation at pre-agreed rates. |
| Assess AI Builder and Copilot Studio | Determine current and projected consumption. Negotiate capacity pools at committed-volume pricing. |
| Cross-reference M365 and D365 entitlements | Identify users whose needs are covered by M365 E5 (Power BI Pro included) or D365 (seeded premium within D365 context). Eliminate duplicate standalone purchases. |
| Negotiate flexibility provisions | Secure per-user/per-app conversion rights, mid-term additions at EA price, and cross-BU capacity reallocation. |
| Benchmark pricing | Compare proposed EA pricing against list prices and market intelligence. EA-negotiated Power Platform pricing should be 15 to 30% below list for volume commitments. See EA Optimisation Service. |
Power Platform licensing sits at the intersection of M365 plan strategy, D365 entitlements, capacity planning, citizen development governance, and EA negotiation. Independent advisory provides the cross-domain expertise needed to optimise all dimensions simultaneously.
| Advisory Value | What We Deliver |
|---|---|
| Licensing assessment and mix optimisation | Comprehensive Power Platform assessment: connector classification (standard vs premium) for every app and flow, user segmentation (seeded vs per-app vs per-user), Dataverse and AI Builder capacity modelling, D365 seeded entitlement verification. Assessments typically identify 20 to 40% savings by reclassifying users from per-user to per-app, eliminating standalone licences where seeded entitlements suffice, and consolidating capacity purchases. |
| EA negotiation support | Power Platform-specific negotiation intelligence: market pricing benchmarks, volume discount thresholds, bundling strategies linking Power Platform to M365 and D365 commitments, flexibility clause language. Consistently achieves 15 to 30% below-list-price outcomes while securing conversion rights and capacity provisions. |
| Complete vendor independence | No Microsoft partnership, no CSP resale revenue, no incentive to recommend specific tiers or adoption levels. Recommendations based exclusively on the organisation's requirements and financial objectives. See Microsoft Advisory Services. |
Yes, but with significant limitations. Every M365 commercial plan (E1, E3, E5, F1, F3, Business) includes seeded Power Apps entitlements that allow users to create and use basic apps with standard connectors only (SharePoint, Excel, Teams, Outlook, OneDrive). The moment an app uses a premium connector (SQL Server, Dataverse, HTTP, custom connectors, SAP, Salesforce, or any on-premises data gateway), every user of that app requires a standalone Power Apps licence: either per-user (~$20/month for unlimited apps) or per-app (~$5/month for one specific app).
Per-user (~$20/user/month) grants one user access to unlimited Power Apps using premium connectors. Per-app (~$5/user/app/month) grants one user access to one specific Power App using premium connectors. The break-even is four apps: users accessing four or more premium-connector apps are cheaper on per-user; users accessing three or fewer are cheaper on per-app. Most Power Platform users access only one or two apps, making per-app the more cost-effective choice for the majority. The optimal strategy is a mix: per-user for power users and citizen developers, per-app for single-app users.
Premium connectors are data connectors classified by Microsoft as requiring standalone Power Platform licensing. They include Dataverse, SQL Server, Azure SQL, Oracle, SAP, Salesforce, ServiceNow, HTTP (REST API calls), custom connectors, and hundreds of other enterprise data sources. If a Power App or Power Automate flow uses even one premium connector, every user of that app or flow requires a standalone licence, regardless of how many standard connectors the app also uses. This "one premium connector triggers full licensing" rule is the most common source of unexpected Power Platform costs.
Only for Power Platform usage outside the D365 application context. D365 licences include seeded Power Apps and Power Automate entitlements that allow users to build apps and flows that extend the D365 application using premium connectors, but only when connecting to Dataverse tables used by D365. If a D365 user builds a Power App for an unrelated business process (e.g. a facilities management app that does not connect to D365 data), that app requires a standalone licence. The contextual boundary is poorly documented and frequently misunderstood.
Bundle Power Platform with your M365 and D365 commitments for maximum leverage. Present Microsoft with a data-backed licence mix (per-user quantities for power users, per-app quantities for single-app populations). Negotiate volume discounts (typically 10 to 25% for commitments above 500 licences), Dataverse and AI Builder capacity pools at committed rates, flexibility provisions to convert between per-user and per-app during the EA term, and multi-year fixed pricing on emerging products like Copilot Studio. Power Platform pricing is more negotiable than M365 pricing because Microsoft is actively driving adoption.
Dataverse is the data platform underlying Power Apps, Power Automate, and Dynamics 365. It provides relational data storage, business logic, and security. Each standalone licence includes a base allocation of Dataverse capacity (database, file, and log storage). When organisational usage exceeds the pooled allocation, additional capacity must be purchased (~$40/GB/month for database). Yes, budget for Dataverse separately in your EA. Negotiate capacity pools at pre-agreed rates rather than purchasing add-on storage at list price after deployment.
Implement three governance mechanisms. First, use Data Loss Prevention (DLP) policies to block premium connectors in the default environment, requiring users to request access to premium-enabled environments where standalone licences are confirmed. Second, deploy the Power Platform CoE Starter Kit to monitor app creation, connector usage, and user activity across all environments. Third, implement a licence request workflow that requires business justification, connector specification, and cost centre approval before IT provisions standalone licences. These prevent the citizen-developer-driven premium connector proliferation that creates budget surprises at EA renewal.
Redress Compliance delivers independent Power Platform licensing advisory: connector classification, user segmentation, per-user vs per-app optimisation, Dataverse capacity planning, EA negotiation support, and governance framework design. We identify 20 to 40% savings through strategic EA bundling. Complete vendor independence. No Microsoft partnerships, no resale commissions.
Microsoft EA Optimisation ServiceIndependent Power Platform licensing advisory. Connector classification, user segmentation, EA negotiation support, and governance design. Fixed-fee engagements. No vendor conflicts.