Power BI Embedded Pricing Explained

Power BI Embedded is priced on capacity, not per user. Instead of buying a licence for each viewer, you buy a unit of compute, an A-SKU from Azure or a Microsoft Fabric F-SKU, sized to how much concurrent rendering and data refresh your application needs. Your external customers then view governed reports through your app without ever holding a Power BI licence. This is what makes embedded the natural cost model for SaaS products and customer portals, but it also means you must size capacity to load rather than headcount, which trips up teams expecting predictable per-seat billing.

Two ways to buy capacity

There are two routes, and they overlap.

A-SKUs (Azure) are the classic Power BI Embedded capacities, provisioned in the Azure portal. They are billed per hour, can be paused and resumed, and scale up or down on demand. This pause behaviour is valuable: if your product is only used during business hours, or you run dev and test environments, you can switch capacity off and stop paying for it.

F-SKUs (Microsoft Fabric) are the newer, broader capacity model. Fabric capacities cover far more than embedding, data engineering, warehousing, real-time analytics, and they include Power BI workloads. For new builds, Microsoft is steering customers toward Fabric F-SKUs, and Copilot has separate capacity and feature requirements. Copilot in Power BI requires paid Fabric F2 or higher, or Power BI Premium P1 or higher capacity. Pro or Premium Per User alone is insufficient. Check administrator settings, supported region and access for the experience you plan to use. For an embedded application, check support for the specific Copilot feature and embedding scenario before budgeting. F-SKUs can also be paused, and reserved or annual commitments reduce the effective rate for steady workloads.

How the cost model actually works

The number you care about is not "price per user" but "capacity needed for peak concurrency". Two products with 10,000 registered customers can need wildly different capacity depending on how many view reports at the same moment, how heavy the queries are, and how often datasets refresh.

Because Microsoft revises SKU tiers, capacity unit allocations and prices regularly, treat any figure you read as indicative and confirm current pricing with Microsoft before budgeting. As of 2026, confirm current pricing directly.

Sizing without overspending

The most common and most expensive mistake is buying a large capacity "to be safe". Start with the smallest viable SKU, then use the Fabric Capacity Metrics app to watch utilisation under real traffic. Smoothing means Power BI averages bursts over time, so short spikes do not necessarily require a bigger SKU. Optimise the model first: a well-designed star schema, aggregations and reduced visual count often cut required capacity more than a larger SKU would, at no recurring cost.

Embedded cost versus per-user licensing

It helps to keep the alternatives in mind. Power BI Pro is a low per-user monthly licence, suitable when viewers sign in themselves (the user owns data pattern). Premium Per User (PPU) is a higher per-user licence for individuals needing premium features. Embedded capacity wins economically once you have many external viewers, because per-user costs would scale linearly while capacity is fixed. For the architecture behind these choices, see our guide on how to embed Power BI in your web app, and our Power BI and Microsoft Fabric services for capacity planning support.

A simple budgeting approach

Model three scenarios: launch (smallest SKU, paused outside business hours), growth (next SKU up, mostly always-on), and scale (reserved capacity with optimised models). Attach expected monthly cost to each and a trigger that moves you between them, for example sustained utilisation above a set threshold. This turns an open-ended bill into a planned ladder, which is exactly what finance teams want to see.

If you are pricing an embedded analytics feature for a product, or trying to work out whether your current capacity is the right size, a Trusted Numbers Review gives you an independent view of your capacity, model efficiency and cost trajectory. It is a fixed, published fee, credited against any follow-on build, so you get clarity before you commit to a bigger spend.