Topic hub
F SKU prices, F0 and pay-per-use, F64, overage and smoothing, sizing, and what a Fabric project costs.
17 articles by the Solv Systems team
Fabric pricing looks simple, one capacity SKU and a per-user licence, until the first invoice. Capacity units are smoothed, bursts are borrowed and paid back, overage can be billed or throttled, Copilot draws from the same pool, and the reservation discount only pays off if you sized correctly in the first place. Most of the questions we get from finance teams and IT leads are about this, not about the technology.
This hub collects our pricing, licensing and capacity writing. It starts with the complete F SKU price guide and a plain explanation of how Fabric measures usage. It covers the newer options, F0 and on-demand billing and what pay-per-use means for small teams, and the thresholds that matter, such as what F64 unlocks and when Power BI Pro is enough. There are guides to sizing a capacity, administering and scaling it, controlling overage, and what Copilot in Fabric costs in capacity terms. For budgeting we have published what a Fabric implementation costs in the UK, the US and South Africa, how to build the business case, and the pilot-first approach we now use before anyone commits to a reservation.
Platform and engineering topics live in the Microsoft Fabric hub. Power BI licensing on its own is covered under Power BI.
Newest first.
F0 and on-demand billing change the Fabric sizing conversation. Why we now start from workload shape, keep reservations for proven steady load, and what we can't size until prices are published.
How we now run a Microsoft Fabric proof of concept: pay-as-you-go today, on-demand when it lands, spend limits set first, capacity metrics read honestly, and only then the reserve decision.
For small and mid-sized teams in the UK and South Africa, Fabric always meant paying for a capacity first. F0, on-demand billing and Fabric apps for Power BI Pro change that conversation.
Fabric capacity overage is generally available: paid compute at three times pay-as-you-go instead of throttling. What it costs, how the 24-hour threshold works, and when to resize instead.
Microsoft announced on-demand billing and a zero-provisioned F0 SKU at FabCon Europe 2026. How they work, what is and is not priced yet, what is coming soon, and whether to wait or reserve.
F64 is the Fabric SKU where report viewers stop needing Power BI licences. What it costs in USD, GBP and ZAR, what else changes at 64 CUs, and the break-even maths against F32.
Copilot in Fabric has no per-user licence: every prompt bills capacity units against your F SKU. How the consumption model works, and how to keep it from eating your capacity.
Sizing is the buying decision; this is the operating one. How to read the Capacity Metrics app properly, what to alert on, and when to scale rather than optimise.
Data volume is the wrong input. Capacity follows refresh frequency, query concurrency and how efficiently your workloads are written - which is why two similar businesses land two tiers apart.
There is a free trial and there is a free licence, and they are different things. What each one actually gives you, where the line sits, and when free is genuinely enough.
Every Microsoft Fabric F SKU with pay-as-you-go and reserved monthly pricing in dollars, pounds and rand, a cost calculator, the F64 threshold, and three worked examples.
Fabric licensing is two systems working together: capacity (F SKUs measured in capacity units) and per-user licences. This guide explains how the model works and what you actually need to buy.
Justifying a Microsoft Fabric investment to your leadership team requires more than a technology pitch. Here is a practical framework for building a compelling, CFO-ready business case.
Microsoft Fabric implementations in the US range from $20,000 to $600,000. Four real project profiles with USD cost ranges, F-SKU capacity costs, and what drives the variation.
Microsoft Fabric implementations in South Africa range from R240,000 to R8 million. Four real project profiles with ZAR cost ranges, capacity costs, and what drives the variation.
Microsoft Fabric implementations in the UK range from £15,000 to £500,000. Four real project profiles with honest GBP cost ranges, capacity costs, and what drives the variation.
How Microsoft Fabric measures what you consume: Capacity Units, the 30-second evaluation window, smoothing and throttling - and how to run analytics spend as a managed dial.
We size capacities from real workloads, not from the price list. Book a free 30-minute call and we will tell you whether a pilot, a pay-per-use capacity or a reservation makes sense.