What is happening. Microsoft is consolidating purchase options for Power BI Premium per-capacity by retiring P SKUs (P1 through P5) in favour of Microsoft Fabric F SKUs (F2 through F2048). The retirement is gradual but the direction is unambiguous. Most Power BI Premium customers will migrate at next renewal in 2026 or 2027.
What changes commercially. F SKUs span a wider range allowing more granular sizing. F64 is the threshold that eliminates per-user Power BI Pro requirements for viewers (equivalent to P1 in this respect). F SKUs also include full Fabric platform capabilities — Synapse Data Warehouse, Data Engineering, Data Factory, Real-Time Intelligence, Data Science.
What to do. Use the migration as EA negotiation leverage. Microsoft account teams have aggressive Fabric attach quotas. The mandatory migration to F SKUs creates a moment where Microsoft will exchange favourable Fabric pricing for broader EA commitments. The right time to negotiate is during EA renewal, not as a separate post-renewal transaction.
What Microsoft is retiring and what replaces it
Power BI Premium per-capacity SKUs were introduced as Microsoft’s premium Power BI offering for organisations needing capacity-based licensing rather than per-user licensing. P1, P2, P3, P4, and P5 SKUs covered capacity tiers from approximately 8 v-cores to 128 v-cores. For organisations with large Power BI viewer populations, capacity-based P SKUs eliminated the need for per-user Power BI Pro licences for content consumers (only content creators required Pro).
Microsoft Fabric, launched in 2023 and matured through 2024-2025, provides a unified data and analytics platform. Power BI is one capability within Fabric; the platform also includes Synapse Data Warehouse, Data Engineering (Spark), Data Factory, Real-Time Intelligence, and Data Science. Fabric F SKUs span F2 through F2048 capacity sizes, providing broader granularity than P SKUs.
The retirement direction: Microsoft has indicated that new P SKU sales are being discouraged and that existing P SKU customers will be encouraged to migrate to F SKUs at next renewal opportunity. Hard end-of-life dates have not been committed publicly, but the trajectory is clear.
P SKU to F SKU capacity mapping
| P SKU | Capacity equivalent | Approximate F SKU |
|---|---|---|
| P1 | ~8 v-cores | F64 |
| P2 | ~16 v-cores | F128 |
| P3 | ~32 v-cores | F256 |
| P4 | ~64 v-cores | F512 |
| P5 | ~128 v-cores | F1024 |
The mapping is approximate. F SKUs provide finer granularity (F2 to F2048) than the P SKU set, allowing more precise capacity sizing. For organisations whose current P SKU is meaningfully over-provisioned relative to actual usage, the F SKU mapping is an opportunity to right-size capacity rather than directly substitute.
The F64 threshold matters
The single most commercially significant fact about F SKUs is that F64 is the threshold at which per-user Power BI Pro requirements for viewers are eliminated. Below F64 (F2, F4, F8, F16, F32), content viewers still require Power BI Pro licences. At F64 and above, viewers are covered by the capacity subscription — no per-user licence needed.
For organisations with large Power BI viewer populations, F64 is the minimum F SKU that delivers the per-user licensing benefit. Below F64, F SKUs cost less but require continuing per-user Pro investment. Above F64, F SKUs cost more but eliminate the per-user cost.
The economic crossover varies by viewer count. For organisations with 200+ Power BI viewers, F64 is typically cheaper in total cost than F32 plus per-user Pro for the viewers. For organisations with fewer viewers, the math is closer.
What Fabric adds beyond Power BI Premium
The F SKU subscription includes the full Microsoft Fabric platform, not just Power BI Premium equivalent. The additional capabilities:
- Synapse Data Warehouse. Cloud data warehouse with SQL endpoint, OneLake storage integration, and unified governance.
- Data Engineering. Spark-based data processing for large-scale data transformation.
- Data Factory. ETL/ELT data pipelines integrating across the Microsoft data ecosystem.
- Real-Time Intelligence. Event processing, streaming analytics, time-series analysis.
- Data Science. Machine learning notebook environment, model training, and deployment.
- OneLake unified storage. Single data lake spanning all Fabric workloads.
For organisations already using or planning to use any of these capabilities — particularly Synapse, Data Factory, or Real-Time Intelligence — the F SKU subscription provides them at no incremental cost beyond the capacity. For Power-BI-only organisations, the additional capabilities exist but are unused.
Using the migration as EA negotiation leverage
The mandatory P-to-F migration creates a commercial opportunity that procurement teams should exploit. Three negotiation tactics apply.
Tactic 1: Time the migration with EA renewal
Microsoft account teams have aggressive Fabric attach quotas. When the EA renewal is in play, the account team will exchange favourable Fabric terms for broader EA commitments — multi-year term, Azure consumption co-commit, Copilot attach. Timing the Fabric migration to coincide with EA renewal captures the bundled discount opportunity.
Tactic 2: Negotiate F SKU pricing as part of EA
Fabric capacity is procurable through EA as a committed capacity, through Azure pay-as-you-go consumption, or through both in combination. The committed capacity through EA is negotiable in pricing; PAYG consumption is at published rates. For predictable baseline capacity, committed pricing through EA captures negotiated discount; for variable overage, PAYG provides flexibility. The right mix is organisation-specific.
Tactic 3: Right-size as part of migration
Many organisations on P SKUs are over-provisioned relative to actual usage — sometimes by 30-50% of capacity. The F SKU finer granularity allows downsizing to actual need. Microsoft account teams will sometimes accept right-sizing during migration that they would resist outside the migration window. The migration is the moment to make capacity adjustments.
Migration action plan
- Inventory current P SKU usage. Document current P SKU tier, actual capacity utilisation, and Power BI viewer/creator counts.
- Map to appropriate F SKU. Direct mapping per table above, then adjust for actual utilisation. F64 threshold matters for organisations with large viewer populations.
- Time migration with EA renewal if possible. Bundles the Fabric commercial into the EA negotiation for better terms.
- Decide on committed vs PAYG mix. Committed for baseline, PAYG for variable overage typical. Specific mix depends on usage patterns.
- Engage independent advisory. The migration commercial decisions are material. Book a scoping call.