Microsoft Fabric Licensing & Pricing: The Complete Enterprise Guide

Microsoft Fabric launched in 2023 as a unified analytics platform that merges data engineering, data warehousing, data science, real-time analytics, and business intelligence under one roof. For enterprises already running Power BI Premium, Azure Synapse, or Azure Data Factory, Fabric represents both an opportunity and a licensing complexity that — if left unmanaged — will dramatically inflate your Microsoft spend.

This guide, part of our broader Microsoft Enterprise Agreement negotiation series, explains Fabric's capacity model, SKU tiers, OneLake storage pricing, and the negotiation levers available when Fabric appears in your EA or Azure MACC commitment. Whether you are evaluating Fabric for the first time or renewing an existing commitment, understanding these mechanics will save you millions.

What Is Microsoft Fabric and Why Does Licensing Matter?

Microsoft Fabric is a SaaS analytics platform built on top of Azure, delivered through a capacity-based licensing model. Unlike traditional per-user SaaS licences, Fabric charges for compute capacity — measured in Fabric Capacity Units (CUs) — and separate storage through OneLake. This model suits heavy analytical workloads but creates significant budget risk for enterprises that under-specify capacity, provision carelessly, or fail to negotiate capacity reservation discounts.

Fabric includes the following workloads within a single capacity: Power BI (including Premium features), Data Factory pipelines, Lakehouse, Data Warehouse, Real-Time Analytics (KQL), Data Science (notebooks and ML), and Data Activator. Organisations that previously licensed these individually through a mix of Power BI Premium, Azure Synapse, and Data Factory now have a pathway to consolidate — but Microsoft prices that consolidation premium.

Microsoft Fabric Capacity SKUs: F SKUs Explained

Fabric is purchased through Fabric Capacity SKUs, labelled F2 through F2048. The number refers to the number of capacity units (CUs). Microsoft sells these as Pay-As-You-Go reservations through the Azure portal, as reserved instances (1-year or 3-year), or bundled into an Azure MACC commitment.

SKU	Capacity Units (CUs)	Approx Monthly (PAYG)	1-Year Reserved Discount	3-Year Reserved Discount
F2	2 CUs	~$262	~23%	~37%
F4	4 CUs	~$524	~23%	~37%
F8	8 CUs	~$1,049	~23%	~37%
F16	16 CUs	~$2,097	~23%	~37%
F32	32 CUs	~$4,194	~23%	~37%
F64	64 CUs	~$8,389	~23%	~37%
F128	128 CUs	~$16,777	~23%	~37%
F256	256 CUs	~$33,554	~23%	~37%
F512	512 CUs	~$67,109	~23%	~37%
F1024+	1024+ CUs	Custom	Negotiable	Negotiable

Note: prices above are illustrative list prices and vary by region. Negotiated MACC pricing and EA discounts can reduce these significantly. For enterprises committing to F128 and above, custom reserved-instance pricing is available during EA negotiations.

Power BI Premium vs Fabric Capacity: The Migration Decision

Microsoft is progressively migrating Power BI Premium P SKUs to Fabric F SKUs. The equivalencies are approximate: a P1 SKU (~8 vCores) maps loosely to an F64. However, Fabric F SKUs include additional workloads beyond Power BI — data engineering, warehousing, and AI — which means the pure Power BI workload gets more capacity than it needs, inflating cost unless you actually use those additional services.

Before agreeing to a Power BI Premium → Fabric migration during an EA renewal, model your actual workload split. If 80% of your usage is Power BI and 20% is data engineering, negotiate based on that split rather than accepting Microsoft's default F-SKU recommendation. Microsoft's sales teams are incentivised to recommend F128 or higher to unlock the "enterprise" tier benefits — those benefits may not justify the cost premium.

OneLake Storage Pricing

Microsoft Fabric introduces OneLake, a unified data lake that underlies all Fabric workloads. OneLake storage is billed separately from capacity compute, at approximately $0.023 per GB per month (list price). While this appears modest, enterprises with large data estates — petabytes of raw, processed, and curated data — can accumulate significant OneLake storage bills that are separate from their EA or MACC commitments unless explicitly included.

OneLake Cost Management Best Practices

• Tiered storage governance: Establish retention policies that move cold data to cheaper tiers or delete it entirely. Unmanaged OneLake storage is one of the fastest-growing hidden costs in Microsoft environments.
• Delta format efficiency: Fabric's default storage format is Delta/Parquet, which is efficient. However, without compaction schedules, small file proliferation can double or triple effective storage consumption.
• Shortcut vs. copy decisions: OneLake Shortcuts allow you to reference data in Azure Data Lake Storage Gen2, Amazon S3, or Google Cloud Storage without copying it. Use shortcuts where possible to avoid redundant OneLake storage charges.
• MACC inclusion: Negotiate to include OneLake storage within your Azure MACC commitment rather than leaving it as a separate metered charge.

Fabric Licensing in the Enterprise Agreement Context

Microsoft Fabric capacity can be purchased as a standalone Azure service, but most enterprise customers will encounter it as part of their Enterprise Agreement or their Microsoft Azure Consumption Commitment (MACC).

EA Fabric Licensing Options

Within the EA, Microsoft increasingly bundles Fabric capacity within Microsoft 365 E5 suites or as an add-on to Power BI Premium. The key negotiation points within an EA context are:

• Reserved capacity discounts: 1-year reservations offer approximately 23% off PAYG; 3-year reservations offer approximately 37%. For predictable analytical workloads, these discounts are almost always justified.
• Bursting vs. baseline capacity: Fabric allows capacity bursting — consuming more CUs than reserved during peak periods, at PAYG rates. Negotiate a burst cap or ensure your baseline reservation covers peak loads, as uncapped bursting can create unpredictable month-end invoices.
• Multi-region capacity: If your organisation operates across multiple Azure regions, Microsoft may attempt to sell separate capacity reservations per region. Challenge this — Fabric capacity is global and workloads can be orchestrated to use a primary region for billing efficiency.
• Trial-to-commit transitions: Microsoft offers Fabric free trials (60 days). Enterprises that accept a trial without a negotiation strategy are in a weak position when Microsoft converts that trial to a paid commitment. Engage a negotiation advisor before the trial ends.

Fabric Licensing Under Microsoft 365 Copilot

Microsoft positions Fabric as the data backbone for Microsoft 365 Copilot. If your organisation is deploying Copilot for Power BI or Copilot for Data Factory — both of which require Fabric capacity — your Fabric requirements will scale proportionally with your Copilot deployment. This is a critical planning point: organisations that commit to Copilot licences without provisioning adequate Fabric capacity will face urgent (and expensive) reactive capacity purchases.

Microsoft's sales teams will use Copilot adoption as a lever to sell larger Fabric reservations. The counter-strategy is to pilot Copilot for analytics on a limited Fabric footprint, measure actual CU consumption, and right-size the reservation before committing to enterprise-wide deployment.

Fabric vs Azure Synapse: Should You Migrate?

Microsoft has announced that Azure Synapse Analytics will be gradually superseded by Microsoft Fabric. For enterprises with significant Synapse investments, the migration question is both technical and commercial:

• Synapse to Fabric migration is not free: While Fabric's Data Warehouse is a successor to Synapse SQL Pools, data migration, ETL pipeline rewrites, and workspace reconfiguration require material effort and cost.
• Support lifecycle: Microsoft has not announced a formal Synapse end-of-life date, but investment in Synapse is clearly declining. Enterprises on Synapse should plan a migration roadmap but avoid being rushed into Fabric commitments before they are technically ready.
• Cost arbitrage window: Negotiate Fabric capacity pricing while Synapse still has support. Once Synapse deprecation is announced, Microsoft's leverage increases significantly.

Key Negotiation Tactics for Microsoft Fabric

Our advisors at IT Negotiations have worked through dozens of Fabric licensing negotiations. The following tactics consistently produce the best outcomes:

1. Demand Independent Workload Sizing

Microsoft's pre-sales engineers will run a sizing assessment to recommend your Fabric SKU tier. These assessments are not independent — they are optimised to sell larger SKUs. Before accepting any Microsoft SKU recommendation, commission an independent workload assessment that maps your actual data volumes, query frequency, concurrency requirements, and growth projections to minimum-viable Fabric CUs.

2. Benchmark Against Azure Databricks

Microsoft Fabric competes directly with Azure Databricks for data engineering and ML workloads. Databricks is available on Azure Marketplace and can be purchased via MACC. Actively benchmarking Fabric against Databricks — and communicating that comparison to Microsoft — creates genuine competitive pressure that drives Fabric discounts.

3. Leverage MACC Flexibility

If your organisation has an Azure MACC, push to include Fabric capacity reservations within the MACC drawdown. This prevents separate invoice streams, applies MACC discounts to Fabric, and gives you flexibility to reallocate committed spend if Fabric consumption is lower than forecast.

4. Negotiate Burst Caps

Fabric's capacity bursting is billed at PAYG rates, which are 23–37% more expensive than reserved rates. If your workloads are variable, negotiate a burst cap or a burst rate discount within your Enterprise Agreement. Without a cap, a single poorly-written query that runs uninterrupted overnight can generate an invoice surprise.

5. Phase Commitments

If you are new to Fabric, resist Microsoft's push for a multi-year capacity reservation in year one. Negotiate a one-year commitment at reserved rates, with an option to lock in multi-year pricing at a guaranteed discount after your first year of usage data. This protects you from over-committing on a platform your teams are still learning to optimise.

Common Fabric Licensing Mistakes

• Accepting Microsoft's default SKU recommendation without independent sizing validation — typically 1–2 tiers too large.
• Ignoring OneLake storage costs in TCO calculations — storage can represent 20–30% of total Fabric cost at scale.
• Allowing trial periods to expire without a negotiation strategy — Microsoft has maximum leverage at trial expiry.
• Bundling Fabric into a Power BI Premium renewal without explicitly negotiating the Fabric component — Power BI licensing teams and Fabric licensing teams are separate, and renewal reps often conflate the two.
• Skipping burst governance — failing to implement capacity guardrails (auto-pause, workspace throttling) that prevent uncontrolled CU consumption by ad-hoc users.
• Not evaluating Fabric within the broader Microsoft stack strategy — Fabric licensing decisions should be made in the context of your EA structure, MACC, and M365 licence tier.

Fabric Licensing FAQ

Is Microsoft Fabric included in Microsoft 365 E3 or E5?

Microsoft Fabric capacity is not included in Microsoft 365 E3 or E5 user licences. Fabric requires separate capacity reservation. However, Power BI Pro (included in M365 E3/E5) does allow users to access reports hosted on Fabric capacity — you still need to pay for the capacity itself.

Can I use Fabric capacity with Power BI Embedded?

Yes. Power BI Embedded workloads can run on Fabric capacity (F SKUs), which simplifies licensing for ISVs and enterprises building embedded analytics products. The pricing economics are generally more favourable on F SKUs versus legacy EM/A SKUs.

How does Fabric count against my MACC?

Fabric reserved capacity can be structured to drawdown against your Azure MACC, provided the reservation is purchased through the Azure portal under the same subscription hierarchy as your MACC commitment. Confirm this structure with Microsoft in writing before signing any Fabric reservation.

What happens to Power BI Premium A SKUs?

Power BI Premium A SKUs (used for embedded scenarios) are being replaced by Fabric F SKUs. Microsoft has not set a hard retirement date, but new A SKU capacity is no longer available for purchase in most regions. Existing A SKU customers should engage Microsoft on a migration timeline that includes pricing protections.

Summary: Fabric Licensing Principles for Enterprise Buyers

Microsoft Fabric is a compelling analytics platform, but its capacity-based pricing model creates material risk for enterprises that fail to manage it actively. The most important principles:

• Independent workload sizing before any SKU commitment
• Reserved capacity over PAYG for predictable workloads
• MACC inclusion to leverage existing Azure committed spend
• Burst caps and workspace governance to prevent surprise charges
• OneLake storage governance as a parallel cost stream
• Competitive benchmarking (Databricks, Snowflake) to maintain negotiation leverage

IT Negotiations has helped enterprise clients reduce Microsoft Fabric commitments by 20–40% through independent sizing, competitive benchmarking, and EA negotiation support. Our advisors bring former vendor-side intelligence to every negotiation — contact us before your next EA renewal includes a Fabric discussion.