Microsoft Power Platform Licensing Guide 2026: Complete Enterprise Reference

Power Platform in the 2026 Enterprise Landscape

Microsoft Power Platform — encompassing Power Apps, Power Automate, Power BI, Power Pages, and Copilot Studio — has become a strategic platform investment for enterprise organisations. The platform's citizen developer model, combined with Microsoft's extensive marketing to business users, has driven rapid adoption at a rate that frequently outpaces the licence governance infrastructure organisations have in place to manage it.

Power Platform is now one of the fastest-growing sources of unbudgeted Microsoft spend in the enterprise. The seeded entitlement model — where every M365 E1, E3, E5, and E7 user receives baseline Power Platform access — creates a deceptively low initial cost. The hidden costs emerge when applications connect to premium connectors, when Dataverse storage accumulates beyond default allocations, when Copilot Studio sessions scale with bot adoption, and when the AI Builder credit removal in November 2026 hits organisations that built document automation on the complimentary 5,000 credits.

Understanding Power Platform licensing in 2026 requires mapping five distinct cost dimensions simultaneously: per-user licences for creators and consumers, capacity-based costs for BI and environment storage, session-based charges for bots and chatbots, consumption-based charges for AI processing, and connector entitlement boundaries that determine which users require which licence tier.

The M365 Seeded Entitlement: What It Covers and What It Doesn't

Every user with an M365 E1, E3, E5, or E7 licence receives seeded Power Platform entitlements. These seeded rights allow users to build and run Power Apps canvas applications connecting to M365 data sources (SharePoint, Teams, Excel, OneDrive, Outlook), create basic Power Automate flows between M365 services, access Power BI service at Pro level (E5 includes Power BI Pro), and publish basic internal-facing Power Pages websites.

The seeded entitlement boundary is defined by the connector tier. Standard connectors — Microsoft-owned M365 services and a curated set of common enterprise connectors — are accessible on seeded entitlements. Premium connectors — Dataverse, Dynamics 365, SQL Server, SAP, Salesforce, ServiceNow, and hundreds of non-Microsoft SaaS APIs — require either Power Apps Premium ($20 per user per month) or Power Automate Premium ($15 per user per month) depending on the workload.

The practical implication is that any Power Platform application or automation that touches business-critical enterprise systems beyond the M365 boundary will require premium licences for every user who accesses it. This is the most frequently encountered licensing compliance gap — development teams build applications on the seeded entitlement using M365 data, deploy to production, connect to a premium system, and inadvertently trigger a True-Up liability for the entire user population without realising the licence threshold has been crossed.

Power Apps Licensing: Every Tier Explained

Seeded M365 Entitlement

Included with all M365 plans. Users can run and create canvas apps using standard M365 connectors. No additional Power Apps licence required. This covers a significant number of internal productivity application use cases — simple forms, approval workflows, inventory tracking via SharePoint — where the data layer stays within M365. The moment an app connects to Dataverse, Dynamics 365, or any premium connector, this entitlement no longer suffices for affected users.

Power Apps Premium: $20 Per User Per Month

Power Apps Premium provides unlimited app creation and consumption for a single licensed user, including access to all premium connectors, Dataverse access, the ability to build model-driven apps (more structured applications backed by Dataverse tables), and Power Pages site creation and consumption. At $20 per user per month, it is the standard licence for enterprise developers building production applications on the platform, and for users who need to access any application using premium connectivity.

Power Apps Premium is included within certain Dynamics 365 plans — specifically, users with qualifying Dynamics 365 licences (Sales Enterprise, Customer Service Enterprise, Field Service, and others) receive Power Apps Premium rights as part of their Dynamics 365 entitlement, limited to apps within the same Dynamics 365 environment. Organisations with large Dynamics 365 deployments should audit whether Power Apps usage falls within Dynamics-entitled environments before purchasing standalone Power Apps Premium.

Power Apps Per App: Retired January 2026

The Power Apps Per App plan — $5 per user per app per month — was retired from Microsoft's price lists for new customers on 2 January 2026. This had been the most cost-effective entry point for organisations deploying a single application using premium connectors to a targeted user population. An HR self-service app accessed by 500 employees, for example, cost $2,500 per month under Per App versus $10,000 per month under Premium.

Existing EA customers who held Per App licences before the retirement can continue using and renewing them through their current agreement term, with changes reconciled at annual True-Up. However, no new Per App licences can be added to agreements that did not include them before the retirement date. This change structurally increases Power Platform entry costs for organisations that relied on Per App for targeted deployments, and forces a migration planning exercise for every organisation currently on Per App licences as their EA approaches renewal.

Power Automate Licensing: Every Tier Explained

Seeded M365 Entitlement

Users with M365 licences can create automated flows between M365 services using standard connectors. SharePoint-to-Teams notifications, OneDrive-triggered emails, Outlook calendar-based workflows, and Teams approval automations are all available without any additional Power Automate licence. This seeded capability covers a wide range of basic business process automation requirements, particularly in organisations where the primary data sources are SharePoint and Teams.

Power Automate Premium: $15 Per User Per Month

Power Automate Premium (previously Power Automate Per User) provides unlimited cloud flows and desktop flows for a single licensed user, with access to all premium connectors, Dataverse, process mining features, attended robotic process automation (RPA) using Power Automate Desktop, and unlimited AI Builder action use (until the November 2026 removal of complimentary credits). This is the standard licence for users who build or run any automation connecting to premium data sources or running desktop automation.

Power Automate Process: $150 Per Bot Per Month

Power Automate Process (previously Power Automate Per Flow) licences a flow rather than a user. At $150 per flow per month, it is intended for automations that run in unattended mode — executing scheduled tasks, batch processes, or system-to-system integrations without a specific user context. For high-volume, always-running automations, the Process model is more cost-effective than assigning multiple Premium user licences to a shared service account.

The Process model is particularly relevant for RPA deployments where unattended bots process large volumes of transactional data overnight — invoice processing, data synchronisation, system integration workflows. A single Process licence at $150 per month covers the flow regardless of how many times it runs, making it significantly cheaper than a per-execution consumption model for high-frequency automations.

Power BI Licensing: Pro, PPU, and Fabric

Power BI licensing is detailed in our Power BI Premium Licensing guide, but the key 2026 facts are: Power BI Pro is $10 per user per month (included in M365 E5 and the new M365 E7 SKU). Power BI Premium Per User (PPU) is $20 per user per month and provides all Premium features on a per-user basis. Microsoft Fabric F-SKUs provide capacity-based deployment from $262 per month (F2) to over $99,900 per month (F2048). P-SKUs are retired — organisations on P1 through P4 must migrate to F-SKUs at their next renewal.

The critical decision point for 2026 Power BI deployments is the F64 threshold. Fabric F-SKUs below F64 do not include unlimited viewer access — report consumers still need Pro licences. F64 and above eliminate the per-user Pro requirement for viewers, making capacity-based deployment economical for organisations with more than 250 to 500 report consumers. Microsoft's strategic direction is firmly toward Fabric — new Power BI features are Fabric-first, and the analytics roadmap is integrated with broader Fabric data workloads.

Power Pages: External User Licensing

Power Pages enables organisations to build authenticated customer portals, partner extranets, and public-facing web applications backed by Dataverse. Its licensing model is fundamentally different from internal user licensing — it charges per authenticated external user and per anonymous page visit rather than per named internal employee.

The Authenticated Users capacity add-on costs $200 per 100 authenticated users per month — approximately $2 per external user per month. The Anonymous Users capacity add-on costs $75 per 50,000 anonymous user sessions per month. For customer-facing portal use cases with large external user populations, Power Pages costs scale rapidly. A portal with 10,000 authenticated customers costs $2,000 per month in Authenticated Users capacity alone, before Dataverse storage and additional platform costs.

Internal employee portals — where all users hold M365 licences — are covered by the seeded entitlement provided the portal uses only standard connector data sources. The moment internal portals use Dataverse-backed data, employees accessing the portal require Power Apps Premium licences regardless of the portal's internal-facing nature. This is one of the most common compliance blind spots in Power Pages deployments.

Copilot Studio: The Growing Session-Based Cost

Copilot Studio (formerly Power Virtual Agents) is Microsoft's platform for building AI-powered conversational agents — customer service bots, employee self-service copilots, and process-guided assistants. Its licensing model operates on sessions at $200 per 2,500 sessions per month, making it one of the few Power Platform components priced on usage rather than named users.

A session is a conversation lasting up to 60 minutes or 100 turns. For simple rule-based bots, sessions are short and predictable. For AI-enabled agents using generative responses backed by Azure OpenAI, session complexity and duration are harder to predict — users engage differently with conversational AI than with menu-based bots, often exploring capabilities and asking follow-up questions that extend session length and depth.

Copilot Studio is deeply integrated with Microsoft 365 Copilot — the $30 per user per month AI productivity add-on now bundled within the new M365 E7 SKU. Microsoft's commercial motion is to position Copilot Studio as the enterprise agent development platform, complementing M365 Copilot's out-of-the-box AI capabilities with custom organisational agents. Organisations that purchase E7 or M365 Copilot should model Copilot Studio session costs as a necessary companion investment if they plan to build custom agents — the session-based pricing is additive to the E7 or Copilot licence cost.

Dataverse: The Storage Cost That Defines Total Cost

Dataverse is the relational database layer for Power Apps model-driven applications, Dynamics 365, and Copilot Studio. Its $40 per GB per month database storage charge is the largest per-unit cost in the Power Platform portfolio and the one most commonly omitted from initial deployment cost models.

Default Dataverse storage allocations per tenant: 10 GB database plus 20 GB file storage. Additional allocation per qualifying licence: 250 MB database and 2 GB file storage per user with Power Apps Premium, Power Automate Premium, or a qualifying Dynamics 365 licence. For a 1,000-user Power Apps Premium deployment, this provides approximately 10 GB tenant base plus 250 GB user-allocated database storage — 260 GB total database allocation before any overage charges.

In practice, Dataverse accumulates data faster than organisations plan for. Application records, audit logs, workflow execution histories, attachments stored as file records, and integration data from connected systems all consume Dataverse storage. A mid-scale deployment with 500 active users generating daily records can exceed its allocation within 18 to 24 months without active data retention management. At $40 per GB per month, a 100 GB overage costs $48,000 per year — more than the annual Power Apps Premium licence cost for many targeted user populations.

Data retention policies, archiving strategies, and periodic database cleanup are not optional operational overhead — they are commercial necessities in any Dataverse-based deployment. The Power Platform admin centre provides storage consumption reports at the environment level; these should be reviewed monthly and flagged to the licensing team when consumption approaches 70 percent of allocation.

AI Builder: The November 2026 Credits Removal

AI Builder provides machine learning capabilities within Power Platform — document processing (AI models that extract data from invoices, forms, receipts, and contracts), prediction models for business data, object detection in images, and AI-powered processing within Power Automate flows. Currently, Power Apps Premium and Power Automate Premium include 5,000 AI Builder credits per user per month.

Microsoft has announced that these complimentary credits will be removed effective 1 November 2026. After this date, organisations that use AI Builder capabilities will need to purchase the AI Builder capacity add-on separately, priced at approximately $500 per 1 million credits per month. The practical impact depends on current AI Builder consumption — organisations with document processing automations that process thousands of documents per month may face significant incremental costs, while organisations that have not activated AI Builder capabilities may be unaffected.

The recommended action is immediate: run an AI Builder usage report from the Power Platform admin centre (under Capacity, AI Builder credits), quantify monthly credit consumption by environment, identify which flows and applications drive the highest consumption, and model the November 2026 cost at add-on pricing. If annual AI Builder credit costs under add-on pricing exceed $10,000, a procurement decision is required before November 2026.

Power Platform and the M365 E7 Context

Microsoft's M365 SKU stack now runs E1, E3, E5, and E7 — with E7 as the current top SKU, positioned above E5 and bundling advanced AI capabilities, enhanced security features, and Microsoft 365 Copilot access that were previously sold as separate add-ons to E5. Microsoft field teams are actively running E5-to-E7 migration motions at renewal, and Power Platform licensing sits at the intersection of this migration.

E7 includes Power BI Pro and enhanced Power Platform seeded entitlements, but does not include Power Apps Premium, Power Automate Premium, or Copilot Studio sessions. Organisations that migrate from E5 to E7 and simultaneously plan to expand Power Platform adoption will face parallel licence costs — the E7 premium for AI and security capabilities plus standalone Power Platform Premium licences for users requiring premium connectors or Dataverse access.

The commercial implication is that the E7 migration decision and the Power Platform expansion decision should be made in the same EA negotiation window. Bundling E7 volumes, Power Apps Premium volumes, and Power Automate Premium volumes in a single EA negotiation creates leverage that individual procurement does not. Organisations that allow Microsoft to negotiate E7 and Power Platform separately — in different contract amendments or renewal cycles — typically pay 15 to 25 percent more than those that bundle these components in a unified commercial discussion.

EA Negotiation Strategies for Power Platform

Power Platform licences are negotiable within the EA, and the degree of discount depends on several factors: the total volume committed, the term length (three-year vs annual), the Azure consumption commit level, and whether Power Platform is negotiated as part of a broader EA renewal or as a standalone amendment.

Standard EA discounts for Power Platform in 2026 are 10 to 20 percent below list price, consistent with the broader Microsoft EA discount range. Organisations that negotiate Power Platform within the context of a large EA renewal — where M365 seat volume, Azure consumption, and Dynamics 365 are all on the table simultaneously — can achieve the upper end of the discount range. Standalone Power Platform amendments, particularly those negotiated mid-cycle outside the formal EA renewal, typically receive minimal discount as Microsoft has limited commercial incentive to negotiate aggressively without a broader relationship lever.

The Microsoft fiscal year ends June 30, making April through June the Q4 window when field teams have maximum quota pressure and the highest incentive to offer incremental discounts to close commitments. Power Platform licence commitments introduced during Q4, bundled within a broader EA renewal conversation, are most likely to attract competitive pricing. Organisations approaching EA renewal between April and June 2026 should use this window deliberately.

Beyond standard discounts, there are three specific Power Platform negotiation levers worth understanding. Storage capacity: Negotiate additional Dataverse storage capacity as part of the EA rather than purchasing capacity add-ons later at list price. Storage add-ons negotiated at EA renewal carry the same discount as base licences. AI Builder credits: With the November 2026 removal of complimentary credits, the window to negotiate AI Builder capacity at EA pricing rather than at-will list pricing closes rapidly. Any organisation with known AI Builder consumption should include AI Builder capacity in the next EA amendment. Per App transition credits: Organisations migrating from Per App to Premium can in some cases negotiate migration assistance or enhanced Premium pricing to offset the cost increase. This requires explicit negotiation with the account team — it is not offered automatically.

The Governance Framework Every Organisation Needs

Power Platform licence governance requires a structured framework that most organisations do not have in place at the time they first encounter a True-Up surprise. The essential components of an effective governance framework are connector monitoring, environment management, storage oversight, and licence assignment controls.

Connector monitoring means maintaining a live registry of every Power App and Power Automate flow in production, with a flag for whether it uses standard or premium connectors. This registry is the early warning system for licence compliance — any new premium connector use triggers a licence review before the connection is deployed. The Power Platform admin centre provides connector usage reports at the environment level; these should be reviewed at least monthly by the Power Platform governance team.

Environment management means structuring Power Platform environments to separate development, test, and production workloads. Development environments are typically provisioned without production data, reducing licence requirements for developers during the build phase. Production environments require governance review before any new application is promoted, including licence impact assessment for the user population.

Storage oversight means monthly review of Dataverse consumption against allocated capacity, with automatic alerts configured at 50 percent and 80 percent thresholds. Data retention policies for every Dataverse entity should be defined at the time of application design, not retroactively when storage alerts fire.

Licence assignment controls mean that Power Apps Premium and Power Automate Premium licences are managed through a formal request and approval process rather than self-service assignment. In many organisations, M365 global administrators can assign Power Platform licences without a procurement review, creating compliance exposure when premium connector use triggers licence requirements for large user populations without corresponding budget.

Ten Priority Recommendations for 2026

1. Audit premium connector use across all production environments: Run a connector usage report from the Power Platform admin centre. Identify every flow and application using premium connectors. Verify that all users accessing those applications hold Power Apps Premium or Power Automate Premium licences.

2. Model the Per App to Premium transition cost: If your organisation holds Per App licences in its EA, calculate the cost differential when those licences come up for renewal. For large single-application deployments, the 4x price increase is material and requires advance budget planning.

3. Run an AI Builder usage audit before September 2026: Quantify monthly AI Builder credit consumption. Model the cost at add-on pricing. Make a procurement decision before the November 2026 removal of complimentary credits creates a budget gap.

4. Implement Dataverse storage monitoring immediately: Configure alerts in the Power Platform admin centre for 50 percent and 80 percent storage utilisation. Define data retention policies for all Dataverse entities.

5. Bundle Power Platform negotiations with the EA renewal: Do not renew Power Platform licences in isolation. Wait for the EA renewal window and negotiate all Power Platform components — Power Apps, Power Automate, Power BI, Copilot Studio sessions, and Dataverse storage — as a single commercial package.

6. Target the April to June Q4 window: Microsoft's fiscal year ends June 30. The Q4 window (April through June) is when field teams have maximum discount incentive. Power Platform commitments introduced in this window attract better pricing than those negotiated outside it.

7. Evaluate E7 and Power Platform costs together: The E7 migration motion from Microsoft field teams is correlated with Power Platform expansion. Assess both decisions together rather than sequentially to avoid paying list price for one component while negotiating the other.

8. Consider Fabric for large Power BI deployments: If Power BI report consumer populations exceed 250 users requiring Premium features, model F64 Fabric capacity against PPU. At negotiated Azure pricing, Fabric capacity often reaches break-even at lower user counts than list price calculations suggest.

9. Negotiate Dataverse storage as part of EA: Storage add-ons purchased at-will after EA renewal are at list price with no discount. Storage capacity committed at EA renewal carries the same discount as base licences. Any predictable storage growth should be pre-committed at EA pricing.

10. Engage independent Microsoft EA advisory specialists: Power Platform licensing spans five cost dimensions simultaneously — per-user, capacity, session, consumption, and storage. Independent advisory with no vendor affiliation provides the objective cost modelling and negotiation strategy that in-house IT and Microsoft-aligned partners cannot.