Browse all topics
Power Platform

Power BI Pro vs Premium Per User vs Fabric capacity

Choosing between Power BI licensing tiers — Pro, PPU, and Microsoft Fabric capacity for different scenarios.

Power BI licensing has three main forms — Pro, Premium Per User (PPU), and Microsoft Fabric capacity (F-SKUs). Each fits different scenarios. Knowing which to pick saves money and avoids capability gaps.

Power BI Pro

The baseline shared-content licence:

  • Per-user per month — affordable.
  • Authoring rights — create and share reports.
  • Consumption rights — view shared reports.
  • Workspace sharing with other Pro users.
  • Sharing with consumers — recipients need Pro to view (unless Premium / Fabric is in play).

What Pro doesn't include:

  • Advanced features like incremental refresh on large models, AI features, paginated reports, deployment pipelines.
  • Sharing with users who don't have a Power BI licence.

The right tier for collaborative BI within small-to-medium teams where all users have Power BI licences.

Power BI Premium Per User (PPU)

A step up from Pro at higher per-user cost:

  • Everything Pro includes.
  • Advanced features — incremental refresh, larger models, paginated reports, AI features.
  • Deployment pipelines.
  • XMLA endpoint for external-tool access.

What PPU doesn't include:

  • Sharing with users who don't have a Power BI licence (PPU isn't enough; consumers still need PPU or Pro or capacity).

The right tier for individual heavy users wanting Premium-level features without needing dedicated capacity. Useful for analyst teams who author complex content but don't need to share with non-licensed consumers.

Microsoft Fabric Capacity (F-SKUs)

Dedicated shared compute backing many workloads:

  • Capacity-based rather than per-user — pay for the compute, license fewer users.
  • Includes Power BI Premium capabilities.
  • Plus the broader Fabric platform — Data Factory, Synapse Data Warehouse, Synapse Data Engineering, Real-Time Analytics, Data Activator.
  • Sharing with non-licensed consumers — when content is in a Fabric-capacity workspace, you can share with users who don't have Power BI Pro / PPU.

Capacity sizes: F2, F4, F8, F16, F32, F64, F128, F256, F512, F1024, F2048 — corresponding to Capacity Units.

Can be paused when not in use (no charges); resumed on demand. Scale up / down between sizes.

The right tier for:

  • Large user populations where licensing everyone per-user is more expensive than capacity.
  • Organisations building on the broader Fabric platform — data engineering, real-time analytics, warehouse alongside BI.
  • Sharing with broad audiences including unlicensed users.

How to choose

| Scenario | Right licensing | | --- | --- | | Small analyst team sharing reports among themselves | Power BI Pro | | Individual analyst needing Premium features | PPU | | Heavy report consumer base with 500+ viewers | Fabric capacity (F64+) | | Building on Fabric for data engineering | Fabric capacity | | Mixed authoring and consumption | Pro for authors, capacity for consumption |

Per-user vs capacity break-even

A rough rule:

  • Under ~50 viewers per Pro author — per-user Pro is cheaper.
  • More than ~50 viewers per author — capacity becomes cheaper because viewers don't need individual licences.

Real break-even depends on actual user counts, viewer engagement, and current pricing. Calculate explicitly.

Microsoft Fabric SKU sizing

Fabric capacity sizing depends on workload:

  • Reporting only — small Fabric capacity (F8–F64) often sufficient for hundreds of report consumers.
  • Plus dataflows and modelling — larger (F128+) to handle the compute.
  • Plus data engineering / warehousing — F256+ for substantial workloads.

Microsoft provides capacity-planning calculators. Start smaller, scale up based on observed usage.

Migration paths

  • From Pro to PPU — add the PPU licence to specific users wanting advanced features.
  • From Pro to Fabric capacity — assign workspaces to the Fabric capacity. Users keep Pro for authoring; viewers stop needing licences.
  • From Premium P-SKU to Fabric F-SKU — Microsoft has migration paths; the new F-SKUs supersede the old P-SKUs.

Operational considerations

  • Capacity utilisation monitoring — Fabric admin centre tracks utilisation; over-utilised capacities throttle, under-utilised waste money.
  • Workspace placement matters — assigning workspaces to capacities is the operational lever.
  • Pause unused capacities — auto-pause during off-hours saves significantly.
  • License usage audit — track who's actually authoring vs consuming; right-size accordingly.

For organisations growing serious Power BI investment, the licensing decision is consequential. Start with Pro; add PPU for heavy users; move to Fabric capacity when viewer counts justify it.