Microsoft Fabric Pricing: Capacity Units, F-SKUs, and What You Pay

Microsoft Fabric pricing has two parts that teams routinely blur together, and getting them straight is the whole game. You buy a capacity, which is a pool of compute measured in Capacity Units and sold as an F-SKU, and you buy per-user licenses for the people who create and view content. On top of both, OneLake storage is billed separately by volume. Miss any of the three and your estimate will be wrong.

This guide breaks down each component with realistic scenarios so you can estimate what you will actually spend. All prices referenced are approximate and change, and vary by region, so always verify against the official Microsoft Fabric pricing page before you budget.

How Fabric Pricing Works: The Capacity Model

Fabric runs all its workloads, data engineering, warehousing, real-time analytics, data science, and Power BI, on a shared compute pool called a capacity. You do not pay per query or per pipeline run. You pay for the capacity itself, sized by an F-SKU, and every workload draws from that same pool. This is convenient (one bill for everything) and also the source of most cost confusion, because a single number has to cover wildly different workloads.

There are three cost components. The capacity (F-SKU) is usually the largest line and is fixed for the size you choose. Per-user licenses (Free, Pro, or Premium Per User) determine who can create and view content, and below a certain capacity size they are mandatory for every viewer. OneLake storage bills separately by the terabyte. The capacity is the anchor; the other two scale with your people and your data.

F-SKUs and Capacity Units

Compute is measured in Capacity Units (CUs), and F-SKUs are sold in a doubling ladder: F2 has 2 CUs, F4 has 4, and so on through F8, F16, F32, F64, F128, F256, F512, F1024, up to F2048 with 2,048 CUs. Cost scales roughly linearly with CUs, so an F4 costs about twice an F2.

For orientation on pay-as-you-go rates, an entry-level F2 is around $260 to $310 per month, and an F64 is around $8,000 to $8,500 per month on demand (Azure pricing; Synapx 2026 guide). The important behavior is that a capacity has a fixed ceiling of compute: when workloads exceed what the SKU provides, Fabric smooths and then throttles rather than sending you a surprise overage bill. That makes the F-SKU a budget you set, but it also means an undersized capacity shows up as slow reports and delayed jobs, not a bigger invoice.

Pay-As-You-Go vs Reserved

Every F-SKU can be bought two ways, and the choice is a real cost lever.

Pay-as-you-go (PAYG) is billed per second with a one-minute minimum and no time commitment, and, crucially, you can pause it. Pausing stops the compute meter entirely, which is ideal for development capacities, dev/test environments, or workloads that only run part of the day. A capacity paused overnight and on weekends can cut its compute bill by well over half.

Reserved capacity is a 1-year commitment that costs roughly 41 percent less than PAYG for the same SKU (Synapx). The trade-off is that a reservation cannot be paused; you pay for it around the clock regardless of use. So the decision is simple in shape: reserve capacities that run more or less continuously, and keep part-time capacities on PAYG so you can pause them. Reserving a capacity you could have paused is a common and expensive mistake.

Per-User Licenses and the F64 Cliff

The capacity is only half the license story. People still need per-user licenses, and the rules create a genuine pricing cliff at F64.

There are three per-user tiers. Free is granted on first sign-in and lets a user create non-Power BI Fabric items (lakehouses, notebooks, pipelines) in a workspace on an F capacity. Pro is required to create and share Power BI content in shared workspaces. Premium Per User (PPU) adds most Premium features on a per-user basis and is cost-effective for Power BI-heavy teams under roughly 250 users, but it does not provision a Fabric capacity.

The cliff is this, in Microsoft's own words: on F-SKUs smaller than F64, "each user viewing Power BI content must have Pro, PPU, or an individual trial." On "F64 or larger, users with only a Free license and a viewer role can view Power BI content" at no per-user cost. For an organization with many viewers, this changes the math completely. Below F64 you pay per head to let people look at a report; at F64 you pay for the capacity once and viewing is free. That is why F64 is often the right answer not because the compute is needed, but because it eliminates hundreds of Pro licenses.

OneLake Storage

All Fabric data lands in OneLake, the unified storage layer, which uses a pay-as-you-go model billed separately from compute at roughly $23 per terabyte per month (Azure pricing), similar to standard cloud object storage. Storage is usually a modest line next to capacity, but two details are worth knowing.

First, mirroring includes a free allowance: per Microsoft, "Mirroring offers a free terabyte of mirroring storage for every capacity unit (CU) you purchase. For example, if you purchase an F64 capacity, you get 64 free terabytes." Second, and easy to get caught by, the same documentation adds that "you pay for OneLake storage if you exceed the free mirroring storage limit or when the capacity is paused" (Fabric mirroring docs). Pausing saves compute, but it does not make mirrored storage free.

Realistic Cost Scenarios

These scenarios use approximate pricing to illustrate cost structure. Your actual costs will vary by region, reservation choice, license mix, and workload. Verify against current pricing before budgeting.

Small team: a dev capacity, paused off-hours

A small team runs an F2 on PAYG for development and Power BI, paused overnight and on weekends, with a handful of Pro licenses for creators and viewers. Rough monthly shape: an F2 running roughly a third of the hours (well under $150 after pausing) plus a few Pro licenses (about $14 each per month) plus minimal storage. Total: a few hundred dollars per month, dominated by licenses rather than compute.

Mid-size: F64 to unlock free viewers

A department with 15 report creators and 300 viewers moves to an F64 specifically so viewers can use Free licenses. Rough monthly shape: F64 on a 1-year reservation (roughly $5,000 per month after the reservation discount) plus 15 Pro licenses for creators (about $210) plus storage for a few terabytes. Total: roughly $5,200 to $6,000 per month. The comparison that justifies it: 300 Pro licenses would add thousands per month on a smaller capacity.

Enterprise: multiple capacities

An enterprise runs several capacities (for example F128 for production plus F64 for a business unit) on reservations, with hundreds of creators on Pro and thousands of free viewers. Rough monthly shape: capacity reservations in the tens of thousands, creator Pro licenses in the low thousands, and OneLake storage scaling with the data estate. Total: tens of thousands of dollars per month, where the main levers are capacity sizing, reservation coverage, and how tightly workloads are packed onto each capacity.

Cost Optimization Strategies

Ranked by impact.

1. Pause PAYG capacities you do not run continuously. The highest-impact lever for part-time workloads. A development or reporting capacity paused nights and weekends can cut its compute cost by more than half, and PAYG exists precisely so you can.

2. Reserve only the capacities that run around the clock. A 1-year reservation saves about 41 percent, but it cannot be paused. Match reservations to continuous workloads and keep intermittent ones on PAYG. Reserving a pausable capacity throws away the pause savings.

3. Size to F64 when you have many viewers. If viewer licenses are your cost driver, the jump to F64 (where Free viewers can view Power BI content) often costs less than the Pro licenses it removes. Do the arithmetic on viewer count, not just compute need.

4. Consolidate workloads onto fewer capacities. Because a capacity is a fixed pool, an underused capacity is wasted budget. Packing more workloads onto one right-sized capacity beats running several half-idle ones, as long as you leave headroom for peaks.

5. Monitor with the Fabric Capacity Metrics app. Throttling and smoothing hide overload as slowness rather than cost, so use the metrics app to see whether a capacity is genuinely saturated (size up) or just spiky (leave it and let smoothing absorb the peaks).

Hidden Costs Most Teams Miss

Viewer licenses below F64. The classic surprise. A team sizes a small capacity for its compute, then discovers every one of its report viewers needs a paid Pro license. For a wide audience, this dwarfs the capacity cost and is the main reason to consider F64.

Reservations you cannot pause. Teams reserve to get the 41 percent discount, then realize they gave up the ability to pause an intermittent capacity. For anything that is not near-continuous, PAYG plus pausing can be cheaper than a reservation.

Paused-capacity storage. Pausing stops compute but flips mirroring storage from free to billable. A capacity you pause to save money still bills for its mirrored data.

Throttling read as a product problem. An undersized capacity does not overspend; it slows down. Teams sometimes chase performance issues that are really a capacity that needs sizing up, or workloads that need spreading across capacities.

Idle over-provisioning. The opposite failure: a capacity sized for a peak that rarely happens bills at full rate all month. Fabric smooths short bursts, so you can often run a smaller SKU than the peak suggests.

How Dawiso Helps Control Fabric Costs

Fabric cost control is partly about capacity settings and partly about knowing what is actually on the platform: which datasets are used, which reports are duplicated, and which pipelines still run for no one. That visibility is a governance problem, and it is where Dawiso helps.

Dawiso's data catalog shows which Fabric and OneLake assets are actively consumed and which are orphaned, so you can retire pipelines that draw capacity for tables nobody reads. Lineage traces data end to end, across ingestion, warehouses, and the Power BI reports downstream, down to column-level lineage, so you can see the real cost of a redundant dataset before you delete it.

The business glossary stops duplicate work: when several teams build the same metric on the same capacity, they all consume compute, and one governed definition replaces them. And for teams extending Fabric with AI, Dawiso serves governed context to agents through the Model Context Protocol, so AI reads trusted, owned definitions rather than guessing at the meaning of a report.

Conclusion

Microsoft Fabric pricing comes down to three components: a capacity F-SKU priced by Capacity Units, per-user licenses with a hard cliff at F64, and OneLake storage on top. The complexity is in the choices around them, and the biggest savings come from three habits: pause PAYG capacities you do not run continuously, reserve only the ones you do, and size to F64 when viewer licenses would otherwise dominate. For a platform comparison, see Databricks vs Microsoft Fabric, and for Power BI within Fabric, see Power BI and Fabric integration.

Sources

Pricing changes often and varies by region. Always confirm current figures against the primary sources below before budgeting.

• Microsoft Learn, Microsoft Fabric pricing (F-SKU pay-as-you-go and reserved rates, OneLake storage rate).
• Microsoft Learn, Understand Microsoft Fabric licenses (F-SKU and Capacity Unit table, per-user licenses, the F64 viewer rule).
• Microsoft Learn, Buy a Microsoft Fabric subscription (per-second billing with one-minute minimum, PAYG vs reservation, pause).
• Microsoft Learn, Pause and resume your capacity (pausing to stop compute billing).
• Microsoft Learn, OneLake capacity consumption (storage billed separately, pay-as-you-go, per GB per month).
• Microsoft Learn, Mirroring in Fabric (free mirroring storage of 1 TB per CU, billable when exceeded or when the capacity is paused).
• Microsoft Learn, Fabric capacity reservations (1-year reservation).
• Synapx, Microsoft Fabric pricing 2026 (approximate F2 to F128 monthly rates, ~41% reservation saving).