Microsoft Fabric Pricing Calculator
Capacity & Cost Estimator
Estimate your F-SKU compute cost, OneLake storage, mirroring free allocation, and Power BI Pro licensing. Built on official Azure 2026 pricing data and verified against Microsoft Learn documentation.
Microsoft Fabric pricing has three components: compute (F-SKU at ~$0.18/CU-hour PAYG in US East), storage (OneLake at $0.023/GB/month), and licences (Power BI Pro at $14/user/month). Each F-SKU includes free mirroring storage equal to its CU count in TB (F64 = 64 TB free). A 1-year reserved commitment saves ~41% versus PAYG. (per Azure Pricing, June 2026)
Microsoft Fabric Cost Optimisation Tips
PAYG for Dev, Reserved for Prod
Use PAYG for development capacities you can pause nights and weekends. Use 1-year Reserved for production. Reserved pays off when a capacity runs more than ~60% of available hours.
F64 — The Viewer Licence Pivot Point
Below F64, every viewer needs Power BI Pro ($14/month). Above F64, viewers pay nothing. For 350+ viewers, F64 Reserved ($5,003/mo) is nearly always cheaper than per-user licences.
Mirroring Free Storage Scales with SKU
Each CU purchased gives 1 TB free mirroring storage. F64 = 64 TB free. If your mirrored data fits within the free limit, mirroring storage costs nothing — a major hidden saving.
Use CI/CD Tiered Rate on Dataflows
Non-CI/CD Dataflow Gen2 charges 16 CU/s flat. CI/CD mode drops to 12 CU/s for the first 10 min and 1.5 CU/s after. Long ETL jobs are dramatically cheaper on CI/CD mode.
Microsoft Fabric Pricing Calculator – Frequently Asked Questions
Pricing estimates are based on official Azure Fabric pricing, Dataflow Gen2 consumption rates, and OneLake consumption documentation as of June 2026. Reserved instance prices are 1-year US baseline rates. Actual costs vary by region, enterprise agreements, and currency. Network billing (not yet active) excluded. Verify current pricing at the Azure Pricing Calculator before commitments. UIG Data Lab is independent and not affiliated with Microsoft.
Understanding the Microsoft Fabric Pricing Framework
The Microsoft Fabric pricing model has three separate billing pillars — compute (F-SKU), storage (OneLake), and per-user licensing (Power BI Pro). Each is billed independently. The most common budgeting mistake is estimating only the SKU cost and forgetting storage and licensing. Use the calculator above before reading further to get your baseline number, then use this guide to understand what drives it.
How Capacity Units (CUs) and F-SKUs Work
The Capacity Unit is the billing currency for all Fabric workloads. Every action — running a SQL query, executing a notebook, refreshing a dataflow, ingesting an event stream — consumes CUs from the pool assigned to your F-SKU. The pool is shared across all workloads assigned to that capacity.
F-SKUs range from F2 (2 CUs) to F2048 (2,048 CUs). Each step up doubles available compute. The key insight: you don’t need to size for your absolute peak because smoothing and bursting handle short spikes. Size for your 24-hour average load, not the 15-minute maximum. See our Fabric Capacity Optimization guide for the full smoothing mechanics.
The Dataflow Gen2 CU Burn Rate — the Most Misunderstood Cost
Dataflow Gen2 is frequently the largest driver of unexpected Fabric bills. Per Microsoft Learn’s official Dataflow Gen2 pricing page, the consumption rates are:
| Mode | CU Rate | When It Applies | Optimization |
|---|---|---|---|
| Non-CI/CD (standard) | 16 CU/second — entire duration | Dataflow Gen2 items without CI/CD support enabled | Switch to CI/CD mode — all new items default to CI/CD as of April 2026 |
| CI/CD Tiered — First 10 min | 12 CU/second | CI/CD mode, first 600 seconds of any run | Keep runs under 10 min where possible |
| CI/CD Tiered — After 10 min | 1.5 CU/second | CI/CD mode, every second after 600s | Long ETL jobs are dramatically cheaper in CI/CD mode |
| Fast Copy (data movement) | 1.5 CU/second | Applies when Fast Copy is active — separate rate from query compute | Enable Fast Copy for eligible connectors — Azure Blob, ADLS, Azure SQL, Snowflake |
| High Scale (staging SQL engine) | 6 CU/second | When staging is on and Lakehouse/Warehouse SQL engine handles queries | Disable staging when source is structured and same-region |
For a 30-minute ETL job running 10 times per day: in non-CI/CD mode this costs 16 × 1,800 × 10 = 288,000 CU-seconds per day. In CI/CD tiered mode: (12 × 600) + (1.5 × 1,200) = 9,000 CU-seconds per run × 10 = 90,000 CU-seconds per day. That is a 68% reduction in Dataflow CU cost from a single configuration change. See our full Dataflow Gen2 Production Guide for Fast Copy optimization and staging bypass strategies.
OneLake Storage Pricing for Microsoft Fabric
Per Microsoft Learn’s OneLake consumption documentation, OneLake storage follows Azure Data Lake Storage Gen2 hot tier pricing — approximately $0.023/GB/month ($23/TB/month) in US baseline regions. This is billed separately from your F-SKU and scales directly with data volume.
Mirroring pause risk: The 1 TB per CU free mirroring storage allocation only applies while your capacity is running. If you pause a PAYG capacity, all mirrored storage becomes billable at standard OneLake rates immediately — not after a grace period. For large mirrored datasets, model this cost before scheduling capacity pauses. For the full mirroring architecture, see our Data Mirroring in Fabric guide.
Smoothing — Why Your Peak CU Usage Doesn’t Determine Your SKU
Smoothing is one of the most misunderstood features of Microsoft Fabric pricing. When a workload bursts beyond your SKU’s base CU allocation, Fabric allows it to complete — then spreads the CU debt across a future window rather than throttling immediately. Interactive operations smooth over a minimum of 5 minutes. Background operations (scheduled refreshes, pipelines, warehouse operations) smooth over 24 hours.
This means sizing for the 24-hour average load — not the 5-minute peak — is correct. A 10-minute Spark job that requires 128 CUs on an F64 capacity uses smoothing to complete without throttling. If you consistently exceed your 24-hour average, throttling begins progressively. For how to respond to active throttling, see the Capacity Optimization guide.
F64 — The Financial Pivot Point in Microsoft Fabric Pricing
F64 is the capacity size that changes the licensing math for most enterprise organizations. Two things happen at F64:
- Power BI Pro licences become optional for viewers: Users with appropriate workspace roles can consume Power BI reports without a $14/month Pro licence. For organizations with 350+ report viewers, F64 Reserved ($5,003/month) is nearly always cheaper than paying per-user licences even if the compute requirement alone would be satisfied by F32.
- F64 = Power BI Premium P1 equivalent: F64 on 1-year reserved pricing ($5,003/month US East) is the direct functional replacement for the legacy P1 SKU at the same price point — but includes all Fabric workloads (Data Engineering, Data Factory, Real-Time Intelligence) that P1 never covered.
PAYG vs Reserved — When Each Makes Sense for Fabric Capacity
Per Microsoft Learn’s reservation documentation, a 1-year Reserved commitment saves approximately 41% versus PAYG rates. The decision rule is straightforward:
- Development capacities: PAYG. Pause nights, weekends, and when not actively in use. An F8 PAYG running 8 business hours/day costs roughly one-third of running 24/7.
- Production capacities: Reserved once your baseline load is established (minimum 30 days of PAYG usage data). The 41% saving is substantial — on F64, that’s approximately $3,400/month versus PAYG.
- Burst capacity for known events: PAYG on a temporary larger SKU for year-end processing, marketing campaigns, or Black Friday workloads. Turn on for 3 days, pay for 72 hours.
Regional Pricing: India, Europe, and the Americas
Azure infrastructure costs vary by region. The US East baseline ($0.18/CU-hour PAYG) is the lowest rate. India regions (Central India, South India) carry a ~33% premium at $0.24/CU-hour. Europe ranges from $0.191/CU-hour (UK South) to $0.23/CU-hour (Sweden Central, Brazil South). Switzerland North sits at $0.22/CU-hour.
For organizations with GDPR or data residency requirements that mandate Europe North (Ireland) or Germany West Central, the price premium versus US East is typically 7–17%. This is usually the right trade-off for compliance — the cost of a data residency incident far exceeds the regional premium. For governance architecture that works within these constraints, see our Fabric Production Stability guide.
Copilot in Fabric — What It Actually Costs
Copilot is available on any F-SKU — F64 is not a hard minimum. Per Microsoft Learn’s Copilot consumption documentation, each Copilot request consumes approximately 6.67 CU minutes as a background operation. On an F64 with 64 × 24 = 1,536 CU hours per day, you can run over 13,800 Copilot requests before exhausting capacity.
Microsoft recommends F64+ for production Copilot workloads because smaller SKUs have less headroom — Copilot competes with other workloads for the same CU pool. The recommended architecture for heavy Copilot usage is a dedicated F64 Copilot capacity, separate from your main production capacity, so Copilot consumption doesn’t affect report performance.
Direct Lake — How It Affects Your Microsoft Fabric Pricing Calculations
Direct Lake mode allows Power BI to query OneLake Delta tables without importing data — eliminating refresh cycle costs. When it works correctly, Direct Lake is far more cost-efficient than Import mode (which burns CUs on every refresh) or DirectQuery (which charges CUs on every user query). However, Direct Lake falls back to DirectQuery when semantic models exceed SKU-specific limits or use features not supported in Direct Lake mode.
A Direct Lake fallback turns what would have been an efficient cached query into a per-click CU charge. Monitoring for fallbacks is a cost-control measure, not just a performance one. For how to identify and fix fallback scenarios, see our Direct Lake Fallback guide.
How to Buy Fabric Capacity — Step by Step
- Provision: In the Azure Portal, search for Microsoft Fabric. Create a new Fabric capacity in your target region. Select your F-SKU. Start with F2–F8 PAYG for initial measurement.
- Measure: Run representative workloads for 30 days. Monitor daily CU utilization in the Capacity Metrics App. Track average utilization — not peak.
- Reserve: Once average utilization is stable, purchase a 1-year reservation via the Reservations blade in Azure. The 41% saving applies from the first hour of the reservation period.
- Assign: Move production workspaces to the reserved capacity in the Fabric Admin Portal. Keep development workspaces on a separate PAYG capacity.
- Optimize: Use the Metrics App’s per-item operation details to identify the highest-CU operations. Fix workload inefficiencies before scaling up capacity.
Fabric vs Databricks vs Snowflake — Cost Comparison Context
Fabric’s capacity-based pricing is structurally different from both Databricks (DBU + underlying VM costs per workload) and Snowflake (credit-based per-query consumption). Fabric simplifies multi-workload environments into one F-SKU bill covering Power BI, Spark, SQL, pipelines, and real-time analytics simultaneously. For detailed architecture and cost comparisons, see our full analysis: Fabric vs Snowflake.
