Power BI Premium no longer has one fixed monthly price to quote. Microsoft is retiring the old Premium per-capacity SKUs (P1 through P5) and selling capacity as Fabric F SKUs instead, billed through Azure per second rather than as a flat monthly fee. The right way to answer "what will this cost us" is to calculate it from your own headcount and viewer count, not to look up a single number.

Why there is no fixed Premium price anymore

Power BI Premium P SKUs are now sold only to customers with an active Enterprise Agreement, and Microsoft directs new and existing customers toward Fabric F SKUs. F SKUs are billed per second through Azure, either pay-as-you-go with no commitment or at a lower rate with a one-year reservation, and the rate is regional. That means the true monthly cost of an F64 capacity in Frankfurt is a different number than the same F64 in Virginia, and it changes with Azure's own pricing updates. Quote the Fabric pricing page for a current figure rather than trusting a number printed in an article.

The two paths, and how to price each one

Every organization's Power BI cost comes down to one of two shapes, or a mix of both.

Path 1: Pro or PPU for every named user

Cost is simple to calculate: headcount multiplied by the per-user price.

• $14.00 per user per month for Pro, paid yearly, for anyone who views, shares or publishes.

• $24.00 per user per month for PPU, paid yearly, for anyone who needs Premium features such as larger models or more refreshes.

As an illustrative example: 50 people who only view reports, on Pro, comes to 50 x $14.00 = $700.00 a month. This path scales linearly. It gets expensive once viewer counts climb into the hundreds.

Path 2: A Fabric capacity for viewers, Pro or PPU only for publishers

An F64-or-larger Fabric capacity lets free-license users view Power BI content, so you stop paying per viewer. You still need Pro or PPU for anyone who publishes or shares content; the capacity does not remove that requirement, it only removes it for viewers. Capacity cost depends on the SKU size, the region and whether you reserve it for a year, so price it on the Fabric pricing page using your own region before comparing it against Path 1.

How to decide between the two

1. Count your builders and publishers separately from your viewers. Builders need Pro or PPU regardless of which path you choose.

2. Price Path 1 for your viewer count. Multiply viewers by $14.00.

3. Price Path 2 for the same viewer count, using the Fabric pricing page for your region and your expected usage pattern (reserved capacity is usually cheaper if you will run it continuously).

4. Compare the two totals. Organizations with a small number of viewers usually do better on Path 1. Organizations with hundreds of viewers, or that already want Fabric for lakehouses and pipelines alongside Power BI, usually do better on Path 2.

See Power BI Premium capacity for how to decide whether you need a capacity at all, and implementing a Power BI Premium capacity for the steps to actually set one up once you have.

Power BI Embedded

Power BI Embedded (A SKUs) is a separate product for putting reports inside your own application. It is billed through Azure and its cost depends on the node size and number of nodes you run, not on a per-user license. See our full licensing guide for how Embedded licensing works for internal versus external users.

FAQs

How is a Fabric capacity billed?

Per second, through Azure, either pay-as-you-go with no commitment or at a discounted rate with a one-year reservation. Pricing is regional, so the same SKU costs different amounts in different Azure regions.

Is it cheaper to buy Pro licenses for everyone or a Fabric capacity?

It depends on your viewer count and region. Multiply your viewer count by $14.00 for the Pro path, then compare that against a Fabric capacity's price for your region on the Azure pricing page. There is no single break-even number that holds for every organization.

How does Power BI Embedded usage show up on my bill?

As an Azure charge tied to the A-SKU node size and number of nodes you have running, billed alongside your other Azure resources rather than as a separate Power BI subscription line.

Sources

• Understand Microsoft Fabric licenses and capacity - Microsoft Learn

• Microsoft Fabric pricing - Microsoft

• Power BI Embedded pricing - Microsoft