Microsoft Fabric vs Power BI Premium
These aren't really two competing products to choose between — Fabric capacity is the successor to Premium capacity, licensing the same underlying resource for a broader set of workloads. The confusion is real, so here's what actually changed.
At a glance
| Dimension | Power BI Premium | Fabric |
|---|---|---|
| What it licenses | Power BI content only — reports, paginated reports, dataflows Gen1, dedicated capacity for AI visuals | Every workload on the same capacity: Power BI, Spark, Warehouse, Lakehouse, Data Factory pipelines, Real-Time Intelligence, Data Science |
| SKU naming | P1–P5 (and EM1–EM3 on the embedded tier) | F2–F2048, sized in Capacity Units |
| Underlying resource | A Power BI-only capacity | The same class of capacity, broadened to license every Fabric engine |
| New purchases | No longer sold as a new capacity — see below | The current way to buy this tier of compute |
| Free viewing threshold | P1 and above | F64 and above (same tier, renamed) |
Full P-SKU-to-F-SKU mapping, CU counts, and per-tier pricing are in the capacity SKU reference.
What actually changed
- Same infrastructure, wider license. A Fabric F64 capacity isn't a different machine from a Premium P1 capacity — it's the same tier of shared capacity, licensed to run Spark notebooks, a T-SQL Warehouse, Data Factory pipelines, and Real-Time Intelligence alongside Power BI, instead of Power BI alone.
- Nothing you built stops working. Reports, semantic models, and refresh schedules on an existing Premium capacity keep running. The renaming and licensing shift doesn't retroactively touch content that's already there.
- The purchasing path moved. New capacity purchases go through Fabric SKUs now rather than standalone Premium SKUs — see the FAQ for what that means at your next renewal.
Should you turn on the rest of Fabric?
Owning an F SKU doesn't obligate you to use Spark or the Warehouse — if Power BI is the only workload today, an F-SKU capacity licenses that exactly the way Premium did, at the equivalent tier. The difference is optionality: the same capacity can pick up a lakehouse or a pipeline later with no new purchase, which is worth knowing about even if you don't need it on day one. Model what a given workload would actually cost in CUs before turning anything on, using the CU cost calculator.
FAQ
Can I still buy Power BI Premium capacity?
Microsoft's direction has been to fold Premium capacity purchasing into Fabric — new P-SKU capacity purchases are no longer the path forward, and F SKU is what you buy instead. Licensing terms like this do shift over time, so confirm current purchase options in the Microsoft admin/licensing portal rather than assuming this page is still current months from now.
What happens to a Premium capacity I already own?
It keeps working. Nothing about your existing reports, refresh schedules, or capacity assignment breaks on its own. The practical question is what your capacity looks like at renewal — plan on moving to the equivalent Fabric F SKU (P1 to F64, P2 to F128, and so on) rather than assuming the P SKU renews indefinitely.
Do I need Fabric if I'm not using Spark, Warehouse, or pipelines?
Not for the workload itself — if every workspace on the capacity is pure Power BI content, a Fabric capacity licenses that exactly the same way Premium did. What you gain is the option to turn on other Fabric engines later on the same capacity without buying anything new, not a requirement to use them.
Is Premium Per User (PPU) affected too?
PPU is a separate, per-seat license from capacity SKUs, aimed at smaller Power BI-only deployments that don't need a shared capacity at all. Whether it's on the same purchasing path as P-SKU capacity has been changing — check current PPU availability in your tenant's licensing terms rather than assuming this page tracks it in real time.