Power BI licensing overview

What it does

Two independent axes decide what someone can do in the Power BI service: the per-user licence they hold, and the capacity the content sits on. Per-user comes in three flavours — Fabric (free), Power BI Pro, and Power BI Premium Per User (PPU). Capacity is a separate organisational subscription. What you can actually do is the intersection of the two.

Key facts

Free users can connect to data and build reports for themselves. They can't share, can't collaborate, and can't publish into other people's workspaces.
Pro is the standard authoring and sharing licence. Pro users can publish, share and subscribe, and can collaborate with other Pro users. On shared capacity, everyone in the loop needs Pro.
PPU includes everything Pro does plus most Premium capacity features, granted per user rather than per workspace. Content in a PPU workspace can only be accessed by other PPU holders — including through the XMLA endpoint, Analyze in Excel and composite models.
Capacity changes the rules for consumption. Where content sits on a qualifying capacity, Pro and PPU authors can distribute it to users holding a free licence.
Microsoft states the free-viewing threshold as Fabric F64 or larger, or a Power BI Premium P capacity. Below F64, viewers need their own paid licence.
Both the report and its underlying semantic model must sit on the qualifying capacity for free users to open it. A report on capacity over a model on shared capacity produces an upgrade prompt.
A PPU workspace is not a Premium capacity workspace. Microsoft calls this out explicitly because people conflate them constantly.
Creating Power BI items in any workspace other than My workspace needs at least a Pro licence, regardless of how much capacity the organisation has bought.
A user can hold more than one licence at once; the service gives them the most permissive one they hold.
Microsoft is consolidating purchase options and retiring the Power BI Premium per-capacity P SKUs in favour of Fabric F SKUs. Both still appear across the documentation, which is why guidance from different pages can look inconsistent.

When to use / skip

Every Power BI engagement needs this conversation in week one, because it drives workspace design, capacity sizing and often the whole architecture. Get it wrong and you either overspend on per-user licences for people who only ever look at a dashboard, or you build a distribution model that quietly requires every viewer to be paid.

The one rule that resolves most arguments: count your authors and count your viewers separately, and never let anyone quote a single number. Authors always need Pro or PPU. Viewers need Pro, PPU, or a capacity big enough to carry them for free.

Configuration decisions

Authors versus viewers, counted honestly. "Everyone might want to edit" is not a count.
Whether the free-viewer threshold is reachable. Below it, capacity buys performance and features but not licence relief.
Whether PPU is a genuine destination or a stepping stone. Sharing constraints make it awkward as a permanent state for anything broadly distributed.
Which workspaces land on capacity, given the model has to be there too, not just the report.
Where prices come from. Microsoft publishes them on the Power BI pricing page and defers the detailed rules to its licensing documentation — quote those, not a number from memory.

Gotchas

The report-and-model-both-on-capacity rule is the single most common licensing surprise on a delivery. A shared enterprise model left on a Pro workspace makes every viewer of every downstream report a paid user.
Free users also need a role in the workspace, or an app they've been given access to. Capacity alone doesn't grant access.
PPU content can only be shared with PPU holders unless the workspace is on capacity. Clients buy PPU for the features and then find they can't distribute the output.
P SKU and F SKU guidance coexists across Learn pages during the transition. Where two pages disagree, take the more recently updated one and flag the discrepancy rather than picking silently.
Trials expire. A pilot that worked beautifully on a Fabric trial capacity becomes an invoice conversation sixty days later.

Consultant notes

Never quote prices from memory in a workshop. Point at the Microsoft pricing page and the current licensing documentation, and let procurement own the number.
Draw the licence model as a picture in the first architecture session — capacities, workspaces, who authors, who views. It settles more arguments than any table.
Watch for the client who bought capacity expecting it to eliminate all per-user cost. Authors still need Pro. Say so before the invoice does.
Model the "what if they grow" case. Licensing shapes that work at fifty viewers and shapes that work at five thousand are different shapes, and migrating between them is disruptive.

Licensing moves. Recheck the free-viewing threshold and the P-to-F SKU transition before repeating any of this in front of a client