Power BI costs are set by two independent decisions: how many people need a per-user license, and whether you buy capacity. Pro is $14.00 and Premium Per User is $24.00 per user per month on annual billing, as published at time of writing (July 2026). Capacity changes the math entirely — at Fabric F64 and above, viewers need no paid license. EPC Group is a Houston-based Microsoft consulting firm operating since 1997, with six Microsoft Solutions Partner designations and 216+ M&A tenant migrations covering 1.83 million users.
Quick facts
| Question | Answer (July 2026) |
|---|---|
| Cheapest way to author and share | Power BI Pro, $14.00/user/month annual |
| Cheapest way to give Premium features to a small team | Premium Per User, $24.00/user/month annual |
| Point at which viewers stop needing a paid license | Fabric F64 and above |
| Status of Power BI Premium P1–P5 | Retiring at end of each customer’s agreement term; no new sales |
| Replacement for P SKUs | Microsoft Fabric F SKUs, bought in Azure |
| Status of Power BI Embedded A SKUs | Active, not part of the P retirement — but Embedded is included in every F SKU |
| Reservation discount vs pay-as-you-go | ~41% for a 1- or 3-year Fabric capacity reservation |
| What the reservation does not cover | Storage and networking charges |
| Report Server entitlement after P retirement | Fabric capacity reservation, or SQL Server Enterprise Edition with Software Assurance |
| Largest single semantic model on F64 | 25 GB |
The 2026 SKU table
Capacity units (CUs) are the unit of compute. The v-core column exists only to translate legacy Power BI Premium sizing; it is a compute comparison, not a statement of licensing equivalence.
| SKU | Capacity Units | Legacy Power BI SKU | v-cores | CU hours/day | Free users can view? |
|---|---|---|---|---|---|
| Free (per user) | n/a | n/a | n/a | n/a | Own workspace only |
| Pro (per user) | n/a | n/a | n/a | n/a | n/a — $14.00/user/mo |
| Premium Per User | n/a | n/a | n/a | n/a | n/a — $24.00/user/mo |
| F2 | 2 | — | 0.25 | 48 | No |
| F4 | 4 | — | 0.5 | 96 | No |
| F8 | 8 | EM1/A1 | 1 | 192 | No |
| F16 | 16 | EM2/A2 | 2 | 384 | No |
| F32 | 32 | EM3/A3 | 4 | 768 | No |
| F64 | 64 | P1/A4 | 8 | 1,536 | Yes |
| F128 | 128 | P2/A5 | 16 | 3,072 | Yes |
| F256 | 256 | P3/A6 | 32 | 6,144 | Yes |
| F512 | 512 | P4/A7 | 64 | 12,288 | Yes |
| F1024 | 1,024 | P5/A8 | 128 | 24,576 | Yes |
| F2048 | 2,048 | — | 256 | 49,152 | Yes |
| F4096 | 4,096 | — | 512 | 98,304 | Yes |
| F8192 | 8,192 | — | 1,024 | 196,608 | Yes |
Microsoft publishes F SKU dollar prices on the Azure pricing page and calculator only, and the rate varies by region. This article quotes no F SKU dollar figure, because no single figure is correct everywhere. The arithmetic below takes your quoted regional price as its input.
The Five-Layer Power BI Cost Stack
Most licensing quotes are wrong because they price one layer and forget four. EPC Group uses a five-layer stack on every Power BI commercial model. Price all five, or the number you take to finance will move.
- Viewer layer. People who only consume. $0 on F64+, or $14.00 each below it. This layer decides whether you buy capacity at all.
- Author layer. People who publish, share, or manage workspaces. Always Pro or PPU, on every SKU. Capacity does not make authors free.
- Capacity layer. The F SKU, the pay-as-you-go/reservation decision, overage exposure, and the dev/test capacity nobody budgets for.
- Connectivity layer. Gateways: the VMs, the cluster members for high availability, and sizing headroom. The 30-refresh concurrency limit means a second cluster, not a bigger box.
- Governance layer. Purview, tenant settings enforcement, certification workflow, and the standing effort to keep it true — the line item most often discovered after signature.
Layers 4 and 5 are absent from every page currently ranking on “power bi pricing.” They are why quoted budgets slip.
The break-even: Pro versus F64, with the arithmetic shown
The only economic question that matters at scale: at what viewer count does capacity cost less than per-viewer licences?
Let C be your quoted monthly F64 cost in your Azure region. Authors pay $14.00 either way, so they cancel out of both sides. The comparison is viewers-avoided against capacity cost.
Break-even viewers = C ÷ $14.00
Below that viewer count, keep buying Pro. Above it, capacity is cheaper — assuming F64 has the compute headroom for the workload, which is a separate test covered further down.
| If your F64 quote is (monthly) | Break-even viewer count | Interpretation |
|---|---|---|
| $6,000 | 6,000 ÷ 14 = 429 viewers | Capacity wins from ~430 viewers up |
| $8,000 | 8,000 ÷ 14 = 572 viewers | Capacity wins from ~575 viewers up |
| $10,000 | 10,000 ÷ 14 = 715 viewers | Capacity wins from ~715 viewers up |
| $12,000 | 12,000 ÷ 14 = 858 viewers | Capacity wins from ~860 viewers up |
Substitute your own regional quote. The formula does not change.
Worked model at three organisation sizes
Assume a common enterprise shape: 10% authors, 90% viewers. All figures use the verified $14.00 Pro price.
250-user organisation — 25 authors, 225 viewers
- All-Pro: 250 × $14.00 = $3,500/month = $42,000/year
- On F64: (25 × $14.00) + C = $350 + C per month
- Capacity must cost under 225 × $14.00 = $3,150/month to win
- Verdict: do not buy capacity. No realistic F64 quote clears $3,150. This organisation buys Pro, and buys PPU only for the specific users who need Premium features. Microsoft’s own scenario guidance points the same way: PPU for populations under roughly 250 Power BI users.
2,000-user organisation — 200 authors, 1,800 viewers
- All-Pro: 2,000 × $14.00 = $28,000/month = $336,000/year
- On F64: (200 × $14.00) + C = $2,800 + C per month
- Capacity must cost under 1,800 × $14.00 = $25,200/month to win
- Verdict: capacity wins decisively on licensing. Every plausible F64 quote clears the bar. The question is no longer whether to buy capacity but which size — and whether one F64 carries 2,000 users’ refresh and interactive load. Baseline before you buy.
15,000-user organisation — 1,500 authors, 13,500 viewers
- All-Pro: 15,000 × $14.00 = $210,000/month = $2,520,000/year
- On capacity: (1,500 × $14.00) + C = $21,000 + C per month
- Licensing avoided: 13,500 × $14.00 = $189,000/month = $2,268,000/year
- Verdict: capacity is not optional, and F64 is almost certainly the wrong size. The constraint flips from licensing to compute: F64 caps a single semantic model at 25 GB and delivers 1,536 CU hours per day. Size on measured consumption, not headcount. The gap between F128 and F256 is a rounding error against $2.27M/year of avoided Pro licences — buy the size that performs, not the cheapest.
The pattern: the break-even sits in the mid-hundreds of viewers. Below ~400 viewers, buy per-user licences. Above ~1,000, buy capacity and spend the remaining effort on sizing. Between the two, run the formula with your actual quote.
Which SKU do you actually need — decision tree
| Start here | Condition | Buy this |
|---|---|---|
| 1. Does anyone need to publish or share content? | No — personal analysis only | Free licences. Stop. |
| 2. Do you have fewer than ~400 viewers? | Yes, and no Premium features needed | Pro for everyone who publishes or consumes shared content |
| 3. Do a small team need Premium features (larger models, higher refresh frequency, deployment pipelines)? | Yes, and the audience is small and also licensed | PPU for that team. PPU content can only be consumed by other PPU users unless it sits on capacity |
| 4. Do you have several hundred or more viewers? | Yes | Run C ÷ $14.00. If viewer count exceeds it, move to step 5 |
| 5. Do you need free viewer consumption? | Yes | F64 minimum. Below F64 every viewer still needs Pro or PPU, which defeats the purpose |
| 6. Do you need Fabric workloads (Lakehouse, Warehouse, Notebooks, pipelines) but not free viewers? | Yes | F2–F32 is legitimate. Viewers keep their Pro licences |
| 7. Are you on a P SKU today? | Yes | Map P→F by CU, then right-size on measured consumption. Buy the F SKU before cancelling the P SKU |
| 8. Do you embed for external customers (app owns data)? | Yes | Any F SKU — Embedded is included. You no longer need a separate EM or A SKU |
| 9. Is consumption steady and predictable? | Yes | Add a 1- or 3-year reservation (~41% saving) |
| 10. Is consumption spiky or seasonal? | Yes | Stay pay-as-you-go, and use pause/resume plus on-demand resizing |
The hidden costs
Six line items that do not appear on the Microsoft pricing page and do appear on your invoice.
1. Gateways. Gateways run on machines you pay for, and high availability means a cluster. The gateway enforces a concurrency limit of 30 refreshes; past it you get “too many refreshes occurring concurrently,” and the remedy is another cluster member. Microsoft also recommends separate gateways for Import and DirectQuery — a second estate, not a second service. See EPC Group’s Power BI gateway guidance.
2. Capacity overage. Capacity overage (preview) prevents throttling by paying off excess usage — and Azure bills it at three times pay-as-you-go rates. Keep the rolling 24-hour limit below one-third of daily CU hours; beyond that you are paying more than a scale-up costs. Overage limits also consume Fabric quota at 1/24th of the limit set.
3. Dev/test capacity. Production capacity should not carry development load. Standard patterns: one production F SKU plus a smaller capacity paused outside business hours, or two right-sized F SKUs. Never split a capacity already near 100% utilisation — that manufactures overloads on both halves.
4. Purview and governance tooling. Sensitivity labels, DLP, catalogue, and audit evidence are licensed and operated separately. Budget the operating effort as well as the licence — see best data governance consulting firms.
5. Storage and networking. A reservation covers capacity usage only. Storage and networking are charged at pay-as-you-go rates regardless, and the discount applies hourly with no carry-forward — unused reserved hours are lost, not banked.
6. Report Server. Entitlement after P SKU retirement comes from a Fabric capacity reservation or SQL Server Enterprise Edition with Software Assurance. Pay-as-you-go F capacity does not carry it. Verify before cancelling the P SKU; the key then sits on the Fabric capacity tab under Capacity settings.
Pay-as-you-go versus reservation
Reservations are bought in one-CU increments for one or three years, scoped to an Azure region. Microsoft states the saving as approximately 41% against pay-as-you-go.
Four rules decide the answer:
- Reserve only measured baseline. The discount applies hourly and does not carry over; a reservation larger than your running capacity wastes the excess every unmatched hour.
- Reserve after stabilising. Track spend daily for 30 days with Microsoft Cost Management, then reserve the floor.
- Reservations remove pause/resume value. If capacity genuinely idles overnight, pausing pay-as-you-go may beat reserving 24/7. Model both.
- Reservations do not auto-renew unless set to. On expiry, workloads continue and quietly revert to pay-as-you-go rates.
What breaks — failure modes
| Symptom | Root cause | Fix |
|---|---|---|
| Viewers hit a licence wall despite the org owning capacity | Capacity is below F64; free viewer consumption starts at F64 | Scale to F64+, or licence viewers with Pro. There is no third option |
| Reports go dark 91 days after an agreement ends | P SKU cancelled without an F SKU in place: 30-day grace, throttled days 31–90, all operations rejected from day 91 | Buy the F SKU first, reassign and validate workspaces, then cancel the P SKU |
| Azure bill spikes with no capacity resize | Capacity overage active and billing at 3× pay-as-you-go | Set the rolling 24-hour overage limit below one-third of daily CU hours; scale up instead |
| Reservation bought, invoice barely moves | Reservation exceeds running capacity, or spend is storage/networking which the reservation never covered | Re-size the reservation to measured baseline; price storage separately |
| PPU content invisible to the wider business | PPU content can only be consumed by other PPU users unless it sits on capacity | Move the workspace to F64+, or licence the audience with PPU |
| Report Server stops being licensed post-migration | Entitlement now requires a Fabric capacity reservation or SQL Server EE with Software Assurance | Confirm entitlement before cancelling the P SKU; retrieve the key from the Fabric capacity tab |
| Capacity sized to headcount, throttles in week one | Sizing done on user counts rather than measured CU consumption | Baseline 30–45 days in the Fabric Capacity Metrics app, then size |
| Autoscale policy fails to carry over from P to F | Autoscale does not exist on F SKUs | Use on-demand resizing, pause/resume, and a bounded overage limit |
What changed in 2026
- P SKU retirement moved from advisory to operational. Microsoft no longer sells new P SKUs, and customers with expiring Enterprise Agreements or Microsoft Cloud Agreements cannot add or renew P capacity. Migration is manual — Fabric does not decommission the P SKU when you provision an F SKU.
- The retirement now has teeth with dates attached: 30-day grace, throttled interactive access days 31–90, all operations rejected from day 91 until you migrate or delete the capacity.
- Capacity overage (preview) replaced Autoscale as the surge mechanism on F SKUs, with an explicitly published 3× billing multiplier and an admin-set rolling 24-hour limit.
- Embedded consolidated into F. Power BI Embedded is included with every F SKU, removing the separate EM/A purchase for organisations moving to Fabric. Existing EM and A SKUs remain valid.
- Sovereign clouds are carved out. Fabric is not yet available there, so P SKUs remain supported in those environments pending separate guidance.
- The April 2025 per-user price change is now fully through the renewal cycle, so 2026 renewals are the first at steady state. Separately, monthly billing on annual-term subscriptions carries a 5% premium over annual upfront billing.
Frequently asked questions
How much does Power BI Pro cost in 2026?
Power BI Pro is $14.00 per user per month on annual billing, as published at time of writing (July 2026) on Microsoft's Power BI pricing page. The price changed on 1 April 2025 for new and renewing customers. Monthly billing on an annual-term subscription carries a 5% premium over paying annually upfront.
How much does Power BI Premium Per User cost?
Premium Per User is $24.00 per user per month on annual billing, as published at time of writing (July 2026). PPU includes all Power BI Pro capabilities, so a PPU user does not also need a Pro licence. PPU content can only be consumed by other PPU users unless it is hosted on a Fabric or Premium capacity.
Is Power BI Premium being discontinued?
Power BI Premium per-capacity SKUs (P1–P5) are being retired at the end of each customer’s current agreement term, and Microsoft no longer sells new ones. Premium Per User is a separate per-user licence and is not being retired. Fabric F SKUs are the replacement for per-capacity Premium.
What happens if my P SKU expires before I migrate?
Content stays accessible for a 30-day grace period. From day 31 to day 90 access is throttled and interactive operations are delayed. From day 91 all operations are rejected. Your data is retained but inaccessible until you migrate the workspaces to a Fabric F SKU or delete the capacity.
Which Fabric SKU lets free users view reports?
F64 and above. On F64 or larger capacity, users with only a Fabric Free licence and the Viewer role can view Power BI content. On any capacity below F64, and on Power BI Embedded A SKUs, each viewer needs a Pro or Premium Per User licence.
How do I calculate whether F64 is cheaper than Power BI Pro?
Divide your quoted monthly F64 cost by the $14.00 Pro price. The result is the viewer count at which capacity becomes cheaper. Authors need Pro on either option, so they cancel out of the comparison. Above the break-even, buy capacity; below it, buy Pro licences.
Which F SKU replaces my P SKU?
Map by capacity units at eight CUs per v-core: P1 becomes F64, P2 becomes F128, P3 becomes F256, P4 becomes F512, and P5 becomes F1024. Treat that as a starting point, then right-size against 30 to 45 days of measured consumption in the Fabric Capacity Metrics app.
How much do Fabric capacity reservations save?
Microsoft states approximately 41% against pay-as-you-go for a one- or three-year Fabric capacity reservation. The discount applies hourly to matching capacity and does not carry over, so reserve only your measured baseline. Reservations do not cover storage or networking charges and do not renew automatically unless configured to.
What is capacity overage and what does it cost?
Capacity overage prevents throttling by automatically paying off excess usage up to a limit the capacity admin sets. Azure bills overage at three times pay-as-you-go rates. Microsoft recommends keeping the rolling 24-hour limit below one-third of your daily CU hours, since above that point scaling up the SKU costs about the same.
Do I still need Power BI Embedded A SKUs?
Power BI Embedded is included with every Fabric F SKU, so organisations on F capacity do not need separate EM or A SKUs for embedding. Existing A and EM SKUs are not part of the P SKU retirement and remain valid. Note that A SKUs do not support free-licence viewing at any size.
How is Power BI Report Server licensed after the P SKU retirement?
Report Server entitlement comes from a Fabric capacity reservation or from SQL Server Enterprise Edition with Software Assurance. Verify your entitlement before cancelling a P SKU subscription. After migration the Report Server key is available on the Fabric capacity tab under Capacity settings in the admin portal.
Where EPC Group fits
EPC Group has run Microsoft data platform commercial modelling since 1997 — 29 years, six Microsoft Solutions Partner designations, 11,000+ engagements, six consecutive G2 Leader quarters. Errin O’Connor, Founder and Chief AI Architect, is a 4× Microsoft Press bestselling author.
Related reading: Power BI consulting services · Power BI cost and licensing guide · Power BI Premium vs Premium Per User · Power BI Premium · Microsoft Fabric consulting services · Fabric consulting guide · Microsoft Fabric vs Databricks · Snowflake to Fabric migration · Power BI vs MicroStrategy · Microsoft 365 E3 vs E5 · Microsoft 365 Copilot pricing and licensing · Top Power Platform consulting firms · Power BI consulting in Houston · Power BI consulting in Phoenix · Microsoft Frontier Company.
Get the model run against your numbers
Bring your user population, Azure region, and renewal date. EPC Group runs the Five-Layer Cost Stack and the break-even formula against your actual quote, and returns a sized recommendation with the arithmetic shown. Start at Power BI consulting services.
Sources and verification
- Microsoft — Power BI pricing (Pro and PPU list prices, annual billing) — https://www.microsoft.com/en-us/power-platform/products/power-bi/pricing
- Microsoft Learn — Understand Microsoft Fabric licenses (SKU/CU table, F64 free-viewer rule) — https://learn.microsoft.com/en-us/fabric/enterprise/licenses
- Microsoft Learn — Power BI Premium to Microsoft Fabric migration overview — https://learn.microsoft.com/en-us/power-bi/support/premium-migration-overview
- Microsoft Learn — P SKU to F SKU migration decision guide (retirement timeline, P→F mapping) — https://learn.microsoft.com/en-us/power-bi/support/premium-migration-decision-guide
- Microsoft Learn — Premium to Fabric migration FAQ (PPU not retired, EM/A out of scope) — https://learn.microsoft.com/en-us/power-bi/support/premium-migration-faq
- Microsoft Learn — Migrate workspaces from Power BI Premium to Microsoft Fabric — https://learn.microsoft.com/en-us/power-bi/support/premium-migration-how-to
- Microsoft Learn — Capacity overage (preview) in Microsoft Fabric (3× billing, CU hours/day) — https://learn.microsoft.com/en-us/fabric/enterprise/capacity-overage-overview
- Microsoft Learn — Save costs with Microsoft Fabric Capacity reservations — https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/fabric-capacity
- Microsoft Learn — Plan your capacity size (CU per SKU, 30-second evaluation period) — https://learn.microsoft.com/en-us/fabric/enterprise/plan-capacity
- Microsoft Learn — The Fabric throttling policy — https://learn.microsoft.com/en-us/fabric/enterprise/throttling
- Microsoft Learn — Capacity and SKUs in Power BI embedded analytics (A SKU behaviour, 25 GB model limit) — https://learn.microsoft.com/en-us/power-bi/developer/embedded/embedded-capacity
- Microsoft Learn — Direct Lake overview (per-SKU guardrails and max memory) — https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview
- Microsoft Learn — Partner Center March 2025 announcements (1 April 2025 price change, 5% monthly premium) — https://learn.microsoft.com/en-us/partner-center/announcements/2025-march
- Microsoft Learn — Power BI service features by license type — https://learn.microsoft.com/en-us/power-bi/fundamentals/service-features-license-type
- Microsoft Learn — Troubleshoot the on-premises data gateway (30 concurrent refresh limit) — https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-tshoot
- Microsoft Azure — Microsoft Fabric pricing (pay-as-you-go and reservation, regional variance) — https://azure.microsoft.com/en-us/pricing/details/microsoft-fabric/
- Microsoft Learn — Microsoft Fabric capacity planning guide — https://learn.microsoft.com/en-us/fabric/enterprise/capacity-planning-manage-capacity-growth-governance