Content reviewed: 12 October 2026
Start with three lists: content creators, readers, and the features and performance the solution needs. Pro and Premium Per User are user licences. Fabric F is paid capacity. The design must combine both licensing models with operational requirements; audience size or the word “Premium” alone cannot decide the purchase.
Licences for authors and readers
| Workspace | Author in a team workspace | Reader |
|---|---|---|
| Pro on shared capacity | Pro or PPU | Pro or PPU |
| Premium Per User | PPU | PPU for interactive access |
| Fabric F2–F32 | Pro or PPU | Pro or PPU |
| Fabric F64 or larger | Pro or PPU | Fabric Free can suffice with appropriate access |
The table follows Fabric and Power BI licensing rules. For a free reader, check the Viewer role or app access. Do not assign Member or Contributor merely to simplify sharing. Owning capacity does not grant data access; permissions and security remain separate. Trials can temporarily change test results, so the table describes a lasting production design.
Count the entire Pro audience
Readers in a standard Pro workspace also need qualifying user licences. Microsoft distinguishes licensing, content location and permissions. Before buying, check assigned service plans, such as Power BI Pro in the relevant E5 package. The number of new licences is not automatically the number of people on the audience list.
PPU provides features, not Fabric capacity
Premium Per User includes Pro capabilities and advanced Power BI features. It does not provide separate capacity for lakehouses, warehouses or notebooks. Assess PPU for a defined group with shared requirements; buying it only for authors does not give Pro readers ordinary interactive access to PPU content.
Separate opening a report from receiving an attachment. Microsoft documents a PPU exception: a subscription with the same attachment for everyone can also reach a Pro user who cannot open that PPU content in the portal. This does not grant interactive access. Record delivery requirements separately.
F64 is an access threshold, not a sizing calculation
F64 and larger allows appropriately authorised free users to read Power BI content. Smaller F capacity does not provide those rights, even when it runs other Fabric workloads. Distinguish the minimum capacity needed for licensing from the capacity needed for performance. The final size must satisfy both.
Record query concurrency, model refreshes, memory demand and other Fabric workloads before deciding. Test the busiest part of the working day. Assess overnight processing and report availability separately: planned capacity pauses can change the service users receive. Assign monitoring and budget ownership in advance.
Example: ten authors and one hundred readers
| Requirement | Option to compare | Decisive check |
|---|---|---|
| Ordinary reports | 110 qualifying Pro or PPU user entitlements | Subtract users already covered; check limits |
| PPU features for this group | 110 PPU licences versus suitable F capacity and 10 author licences | Feature parity, measured performance and actual quote |
| Fabric processing fits F16 | F16 plus Power BI reader entitlements | Compute capacity does not remove Pro/PPU requirements |
| Broad audience with Free | F64 or larger plus author licences | Supported report and model placement, and access |
These are hypothetical headcounts, not a price recommendation. For each option, calculate additional user licences, capacity operation during required hours and related services. Use quotes with the same region, currency, period and contract assumptions. Prices are not directly comparable when the options do not meet the same requirements. Microsoft’s planning guide supports the licence inventory.
Reports and models can live in different workspaces
Placing a report on F64 is insufficient if its underlying semantic model stays in a workspace that does not permit free viewing. Microsoft flags this dependency. Map the entire chain from app to report to model in your pilot, then test with an actual reader account without a trial. An author’s access does not prove availability for the audience.
A paginated report does not decide the licence
Current paginated-report documentation gives .rdl and .pbix the same basic licence requirements. Pro or PPU allows publishing to another workspace with at least Contributor access; using a semantic model requires Build permission. A print-oriented output therefore does not by itself force PPU. Test export, memory and delivery against the actual report.
Moving from Premium P requires a planned F purchase
The migration guide distinguishes an active Enterprise Agreement from its expiry. Existing P capacity can run and renew annually under an active EA until that agreement ends. Plan an F migration when the agreement expires. Assess the documented sovereign-cloud exception separately rather than copying commercial deadlines without verification.
After subscription expiry, the guide lists 30 days of ordinary operation, throttling on days 31–90 and rejected operations from day 91. Do not schedule migration at the end of this safety period. Mapping P1 to F64 compares compute units; it does not guarantee functional or licensing equivalence.
Evidence for the decision
- 01
Map users and entitlements
Separate authors, readers and attachment recipients; record existing licences
- 02
Check the complete content chain
Report and model workspaces, target roles and app access
- 03
Measure the required workload
Pilot peak demand, refreshes and other Fabric workloads
- 04
Compare equivalent quotes
Match features, availability, region and period; name operational and cost owners
If you already own licences and need to find out why a recipient cannot open a link, use our Power BI report-sharing guide. This article helps choose the licensing model and size the solution. External app owns data applications need a separate architecture and licensing assessment.
Frequently asked questions
Does an author on F64 need a paid licence?
Creating and publishing Power BI content to team workspaces requires Pro or PPU. Free viewing rights do not remove that requirement.
Is F64 the right size for a given number of readers?
Headcount alone does not determine performance. F64 is a licensing threshold; measure the actual workload to establish capacity needs.
Is moving a report from PPU to F64 enough?
Check its underlying model, dependencies and target permissions too. Moving one report does not prove access for Free users.
Do paginated reports require PPU?
Not automatically. Microsoft gives them the same basic requirements as .pbix; workspace, permissions and operational features determine the design.








