Microsoft Fabric is priced as capacity units (CUs) sold in fixed SKUs called F2, F4, F8 and so on up to F2048. Each step roughly doubles the compute and roughly doubles the price. The principle is simple. The detail is where teams get caught out, particularly around what happens when capacity is exhausted and how Power BI licences interact with the capacity bill. This is the version we wish someone had given us before our first Fabric project.
The headline numbers (UK, 2026)
Pay-as-you-go list prices for the smaller SKUs, assuming the capacity is running 24/7:
F2 — roughly £210 per month. The entry point. Suitable for proofs of concept, small dev environments, or very light production workloads.
F4 — roughly £420 per month. Realistic for a small production workload with a handful of report consumers.
F8 — roughly £830 per month. The sweet spot for a lot of UK mid-sized businesses running Power BI plus a small Data Factory pipeline.
F16 — roughly £1,650 per month. Where Power BI Premium-style workloads start to feel comfortable.
F32 and up — £3,300+. Enterprise territory, with the ability to support thousands of concurrent users and several parallel workloads.
Reservations (12-month commitments) cut the bill by around 40%. Pause/resume gives you back unused hours but is fiddly to operationalise — most teams end up leaving capacity running.
What is actually included
A Fabric capacity covers Data Factory, Data Engineering (Spark notebooks), Data Warehouse, Real-Time Intelligence, Data Science, and most importantly Power BI Premium features. That last point matters: from F64 upwards, every user in your tenant can view Power BI content without needing a Pro licence. Below F64, consumers still need Pro (or PPU) licences at £8 / £18 per month.
Storage in OneLake is billed separately at roughly £0.02 per GB per month. For most workloads it is rounding error compared to compute. Data egress (moving data out of OneLake to another region) is the one to watch — it can quietly add up if you are not careful with cross-region pipelines.
The three gotchas that hurt the first bill
1. Smoothing and bursting. Fabric lets short-term spikes "burst" above your capacity for up to 24 hours, then smooths the cost back out across the day. Convenient, except the smoothing can push you past your capacity threshold without anyone realising, and the next thing that runs gets throttled. Install the Capacity Metrics app on day one and check it weekly.
2. The "below F64 Pro licence" rule. Plenty of teams adopt F2 or F8 thinking it replaces Power BI Pro for their users. It does not. Until you hit F64 (around £6,600 per month), every viewer still needs a Pro licence. For most mid-sized organisations, that maths means staying on Power BI PPU is cheaper than buying a small Fabric capacity if the only goal is Power BI consumption.
3. Background and interactive workloads on the same capacity. A heavy notebook running at 9am can eat all the CUs and leave Power BI reports throttled for the rest of the morning. Production data engineering and production Power BI are best kept on separate capacities once your workload is non-trivial.
How the maths usually plays out
We tend to give clients three rough comparisons before they choose:
20 Power BI users, no other workloads. 20 × £8 Pro = £160 / month. Fabric F2 = £210 / month and still requires Pro licences. Verdict: stay on Pro.
50 Power BI users plus a daily pipeline. 50 × £8 = £400 / month for Pro, plus engineering tooling. Fabric F8 at £830 / month bundles the pipeline and gives you OneLake. Verdict: depends on whether the pipeline is a "nice to have" or a real workload — probably worth it if it is real.
300 Power BI users, multiple workloads, no Pro licences. 300 × £18 PPU = £5,400 / month. Fabric F64 at around £6,600 / month covers all of it without Pro licences and adds the rest of the platform. Verdict: Fabric wins clearly.
Practical tips that have saved real money
Run development on a separate, paused F2 that you turn on only during business hours. You will pay for maybe 200 hours a month rather than 720.
Keep an eye on auto-scale settings; the default behaviour can commit you to a higher tier accidentally. Disable it until you have a baseline.
Reserve capacity once you have three months of usage data and the size has stabilised. Do not reserve on month one — you will likely choose the wrong SKU and be stuck with it.
For a guided look at sizing Fabric capacity for your specific workloads, our Microsoft Fabric consultancy page covers how we run a quick capacity assessment, and our plain-English Fabric guide explains the architecture in more detail.
Frequently asked questions
What is the cheapest Microsoft Fabric tier?
The smallest SKU is F2, listing at roughly £210 per month in the UK if left running. Pausing it when not in use lowers the effective monthly cost.
Do Fabric users still need Power BI Pro licences?
Below F64, yes — every report viewer still needs a Power BI Pro or PPU licence. F64 and above include Power BI viewing for all users in the tenant.
How is Fabric different from paying per Power BI user?
Power BI Pro is per-user and predictable. Fabric is per-capacity and shared across all workloads. For mostly-Power BI usage below 300 users, Pro is usually cheaper.
Want to talk this through with someone?
We are an independent UK Power BI and Microsoft Fabric consultancy. Honest opinions, fair prices, no sales pressure.