Microsoft Licensing Intelligence

Microsoft Fabric Licensing: Complete Enterprise Guide 2026

Last reviewed: 2024-12-25 · Microsoft Negotiations

Microsoft Negotiations · Est. 2016 · 500+ Engagements · $2.1B Managed

Microsoft Fabric is the most significant restructuring of Microsoft's analytics licensing in a decade. Launched in May 2023 and now generally available, Fabric consolidates Power BI, Azure Data Factory, Azure Synapse Analytics, Azure Data Lake Storage, and Azure Databricks-equivalent workloads into a single SaaS capacity model. The licensing model is genuinely simpler than what it replaces — but simplicity at the SKU level hides significant complexity in capacity sizing, per-user requirements, storage billing, and the P-SKU-to-F-SKU migration that Microsoft is actively driving. Getting this wrong costs $200,000–$800,000/year at enterprise scale.

Independent Advisory. Zero Vendor Bias.

500+ Microsoft EA engagements. $2.1B in managed spend. 32% average cost reduction. We negotiate on your behalf — never Microsoft's.

View Advisory Services →

Microsoft Fabric & Power BI Licensing Guide Series

▶ Microsoft Fabric Licensing: Complete Enterprise Guide (this page) Microsoft Fabric Capacity Planning: F SKU Sizing Guide Microsoft Fabric vs Power BI Premium: Migration Decision Guide OneLake Licensing & Storage Cost Optimisation Fabric F SKU vs P SKU: Full Comparison Synapse Analytics vs Microsoft Fabric: Migration Guide

What Microsoft Fabric Actually Is — And Why It Changes Licensing

Before 2023, enterprise analytics on Microsoft required buying separate services: Power BI Premium for reporting, Azure Data Factory for ETL, Azure Synapse for data warehousing and Spark, Azure Data Lake Storage for data storage, and potentially Azure Databricks for advanced analytics. Each service had separate licensing, separate pricing, separate capacity management, and separate billing.

Microsoft Fabric collapses all of these into a single capacity model. Buy one Fabric capacity (measured in Capacity Units — CU), and that capacity runs Fabric workloads across all components: Data Factory (pipelines), Data Engineering (Spark/Notebooks), Data Warehouse (T-SQL), Real-Time Intelligence (KQL/Eventstream), Power BI (reports/dashboards), and Data Science (ML experiments). One licence, one billing metre, one capacity pool.

The Fabric Workload Components

Fabric WorkloadPrevious EquivalentWhat It DoesCapacity Consumption Pattern
Data FactoryAzure Data Factory / SSISETL/ELT pipelines, data integrationCompute-heavy during pipeline runs
Data Engineering (Lakehouse)Azure Synapse Spark / Azure DatabricksSpark-based data transformation, notebooksBurst during batch jobs
Data WarehouseAzure Synapse Analytics (SQL Pool)Serverless T-SQL queries over OneLake dataQuery-driven; smooths out over time
Real-Time IntelligenceAzure Data Explorer / Stream AnalyticsKQL queries, Eventstream ingestion, real-time dashboardsContinuous low-level consumption
Power BIPower BI PremiumReports, dashboards, semantic models, paginated reportsBurst during report refresh; continuous for DirectQuery
Data ScienceAzure Machine LearningML experiments, model training, feature storesBurst during model training runs
Data ActivatorNo direct equivalentEvent-triggered actions from data changesLow, event-driven

The key insight is that Fabric capacity is a shared pool. When your Spark jobs run heavy batch transforms overnight, that capacity is available for interactive Power BI queries during business hours. This temporal sharing allows organisations to run more workloads on less capacity than buying separate services — but it also means that unexpected capacity contention between workloads is the primary operational headache.

The Fabric Licensing Model: F SKUs, P SKUs, and Per-User Options

F SKU — The Primary Fabric Licensing Path

F SKUs are Azure resources — you purchase Fabric capacity through the Azure portal (or ARM templates, Terraform). They are measured in Compute Units (CU) and available in sizes from F2 (2 CU) to F2048 (2,048 CU). F SKUs have two purchasing modes:

F SKU SizeCU CountPay-as-you-go ($/hour)1-Year Reserved3-Year ReservedPower BI Premium Equivalent
F22$0.36$0.25$0.19— (no P equivalent)
F44$0.72$0.50$0.38— (no P equivalent)
F88$1.44$1.00$0.76— (no P equivalent)
F1616$2.88$2.00$1.52— (no P equivalent)
F3232$5.76$4.00$3.04— (no P equivalent)
F6464$11.52$8.00$6.08≈ P1 equivalent
F128128$23.04$16.00$12.16≈ P2 equivalent
F256256$46.08$32.00$24.32≈ P3 equivalent
F512512$92.16$64.00$48.64≈ P4 equivalent
F10241,024$184.32$128.00$97.28≈ P5 equivalent
F20482,048$368.64$256.00$194.56

At 3-year reserved pricing, an F64 costs approximately $4,370/month ($0.0608/hour × 720 hours × 100% uptime — though you can pause it during non-use periods, reducing effective monthly cost to $2,000–$3,000 for typical enterprise workloads with overnight/weekend pauses).

P SKU — The Legacy EA Path

P SKUs (P1–P5) were the original Power BI Premium capacity model, available only through Microsoft EA. With the introduction of Fabric, Microsoft is migrating customers from P SKUs to F SKUs. Key differences:

DimensionP SKUs (P1–P5)F SKUs (F64–F1024)
ProcurementMicrosoft EA onlyAzure Portal / EA / MACC
BillingMonthly flat rate via EA invoiceHourly (PAYG), monthly (reserved)
Pause/ResumeCannot pauseCan pause (stop billing when idle)
MACC eligibleNoYes
Price vs equivalentP1: $4,995/monthF64 3-yr reserved: ~$3,200/month
Full Fabric workloadsYes (since Fabric launch)Yes
Future directionBeing phased outStrategic direction

If you are on a P SKU EA today, Microsoft will eventually require migration to F SKUs. The migration path is not disruptive technically (workspaces and reports migrate), but it requires modifying the EA or creating new Azure reservations. Begin planning this migration at your next EA renewal — do not allow Microsoft to auto-renew P SKU terms; use the renewal as the opportunity to convert to F SKU reserved pricing.

Power BI Premium Per User (PPU)

PPU at $20/user/month is the entry point for individuals who need Fabric features without purchasing a full capacity. PPU users get access to all Fabric workloads and Power BI Premium features scoped to their own workspaces. Reports shared from PPU workspaces require the consumer to also have PPU (or a full Fabric capacity).

PPU is the right choice for: data teams of 5–20 people who need Fabric data engineering capabilities but don't yet have broad report distribution requirements. It is not the right choice at 50+ users — the cost ($20 × 50 = $1,000/month) is competitive with an F8 capacity ($0.50/hour × 720 = $360/month on 1-year reserved) that serves unlimited users for consumption.

Get an Independent Second Opinion

Before you commit to Microsoft Fabric capacity or migrate from Power BI Premium, speak with an adviser who has no commercial relationship with Microsoft.

Request a Consultation →

Per-User Licensing Requirements

Fabric capacity does not eliminate per-user licensing requirements. Content creators and collaborators in Fabric need either a Power BI Pro licence ($10/user/month), a PPU licence ($20/user/month), or an M365 E5 subscription (which includes Power BI Pro). Report consumers — users who only view content without creating or editing — can consume from a Fabric capacity without a per-user licence.

User RoleMinimum Licence RequiredMonthly CostNotes
Report Consumer (view only)None (if capacity is F/P SKU)$0Capacity covers consumption; this is Fabric's biggest advantage over per-user models
Report Creator (build reports)Power BI Pro or PPU$10 or $20/monthPro sufficient for most creators if capacity is F64+
Lakehouse/Warehouse EngineerPower BI Pro or PPU$10 or $20/monthPPU required if using PPU-only capacity; Pro sufficient on F/P capacity
Data Scientist (Notebooks)Power BI Pro or PPU$10 or $20/monthSame as engineer
Fabric AdministratorPower BI Pro + admin role$10/monthAdmin role is Azure AD-based; no additional licence cost
External Guest (B2B)Pro in home tenant or consuming tenant capacityVariesAzure AD B2B; licence in home tenant typically covers viewing

The critical implication: in a large enterprise with 2,000 report consumers and 100 report creators, you pay the capacity cost once ($5,000–$10,000/month for F64/F128) plus $10 × 100 = $1,000/month for creators. Total: $6,000–$11,000/month. The same organisation on Power BI Pro (no capacity) pays $10 × 2,100 = $21,000/month. Fabric capacity with F SKU breaks even at approximately 120–150 total users depending on SKU size.

OneLake: The Storage Billing Layer

OneLake is Fabric's unified storage layer — a single Azure Data Lake Storage Gen2-compatible data lake that all Fabric workloads share. Storage in OneLake is billed separately from Fabric capacity at $0.023/GB/month for LRS (locally redundant) or $0.046/GB/month for GRS (geo-redundant). Data movement into OneLake (ingestion) is free; reads and queries consume capacity, not storage billing.

For the full storage cost model and optimisation strategies, see our OneLake licensing and storage cost guide.

Fabric Capacity Sizing Decision Framework

Sizing Fabric capacity correctly is the most consequential licensing decision. Too small and you face performance degradation and throttling; too large and you overspend. The decision framework:

Organisation TypeUsersPrimary WorkloadRecommended Starting SKUMonthly Cost (3-yr reserved)
Small BI team, no Spark50–200 consumers, 10–20 creatorsPower BI reports, Dataflows Gen2F64~$2,500–3,200
Mid-market analytics200–1,000 consumersPower BI + some LakehouseF128~$5,000–6,400
Enterprise BI + moderate ETL1,000–5,000 consumersPower BI Premium replacement + Data FactoryF256~$10,000–12,800
Enterprise data platform5,000+ consumers + engineering teamFull data platform — Lakehouse, Warehouse, BIF512 or 2×F256~$20,000–28,000
Individual/small team exploration1–50 usersDevelopment and prototypingPPU ($20/user/month)$200–1,000

These are starting points. Right-sizing Fabric requires telemetry — the Fabric Capacity Metrics App (free, from AppSource) provides per-workload CU consumption data. Run it for 2–4 weeks on trial capacity before committing to reserved pricing. For detailed sizing methodology, see our Microsoft Fabric capacity planning guide.

Fabric vs Power BI Premium: The Migration Decision

For organisations currently on Power BI Premium P SKUs, the migration to Fabric F SKUs is inevitable — but timing matters for cost optimisation. The core comparison:

The full migration analysis is covered in our Microsoft Fabric vs Power BI Premium comparison guide.

Microsoft Fabric EA Negotiation Strategy

Fabric sits at the intersection of Microsoft's data platform (Azure) and productivity (M365) negotiation tracks. This gives buyers more leverage than either track alone. The negotiation principles:

Lever 1 — Reserved Capacity vs EA P SKU

Microsoft's EA account teams will default to quoting P SKUs because they're familiar EA line items. Always request F SKU pricing. The 3-year reserved F64 at ~$3,200/month vs P1 at $4,995/month is a $21,540/year difference on a single capacity — the numbers are self-evidently in your favour. Microsoft will try to maintain P SKU pricing by emphasising "simplicity" and "EA-friendly billing." Push back: F SKU via Azure Reserved Instances with an EA subscription is equally manageable.

Lever 2 — MACC Linkage for F SKU Burn

F SKU capacity purchased via Azure counts toward MACC (Microsoft Azure Consumption Commitment) burn. If your organisation has an Azure MACC commitment, structuring Fabric capacity as F SKU via Azure converts your analytics platform cost into committed Azure spend — effectively giving you Azure EA discounts (typically 15–30%) on top of the 3-year reserved discount. This is available only with F SKUs, not P SKUs.

Lever 3 — Competitive Alternatives

Databricks (Unity Catalog + Delta Lake) is the primary competitive alternative for the data engineering and warehousing components of Fabric. Snowflake competes on data warehousing. Google BigQuery and AWS Redshift compete on analytics. Documenting a credible migration path to Databricks or Snowflake provides negotiating leverage on F SKU pricing. Microsoft's current discount ceiling for documented competitive situations is typically 25–35% below 3-year reserved list price.

Lever 4 — Power BI Pro Consolidation

If you're purchasing both Power BI Pro licences and Fabric capacity, negotiate them as a bundle. The combination of 200+ Pro licences + F64 capacity often unlocks bundle discounts of 10–15% on the Pro licence side. Microsoft wants to retain BI users on Power BI as organisations migrate analytics workloads to Fabric.

📄 Free Guide: Microsoft EA Negotiation Playbook

Full negotiation tactics for Azure, Fabric, and Microsoft 365 — including F SKU vs P SKU migration scripts and benchmarks.

Download Free Guide →

Fabric Trial and Proof-of-Concept Strategy

Microsoft offers a 60-day Fabric trial that includes F64-equivalent capacity. Use it strategically:

Synapse Analytics Migration to Fabric

Organisations running Azure Synapse Analytics (dedicated SQL pools, Spark pools) have a migration path to Fabric's Data Warehouse and Data Engineering workloads. The licensing implication: Synapse dedicated SQL pool pricing (from $1.51/DWU-hour) is often more expensive than equivalent Fabric Warehouse capacity for typical query patterns. Fabric Warehouse uses a serverless billing model — you pay CU consumption per query rather than for always-on dedicated pool capacity. See our Synapse Analytics vs Fabric licensing guide for the full migration framework.

Frequently Asked Questions

What is Microsoft Fabric and how is it licensed?

Microsoft Fabric is a unified analytics platform combining data engineering, data integration, data warehousing, real-time intelligence, and Power BI into a single SaaS service. It is licensed through Fabric Capacity — measured in Capacity Units (CU) — purchased as F SKUs (F2 through F2048) via Azure subscriptions, or P SKUs (P1–P5) via Microsoft EA.

What is the difference between F SKUs and P SKUs in Microsoft Fabric?

F SKUs are purchased through Azure (pay-as-you-go or reserved) and offer hourly billing, pause/resume capability, and MACC burn eligibility. P SKUs are purchased through Microsoft EA, billed monthly, cannot be paused, and are tied to the EA commitment period. F SKUs are almost always better for enterprises with Azure MACC commitments. P SKUs are gradually being deprecated in favour of F SKUs.

Does every user need a Microsoft Fabric licence?

Fabric creators and collaborators need either a Power BI Pro licence ($10/user/month), Power BI Premium Per User ($20/user/month), or Microsoft 365 E5. Power BI report consumers can view content shared from a Fabric capacity without a per-user licence — the capacity covers consumption.

What is OneLake and does it have separate licensing costs?

OneLake is Microsoft Fabric's unified storage layer. Storage in OneLake is charged separately from Fabric capacity at $0.023/GB/month (LRS). OneLake storage costs are billed through Azure and can count toward MACC commitments.

Can Microsoft Fabric replace Power BI Premium?

Yes, and Microsoft is actively migrating customers from Power BI Premium to Fabric. An F64 capacity provides equivalent Power BI Premium compute to a P1, at approximately 25–35% lower cost when purchased as Azure reserved capacity. The full Fabric capabilities are included at no additional licence cost.

Microsoft Licensing Intelligence — Weekly

Negotiation tactics, price movement alerts, and licensing analysis. Read by 4,000+ enterprise buyers.

Subscribe Free →

Related Microsoft Analytics & Data Licensing Guides