Thank you for registering. Your copy of the Power Platform Licensing Guide has been prepared for immediate access. 16 pages on Power Apps per-user and per-app licensing, Power Automate premium and RPA licensing, Power BI Premium capacity and per-user models, Copilot Studio per-session and tenant licensing, and the EA negotiation framework for Power Platform commitments.
A confirmation has also been sent to your registered email address. If you don't receive it within 10 minutes, check your spam folder.
Power Platform licensing complexity stems from rapid product evolution, a model that prices by user and by session and by capacity depending on which component you're using, and a consistent pattern of organisations deploying Power Apps and Power Automate widely before understanding the licensing implications. The result: cost surprises at true-up time, RPA commitments made without understanding the premium connector and attended/unattended flow distinction, and Power BI Premium deployments that could be restructured to deliver equivalent capability at significantly lower cost. Here is the preview of the most commercially critical areas.
Power Apps offers two primary licensing models: the Per-User Plan ($20/user/month) that allows a licensed user to run unlimited Power Apps applications, and the Per-App Plan ($5/user/app/month) that licenses a specific user for a specific application. The economic logic appears straightforward: users who run more than 4 Power Apps applications are cheaper on a Per-User Plan; users who run 4 or fewer are cheaper on Per-App Plans. In practice, the calculation is more complex because Power Apps usage patterns are not static — a user provisioned with a Per-App Plan for one application frequently encounters additional Power Apps in the environment and requires additional Per-App licences. Organisations that deploy Power Apps broadly and assign Per-App Plans consistently find their Per-App licence costs approaching or exceeding Per-User Plan costs within 12–18 months of initial deployment, without the intended cost reduction. The guide provides the user segmentation framework for making the right choice at deployment time rather than discovering the miscalculation at true-up.
Power Automate licensing divides into standard automation (included in Microsoft 365 licences for basic scenarios using standard connectors) and premium automation (requiring a Power Automate Premium or Process licence for premium connectors, business process flows, and robotic process automation). The dividing line between standard and premium connectors is the primary source of unexpected licensing spend: organisations build flows using what they believe to be standard connectors, then discover at the point of deployment or audit that specific connectors — including many commonly used enterprise system connectors — are classified as premium, requiring standalone Power Automate licences for every user whose flows use them. The RPA model adds further complexity: attended RPA (where a human is present during automation execution) requires a Power Automate Premium licence per user, while unattended RPA (automation running without human interaction) requires a Power Automate Process licence per process bot, at $150/bot/month — a cost structure that scales very differently from the per-user model.
Power BI licensing has three tiers: Power BI Free (limited to personal use, no sharing), Power BI Pro ($10/user/month, required for sharing content with other Pro users), and Power BI Premium (either per-capacity at $4,995/month for a P1 node, or per-user at $20/user/month). Power BI Pro is included in Microsoft 365 E5 and as an add-on for E3. Power BI Premium Per User provides access to all Premium features — including paginated reports, AI features, deployment pipelines, and larger dataset sizes — for individual users at the same $20/user cost as Power Apps Per-User. The capacity model (P nodes) is relevant for organisations distributing Power BI content to large populations of view-only consumers: under the P-node model, a single Premium capacity licence allows unlimited users to consume reports published to Premium workspaces without individual Power BI Pro licences. The per-user vs. per-capacity economics decision requires careful modelling of the consumer-to-author ratio in your Power BI deployment.
Copilot Studio (formerly Power Virtual Agents) is licensed by conversation session rather than by user — a fundamentally different pricing model that most procurement teams encounter without adequate preparation. A session is defined as a 60-minute interaction window between an end user and a Copilot Studio agent, regardless of the number of turns within that window. Each Copilot Studio tenant receives 25,000 sessions per month included with a Microsoft 365 subscription — sessions that expire monthly and cannot be carried forward. Beyond the included sessions, additional sessions are purchased in blocks at approximately $200 per 1,000 sessions. The primary licensing risk: organisations that deploy Copilot Studio agents to high-volume use cases (HR helpdesk, IT support, customer service) consume the included 25,000 sessions quickly, then encounter per-session charges that were not in the original deployment budget. Session consumption for a moderately active internal helpdesk running 8 hours daily can exceed the monthly inclusion within the first week.
The Power Platform Licensing Guide is structured as both a planning resource for organisations beginning Power Platform deployments and an optimisation framework for organisations already running Power Platform at scale who have encountered the licensing complexity that deployment-phase decisions created.
Chapter 1 covers the full Power Apps licensing model including the often-overlooked Microsoft 365 seeded rights: every Microsoft 365 and Office 365 commercial plan includes a version of Power Apps that allows users to build and run applications connecting to standard connectors and Microsoft Dataverse for Teams. The seeded rights are functional for many internal productivity use cases but stop short of premium connectors, the full Dataverse environment, and several advanced platform capabilities. Understanding the boundary between seeded rights and standalone Power Apps licensing is the key to avoiding unnecessary licence purchases for scenarios that M365 already covers. The chapter also covers the Power Apps per-app plan metre model — where consumption-based billing in certain deployment scenarios replaces the per-user-per-app flat rate — and the implications for organisations moving toward a pay-as-you-go Power Platform approach.
Key finding: 42% of Power Apps Per-App Plan purchases in large enterprises cover scenarios that are fully within the scope of the Microsoft 365 seeded Power Apps rights — representing direct avoidable spend with no corresponding capability gap.Power Automate is the most complex licensing area within the Power Platform because the line between included and premium capability is non-obvious, changes as Microsoft evolves the connector classification, and has direct compliance implications. Chapter 2 provides the complete framework: how to audit existing Power Automate flows for premium connector usage, the specific connectors that are classified as premium (including the enterprise connectors most commonly used in large organisations — SAP, Salesforce, ServiceNow, and several others), the difference between Power Automate Premium and the Power Automate Process licence for RPA, and the desktop flow licensing model for attended automation scenarios. The chapter covers the Power Automate per-user with attended RPA licence ($40/user/month) and its relationship to the standalone Power Automate Premium ($15/user/month) — including the scenarios where the combined licence is more cost-effective than separate purchases and the scenarios where separate licensing is appropriate.
Key finding: In organisations with more than 500 Power Automate users, an average of 34% of users are running flows that use premium connectors while only licensed for the M365 seeded Power Automate rights — creating compliance exposure that Microsoft's Power Platform admin centre makes straightforward to identify during any SAM review.Chapter 3 covers Power BI Premium in depth — both the per-user model (Premium Per User, or PPU) and the per-capacity model (P1, P2, P3, and P4 nodes), including the Microsoft Fabric integration that has restructured Power BI Premium capacity licensing since 2023. Microsoft Fabric uses a capacity unit (CU) model — Fabric SKUs F4 through F2048 replace the previous P-node SKU structure, with F64 being the approximate functional equivalent of P1. The Fabric capacity model is more granular (you can purchase fractional capacity) but requires understanding CU consumption rates for different workloads. The chapter covers the Power BI Premium capacity decision framework: when per-capacity makes economic sense versus per-user, the workload types that consume disproportionate CUs (paginated reports, dataflows, large dataset refreshes), and the capacity monitoring approach to prevent overprovisioning or underprovisioning. The Microsoft 365 E5 Power BI Pro inclusion and its impact on standalone Power BI Pro purchases within E5 deployments.
Key finding: Organisations purchasing Power BI Premium Per-User licences for populations with 80% or more view-only consumers are paying 3–4x more than a single Power BI Premium capacity node would cost for the equivalent user base — the per-capacity model delivers substantially better economics at scale for content distribution scenarios.Chapter 4 covers Copilot Studio (formerly Power Virtual Agents) licensing in full, with particular focus on session capacity planning — the area where most organisations encounter budget surprises. The chapter provides session consumption models for the most common enterprise use cases: internal IT helpdesk (typical session volume 800–2,000 sessions/month for a 1,000-employee deployment), HR FAQs automation (500–1,200 sessions/month), and external customer-facing agents (highly variable, requiring traffic-based modelling). The Teams deployment model is covered separately — Copilot Studio agents deployed within Microsoft Teams have a different session model that includes specific use cases within the Teams environment without consuming the general session pool, relevant for organisations deploying internal Teams-based chatbots. The chapter also covers the Copilot Studio licensing for organisations building agents that are part of Microsoft 365 Copilot deployments, where the Copilot Studio capacity interacts with the broader Microsoft 365 Copilot licensing in ways that require explicit planning.
Key finding: An active enterprise Copilot Studio deployment with three internal helpdesk agents and one external FAQ bot typically consumes 40,000–80,000 sessions per month — 60–220% more than the included 25,000 sessions — making a committed session block purchase more cost-effective than pay-as-you-go session overage within the first quarter of deployment.Power Platform commitment within an Enterprise Agreement offers negotiation leverage that most organisations do not use effectively. Chapter 5 covers the Power Platform EA strategy: the Power Platform add-on model within existing M365/Office 365 EA commitments, the standalone Power Platform Enterprise Agreement structure, the Microsoft incentives for committing to Power Platform capacity at scale, and the specific negotiation positions available when renewing an EA that includes Power Platform components. The guide covers the Power Apps Pay-As-You-Go metre commitment negotiation, the Power Platform Centre of Excellence (CoE) packaging that Microsoft sales teams often push, the pricing authority structure within Microsoft for Power Platform (which has different approval thresholds than M365 and Azure), and the timing dynamics for Power Platform commitments — where the end-of-quarter and end-of-fiscal pressure that applies to Azure and M365 also applies to Power Platform but with additional product-specific incentives that surface in Q4.
Key finding: Power Platform commitments made at Microsoft fiscal year-end (June 30) typically achieve 18–28% discounts versus mid-year EA amendments — the largest per-unit discount differential we observe across any Microsoft product family, reflecting the significant revenue recognition pressure Microsoft carries on Power Platform growth commitments.Our advisory service covers Power Platform licence position analysis, usage audits for premium connector and RPA compliance, Power BI capacity optimisation, and EA negotiation strategy for Power Platform commitments — with direct experience managing Power Platform costs across complex enterprise estates.
The companion guide covering Microsoft 365 Copilot licensing — the four commitment traps, the Copilot for M365 vs. Copilot Studio distinction, and the negotiation framework for avoiding over-commitment on AI features.
Download Free →The full analysis of Microsoft 365 E3 vs. E5 — covering the Power BI Pro inclusion in E5, the Power Automate premium connector rights by SKU, and the 18-dimension feature comparison that drives the upgrade decision.
Download Free →The 8-chapter EA negotiation framework covering the Power Platform commitment structure, Microsoft pricing authority for add-on products, and the end-of-quarter timing that delivers maximum discount on Power Platform.
Download Free →The frameworks in this guide work. They work better with 20 years of deal data behind them. If you have an upcoming EA renewal, true-up, or Microsoft audit — a 20-minute call with a senior advisor will tell you exactly where your exposure is and what you can negotiate.