Microsoft Fabric licensing is genuinely complicated. The F-SKU tiers, capacity unit behaviour, and the interaction between per-user and capacity billing are not straightforward - and the decisions made without understanding them tend to be expensive in ways that are not obvious until the first renewal.
This whitepaper breaks down how Fabric licensing actually works: the F-SKU structure, capacity units and what they mean for workload allocation, the per-user versus capacity decision, and a worked example for a 200-person UK business that makes the economics concrete.
Most Fabric licensing decisions are made before anyone understands them.
F-SKUs, capacity units, and what they actually mean
The Fabric licensing model is built around capacity units rather than per-user costs for most workloads. Understanding how those units are allocated, how they scale, and how the F-SKU tiers relate to old Power BI Premium tiers is the foundation of a rational licensing decision.
Per-user versus capacity: how to decide
The decision depends on the number of users, the workloads you are running, and how you expect both to grow. The whitepaper covers the break-even points and the scenarios where each approach makes financial sense.
What the whitepaper covers
- How the Microsoft Fabric F-SKU structure and capacity units work in practice
- The per-user versus capacity decision and how to evaluate it for your organisation
- A worked example for a 200-person UK business showing the real licensing economics
- The common mistakes in Fabric licensing decisions and how to avoid them
- How Fabric licensing relates to existing Power BI Premium and Pro investments
Who this is for
IT managers, finance directors, and operations leads responsible for Microsoft licensing decisions who need to understand Fabric's billing model before committing to a procurement decision.