The Power Platform Landscape in 2026
Microsoft’s Power Platform consists of five products that share a common data backbone (Dataverse) but carry entirely separate licensing structures. Understanding which product requires which licence — and where M365 entitlements end and standalone purchases begin — is the central challenge of Power Platform licensing.
The five products are: Power Apps (application building), Power Automate (workflow automation), Power BI (analytics and reporting), Power Pages (external-facing websites), and Copilot Studio (formerly Power Virtual Agents — AI chatbot building). Each has a seeded entitlement through certain M365 plans, a standalone licence tier, and a premium tier that unlocks advanced capabilities. The licensing complexity comes from the interactions between these tiers and the connectors, capacity, and AI credits they include.
“Power Platform licensing follows a consistent pattern: M365 gives you just enough to get started, premium connectors create a dependency on standalone licences, and Dataverse storage caps create ongoing capacity costs. Every escalation feels organic but is architecturally designed to move you from seeded rights to paid subscriptions.”
The Three Licensing Models
Before diving into each product, understand the three licensing models that recur across the platform. Every Power Platform product uses one or more of these.
Model 1: Per-User Licensing
The user pays a monthly subscription that grants unlimited use of the product within defined capability boundaries. This is the standard model for Power Apps, Power Automate, and Power BI. Per-user licences are straightforward for organisations where the same users build and consume apps, flows, and reports regularly. The trap: per-user licences become expensive when you need hundreds or thousands of users to access a single app or flow built by a small team.
Model 2: Per-App / Per-Flow Licensing
Instead of licensing every user, you license the specific app or flow. Users who access the licensed app or flow do not need their own per-user licence. This model is ideal for broadly deployed business applications (expense reporting, leave requests, HR onboarding) where hundreds of users interact with one or two apps. The economics cross over: per-app is cheaper than per-user when more than approximately 15–20 users access a single app, because the per-app licence costs $5/user/month versus the per-user licence at $20/user/month.
Model 3: Capacity-Based Licensing
Certain resources — Dataverse storage, AI Builder credits, Power Pages authenticated sessions, and Power Automate hosted RPA bot sessions — are metered by consumption rather than by user. These capacity entitlements come in pools allocated to the tenant, not to individual users. When usage exceeds the pooled entitlement, you purchase additional capacity packs. This is where Power Platform costs become unpredictable, because capacity consumption scales with adoption — the more successful your Power Platform deployment, the more capacity you need.
Power Apps Licensing
Power Apps Standalone Licence Options
Power Apps Premium: $20/user/month. Unlimited apps, premium and custom connectors, full Dataverse access, on-premises data gateway, AI Builder credits (500 per user/month), Copilot in Power Apps.
Power Apps per App: $5/user/app/month. Access to a single app with premium connectors and Dataverse. Each user needs one per-app licence for each app they access. A user accessing 3 apps needs 3 per-app licences ($15/month) — at which point Premium ($20) is more economical.
Power Apps per App Pay-As-You-Go: $10/active user/app/month. No upfront commitment. Billed through Azure based on actual monthly active users. Better for apps with variable or seasonal usage patterns.
M365 Seeded Entitlements for Power Apps
Most M365 plans include “seeded” Power Apps rights that allow users to create and run apps — but only with standard connectors and within M365 data sources (SharePoint, Exchange, Teams). The moment an app connects to Dataverse, an on-premises data source, a third-party system via premium connector, or uses any premium feature, every user running that app needs a standalone Power Apps licence.
| M365 Plan | Power Apps Seeded Rights | Standard Connectors | Premium Connectors | Dataverse |
|---|---|---|---|---|
| E1 / Business Basic | Run apps only | ✓ | ✗ | ✗ |
| E3 / Business Standard | Create and run apps | ✓ | ✗ | ✗ |
| E5 / Business Premium | Create and run apps | ✓ | ✗ | ✗ |
| F1 / F3 (Frontline) | Run apps only | ✓ | ✗ | ✗ |
The Premium-Connector Trap
Microsoft classifies over 700 connectors as “premium,” including many that enterprise apps routinely require: SQL Server, HTTP with Azure AD, Dataverse, SAP, Salesforce, ServiceNow, Adobe Sign, DocuSign, and virtually every third-party business system. An app that starts on SharePoint (standard) and adds a SQL Server connection (premium) instantly requires every user to upgrade from M365 seeded rights to a standalone licence.
This is not a theoretical risk. In our advisory practice, 60–80% of organisations building Power Apps hit the premium-connector wall within the first 6 months of adoption. The cost impact is significant: a 500-user expense-reporting app that connects to SQL Server requires $2,500/month in per-app licences or $10,000/month in per-user licences — for an app that “looked free” when it only connected to SharePoint.
Power Apps Decision Framework
Choosing between per-user and per-app licensing requires understanding your deployment pattern. If you have a small team of power users who build and use many apps daily, per-user at $20/month is the right model. If you have a single department-wide app used by hundreds, per-app at $5/user/app/month is dramatically cheaper. The crossover point: a user accessing 4+ apps should be on per-user; a user accessing 1–3 apps should be on per-app. Most enterprises need a hybrid approach — per-user licences for builders and heavy users, per-app for the broader population who interact with one or two deployed applications.
Power Automate Licensing
Power Automate Standalone Licence Options
Power Automate Premium: $15/user/month. Unlimited cloud flows with premium connectors, Dataverse access, AI Builder credits (5,000 per user/month), attended RPA (desktop flows), process mining, and Copilot in Power Automate.
Power Automate Process: $150/bot/month. Unattended RPA — a software bot that runs desktop flows without a logged-in user. Each Process licence provides one unattended bot that can run one flow at a time. Additional concurrent capacity requires additional Process licences.
Power Automate Hosted Process: $215/bot/month. Unattended RPA running on Microsoft-hosted virtual machines, eliminating the need for dedicated on-premise or Azure VM infrastructure for the bot.
M365 Seeded Entitlements for Power Automate
M365 E3/E5 and Business Standard/Premium include seeded Power Automate rights for cloud flows with standard connectors. The pattern mirrors Power Apps: the moment a flow uses a premium connector, Dataverse, an on-premises gateway, or desktop flows (RPA), every user running the flow needs a standalone licence. M365 seeded rights do not include desktop flows, process mining, or AI Builder — these are premium-only capabilities.
Critical distinction: Power Automate flows can be triggered by users (interactive) or by system events (automated). M365 seeded rights cover user-triggered flows with standard connectors. Automated flows that run on schedules or system triggers — the most valuable automation pattern in enterprise environments — require standalone licensing when they use premium connectors, because the flow runs in a “service context” that is not covered by M365 seeded rights.
The RPA Licence Escalation
Desktop flows (RPA) are Power Automate’s fastest-growing feature and its most expensive. Each attended RPA user needs Power Automate Premium ($15/month). Each unattended bot needs a Process licence ($150/month) or Hosted Process ($215/month). An enterprise deploying 10 unattended bots across finance, HR, and procurement is spending $1,500–$2,150/month on bot licences alone, before any user licences for attended flows.
The hidden cost: each unattended bot can only run one flow at a time. If you have 20 scheduled flows that need to run during a nightly processing window, you need enough Process licences to handle the concurrent peak, not just the total flow count. Organisations routinely underestimate concurrency requirements and discover queued flows during the first month of production deployment.
Power BI Licensing
Power BI Licence Options
Power BI Pro: $10/user/month (included in M365 E5). Create, publish, and share reports. Required for both creators and consumers who access shared reports in workspaces. The baseline for enterprise Power BI deployment.
Power BI Premium Per User (PPU): $20/user/month. Everything in Pro plus: AI features, paginated reports, larger dataset sizes (up to 400 GB), deployment pipelines, XMLA endpoint read/write, and faster refresh rates. Cost-effective for smaller teams that need premium capabilities without dedicated capacity.
Power BI Premium Per Capacity: Starting at $4,995/month (P1 SKU). Dedicated compute capacity for the entire organisation. Consumers who only view reports do not need Pro licences — they can access reports published to Premium capacity with a free Power BI licence. This is the inflection point for large-scale Power BI deployment.
Power BI Embedded: Azure-based capacity for embedding Power BI reports in external-facing applications. Priced through Azure consumption starting at approximately $735/month (A1 SKU). Users of the embedded application do not need Power BI licences.
The Pro vs Premium Decision
The Power BI licensing decision hinges on a single question: how many consumers will view reports without creating them? Under Pro licensing, every consumer needs a $10/month licence. Under Premium Per Capacity, consumers access reports for free (with a free Power BI account), and you pay a flat capacity fee regardless of consumer count.
The crossover point depends on the Premium tier. For the P1 SKU ($4,995/month), the crossover is approximately 500 consumers: if more than 500 users consume reports without creating them, Premium capacity is cheaper than licensing every consumer with Pro. For organisations with 2,000+ report consumers, Premium capacity saves $15,000–$20,000/month versus universal Pro licensing.
| Scenario | Pro Model | Premium P1 Model | Savings |
|---|---|---|---|
| 50 creators + 200 consumers | 250 × $10 = $2,500/mo | 50 × $10 + $4,995 = $5,495/mo | Pro wins by $2,995 |
| 50 creators + 500 consumers | 550 × $10 = $5,500/mo | 50 × $10 + $4,995 = $5,495/mo | Breakeven |
| 50 creators + 2,000 consumers | 2,050 × $10 = $20,500/mo | 50 × $10 + $4,995 = $5,495/mo | Premium saves $15,005 |
| 100 creators + 5,000 consumers | 5,100 × $10 = $51,000/mo | 100 × $10 + $4,995 = $5,995/mo | Premium saves $45,005 |
M365 E5 Already Includes Power BI Pro
If your organisation is on M365 E5, every E5 user already has Power BI Pro at no additional cost. Before purchasing standalone Pro licences, audit your E5 deployment. In many organisations, 50–70% of Power BI users are already on E5 and have unused Pro entitlements. The ROI of E5 for Power BI-heavy organisations is significantly better than E3 + standalone Pro licences for the same users. See M365 Licensing Cost 2026 for the full E3 vs E5 analysis.
Power Pages Licensing
Power Pages Licence Options
Authenticated Users: Starting at $200/website/month for 100 authenticated users. Additional authenticated users in packs of 100. Authenticated users log in with credentials (Azure AD, social login, local accounts) and access personalised content backed by Dataverse.
Anonymous Users: Starting at $75/website/month for 500,000 anonymous page views. Additional page view packs available. Anonymous users access public-facing content without login.
Pay-As-You-Go: Per-authenticated-user and per-page-view pricing billed through Azure for variable-traffic sites.
Power Pages (formerly Power Apps Portals) is the product most likely to generate unexpected licensing costs. A public-facing portal backed by Dataverse that starts with 100 authenticated users and grows to 5,000 moves from $200/month to several thousand per month in authenticated-user licences, plus Dataverse storage for the portal’s data. Factor authentication growth into portal planning — the licensing cost of a successful Power Pages deployment scales with user adoption, unlike traditional web hosting.
Dataverse interaction: Every authenticated page interaction reads from or writes to Dataverse. Power Pages includes a base Dataverse storage allocation, but high-traffic portals with complex data models consume this rapidly. Dataverse overage storage costs $40/GB/month for database capacity and $2.50/GB/month for file capacity. A portal with 10,000 authenticated users and rich data entry can generate 5–15 GB of Dataverse database growth per quarter.
Copilot Studio Licensing
Copilot Studio Licence Options
Copilot Studio: $200/tenant/month. Provides 25,000 messages per month across all chatbots in the tenant. A “message” is counted as any interaction that triggers a topic or generative answer. Additional message packs available at $100 per 25,000 messages.
Copilot Studio seeded in M365 Copilot: Organisations with M365 Copilot licences receive limited Copilot Studio capabilities for extending Copilot with custom actions and topics. Full standalone capabilities (autonomous agents, multi-channel deployment, generative AI orchestration) require the standalone Copilot Studio licence.
Copilot Studio has evolved dramatically from its Power Virtual Agents origins. In 2026, it functions as Microsoft’s low-code AI agent platform, capable of building autonomous agents that interact with enterprise data through Dataverse, SharePoint, and custom connectors. The licensing model has shifted from per-session to per-message, with the 25,000-message base allocation sufficient for most internal helpdesk or FAQ chatbots but rapidly consumed by customer-facing or high-volume agent deployments.
The cost escalation risk: a customer-facing chatbot deployed across a website, Teams, and email that handles 2,000 interactions per day consumes approximately 60,000 messages per month — requiring $200 base + $100 overage = $300/month minimum. Generative AI responses (GPT-powered answers from enterprise knowledge bases) consume messages faster because the orchestration pipeline counts intermediate steps. Plan for 1.5–3 messages per visible user interaction when using generative AI features.
Dataverse: The Hidden Cost Layer
Dataverse is Power Platform’s shared data backbone — the relational database that stores data for Power Apps, Power Automate, Power Pages, Copilot Studio, and Dynamics 365. Every standalone Power Platform licence includes a Dataverse storage entitlement, but the pooled model creates a capacity management challenge that many organisations discover only after deployment.
Base Entitlements
| Licence | Database (per user) | File (per user) | Log (per user) |
|---|---|---|---|
| Power Apps Premium | 250 MB | 2 GB | None |
| Power Apps per App | 50 MB | 400 MB | None |
| Power Automate Premium | 250 MB | 2 GB | None |
| Copilot Studio | 2 GB (tenant) | 10 GB (tenant) | None |
| Tenant Base | 10 GB | 20 GB | 2 GB |
The tenant receives a base allocation plus per-user increments from each standalone licence. For a 200-user Power Apps Premium deployment: 10 GB base + (200 × 250 MB) = 60 GB database capacity. This sounds generous until you deploy apps with file attachments, image fields, or audit trails — all of which consume database and file storage rapidly.
Dataverse Overage: $40/GB/Month for Database
When pooled Dataverse storage exceeds the entitlement, additional capacity costs $40/GB/month for database and $2.50/GB/month for file storage. The database rate is exceptionally expensive compared to Azure SQL Database ($4–$10/GB/month) or Azure Storage ($0.02/GB/month). Organisations with Dataverse-heavy deployments should monitor storage growth closely and consider archiving strategies to minimise overage.
Common capacity consumers: audit logging (which can grow 1–5 GB/month in active environments), file attachments stored in database tables rather than SharePoint, and Dataverse search indexing. Moving file storage to SharePoint (where M365 provides 1 TB+ per user) and implementing data retention policies can reduce Dataverse consumption by 40–60%.
AI Builder Credits: The New Capacity Currency
AI Builder is Power Platform’s integrated AI capability, providing document processing, text recognition, prediction, and object detection within Power Apps and Power Automate. AI Builder is licensed through credits that are consumed per operation, with different operations consuming different credit amounts.
Each Power Apps Premium or Power Automate Premium licence includes a credit allocation (500 and 5,000 per user/month respectively). Credits pool at the tenant level and are consumed by all AI Builder operations across the organisation. Additional credit packs are available at $500 per 1 million credits per month.
Credit consumption rates vary dramatically: a simple text recognition operation consumes 1 credit, while document processing (invoice extraction, receipt scanning) consumes 3–5 credits per page. An accounts payable automation processing 10,000 invoices per month (averaging 3 pages each) consumes approximately 90,000–150,000 credits. For a 50-user Power Automate Premium deployment with 250,000 pooled credits, this single workflow would consume 36–60% of the tenant’s AI Builder allocation.
The strategic consideration: AI Builder credits are the gateway to Power Platform’s AI capabilities, and Microsoft is rapidly expanding AI features across all five products. Credit consumption will increase as organisations adopt generative AI features in Copilot Studio, AI-powered app generation in Power Apps, and intelligent document processing in Power Automate. Build headroom into your AI Builder credit planning — the allocation that seems generous today will be consumed by features that do not exist yet but are on Microsoft’s roadmap.
Seeded vs Standalone: The Decision Matrix
The most critical licensing decision for most organisations is determining which users need standalone Power Platform licences versus which can operate within M365 seeded entitlements. The decision comes down to four questions:
Question 1: Does the app or flow use premium connectors? If yes, every user needs a standalone licence. There is no middle ground — M365 seeded rights do not cover premium connectors under any circumstances. Check the connector classification carefully; many connectors that seem basic (HTTP with Azure AD, SQL Server, Dataverse) are classified as premium.
Question 2: Does the app or flow access Dataverse? If yes, standalone licensing is required. M365 seeded rights allow only the use of standard connectors with M365 data sources (SharePoint, OneDrive, Exchange, Teams). Dataverse is explicitly a premium capability.
Question 3: Does the automation require desktop flows (RPA)? If yes, Power Automate Premium is required for attended RPA, and Process/Hosted Process licences for unattended bots. M365 seeded rights include zero RPA capability.
Question 4: Is the use case internal or external-facing? External-facing applications (customer portals, partner interfaces, public websites) require Power Pages licensing. No M365 plan includes external-user Power Platform rights. Dynamics 365 plans include some external-portal entitlements, but Power Pages standalone licensing is typically required for Power Platform-built portals.
The Optimal Licensing Architecture
For most enterprises with 200+ Power Platform users, the cost-optimised architecture combines:
Tier 1 — Builders (5–15% of users): Power Apps Premium + Power Automate Premium ($35/user/month combined). These users create apps and flows with premium connectors and Dataverse.
Tier 2 — Department users (15–30%): Power Apps per App ($5/user/app/month) for 1–3 apps. Access premium apps without per-user licence cost.
Tier 3 — Broad population (60–80%): M365 seeded rights only. Access apps built on standard connectors with SharePoint/Teams data sources. No additional licence cost.
This segmentation typically reduces Power Platform licensing cost by 40–55% versus blanket per-user licensing for all users.
Power Platform in Dynamics 365 Environments
Dynamics 365 licences include Power Platform entitlements that are more generous than M365 seeded rights but still carry limitations. Every Dynamics 365 Enterprise licence (Sales, Customer Service, Field Service, Finance, Supply Chain Management) includes: unlimited Power Apps use within Dynamics 365 applications, the right to create and run custom Power Apps that read from and write to Dataverse tables within the Dynamics 365 environment, Power Automate cloud flows that extend Dynamics 365 processes, and a Dataverse storage allocation tied to the Dynamics licence tier.
The limitation: Dynamics 365 use rights cover Power Platform use within the Dynamics 365 context. A Power App that accesses Dynamics 365 data is covered. A Power App that connects to a non-Dynamics data source (a standalone SQL database, a third-party API, a SharePoint library unrelated to Dynamics) may require a separate Power Apps licence depending on the specific scenario. Microsoft’s licensing documentation uses the phrase “within the context of the Dynamics 365 application” to define the boundary — a deliberately ambiguous standard that creates compliance risk for organisations extending Power Platform beyond their Dynamics footprint.
EA Negotiation Strategies for Power Platform
Power Platform licensing is among the most negotiable components of a Microsoft Enterprise Agreement because Microsoft wants adoption volume to drive the platform’s network effects. Five strategies consistently deliver 15–35% savings:
1. Volume tier progression. Power Apps and Power Automate have unpublished volume discount tiers that activate at 500, 1,000, and 5,000 licences. Push for the next tier’s pricing even if your current count falls short. A commitment to reach the tier within 12–18 months is often sufficient to unlock the lower rate.
2. Bundle Power Apps + Power Automate. Users who need both products should be negotiated as a bundle rather than as separate line items. The combined list price is $35/user/month, but bundled EA pricing typically achieves $26–$30/user/month for the pair.
3. Per-app volume packs. Per-app licences are available in volume packs (100, 500, 1,000 app passes) at significant discounts versus individual per-app pricing. A 1,000-app-pass pack at EA pricing can reduce the effective per-app cost from $5 to $3–$3.50/user/app/month.
4. Dataverse storage buffers. Negotiate additional Dataverse storage as part of the EA rather than purchasing overage at $40/GB/month. Pre-purchased storage in the EA typically costs $15–$25/GB/month — 40–60% less than on-demand overage pricing.
5. AI Builder credit pools. As AI features expand, negotiate a forward-looking AI Builder credit allocation. Credits purchased within the EA at commitment pricing are typically 20–30% cheaper than on-demand packs. Project your credit consumption based on current document processing volumes plus planned AI feature adoption over the EA term.
Governance and Compliance Considerations
Power Platform’s low-code nature creates a licensing governance challenge that does not exist with traditional enterprise software. When business users can build apps and automations without IT involvement, licensing compliance depends on ensuring that every app and flow using premium features has appropriate licence coverage for all users who interact with it.
Connector auditing: The Power Platform admin centre provides visibility into which connectors are in use across the tenant. Implement a monthly connector audit that flags any new use of premium connectors in apps or flows running under M365 seeded rights. A single premium connector added by a citizen developer to a widely-shared app can create licensing exposure for every user who has accessed that app.
Environment strategy: Use Power Platform environments to enforce licensing boundaries. Create separate environments for seeded (M365-only) and premium (standalone-licensed) workloads. Data Loss Prevention (DLP) policies can block premium connectors in the seeded environment, preventing accidental licence requirement escalation. This administrative control is more reliable than relying on user awareness of connector classifications.
Licence assignment verification: Power Platform licences are assigned through the Microsoft 365 admin centre, but actual usage occurs through Power Platform apps and flows that may have different user populations. Audit quarterly: compare assigned licences against the actual unique users who have accessed premium-connector apps and flows. Over-assignment wastes budget; under-assignment creates compliance exposure.