Content reviewed: 14 October 2026
Power BI access depends on user licence, workspace mode, report and semantic-model locations, and permissions. An author’s licence or a Teams link does not establish rights for the whole audience.
Separate authors, readers and required features first. Locate both parts of the content, then choose Pro, PPU or Fabric capacity. Premium is not one interchangeable product.
Pro, PPU and capacity
Pro supports publishing and collaboration between licensed users. PPU includes Pro and most Power BI Premium features per user; do not automatically buy separate Pro for someone with PPU. A PPU workspace requires PPU recipients and is different from a Premium capacity workspace. Microsoft distinguishes licences and modes.
PPU does not provision Fabric capacity or automatically run non-Power BI items such as lakehouses, warehouses or notebooks. Those workloads require suitable F or trial capacity. Fabric licensing separates Power BI rights from other items.
| Content mode | Reader | Author or editor |
|---|---|---|
| Pro workspace / shared capacity | Pro or PPU | Pro or PPU |
| PPU workspace | PPU | PPU for the relevant use |
| Fabric F64 or larger | Free can suffice for supported viewing with appropriate access | Pro or PPU for Power BI creation outside My workspace |
| Fabric smaller than F64 | Pro, PPU or suitable individual trial | Pro or PPU for ordinary publishing |
This summarises Fabric licensing, not every embedded or external case. A PPU author can publish in another supported mode; their personal licence alone does not make every recipient require PPU. Stored content mode determines the requirement.
F64: check report and model
Buying F64 and placing only the report there is not sufficient for Free readers. Sharing rules require the underlying semantic model to be on qualifying capacity too. A model left in another workspace without suitable capacity can produce an upgrade prompt even when the report is on F64.
Record the report-workspace and model-workspace names or IDs, their licence modes and actual capacity assignments. Check reader access as well: Fabric documentation specifies Free with a Viewer role on F64+. Higher roles and Power BI editing have different conditions. A capacity icon is not a complete licensing inventory.
A smaller F SKU can provide other Fabric features without the same Free Power BI viewing rights. Reassess the audience after a SKU change. Capacity-based viewing rights do not replace content permissions.
Links and embedded reports
Teams, SharePoint or an internal portal help people find reports. Ordinary internal embedding does not supply a missing Power BI licence. Microsoft distinguishes Embed for your organization from Embed for your customers, which has its own authentication and capacity rules. Do not apply embedded SKU rules to ordinary Power BI service distribution without checking the scenario.
Test with the actual recipient account without a trial. An administrator can have broader access and a different licence. Record report, model, workspace, mode, opening route and audience to separate licensing, bad links and missing access.
A link does not move PPU dependencies
PPU requirements also cover XMLA, Analyze in Excel and composite-model access. Putting a report elsewhere does not give Free users access to its model in a PPU workspace. PPU documentation explains that dependency.
Moving from PPU to capacity requires a full refresh of the relevant datasets or dataflows according to the documentation. Check target-capacity limits, refresh and features too. PPU and a specific F SKU are not necessarily equivalent in performance or functionality. A pilot with temporary elevated rights does not prove access after expiry.

Three authors and eighty readers
Our hypothetical model has three authors and eighty other people who only read. None has a suitable paid entitlement yet, and we exclude trials. They need the same content, but required features are assessed separately first.
| Option | User entitlements | Conditions to confirm |
|---|---|---|
| Pro-mode content | 83 Pro or suitable higher entitlements | Required features without a PPU dependency |
| PPU-mode content | 83 PPU | PPU for authors and recipients of that content |
| Supported F64+ distribution | 3 Pro/PPU authors, 80 Free readers and capacity | Report and model on qualifying capacity, access and performance |
This does not claim identical features or that F64 is cheapest for eighty readers. Let P be one Pro licence’s price for the comparison period and C the suitable capacity price for the same period. Where Pro works in both options, the simple licence comparison is 83P versus 3P + C. The capacity option is cheaper within this limited model when C < 80P.
The inequality is not a market price or recommended user threshold. Include existing licences, features, reservations or operating hours, administration and measured load. If Pro lacks required features, 83 Pro is not a valid option regardless of price. A historical dollar table on a forum cannot establish the break-even point.
RLS and reader roles
Hiding a column, report page or app-navigation item is not data security. Sharing can expose the underlying model; use RLS or OLS where data access must be restricted. Microsoft distinguishes hiding from protection.
For workspace roles, RLS applies to Viewer. It does not apply to Admin, Member or Contributor, which have model-editing rights. Do not give a reader Contributor simply to fix a viewing problem. Include role-specific RLS rules in the test.
A Viewer with model Build permission remains restricted by RLS, including Analyze in Excel. Build does not automatically bypass RLS, but it can enable further model use. Test the actual output as an ordinary recipient. For DirectQuery with SSO, Test as role is unsupported; documentation recommends an actual Viewer account.
Publish to web is public
Publish to web lets anyone on the internet view without authentication. Microsoft warns about detailed underlying data aggregated by a visual too. Sending the link only to colleagues does not make it controlled internal distribution. Public publishing conditions require content suitable for public access; RLS reports are unsupported.
A pilot that exposes missing rights
| Layer | Record |
|---|---|
| User | Licence, any trial and actual role |
| Report | Workspace, mode, capacity and opening route |
| Semantic model | Workspace, mode and relevant dependencies |
| Data | RLS/OLS, permitted rows, export and any Build permission |
| Operation | Refresh, gateway, performance and temporary-entitlement expiry |
A Free reader must complete the final scenario without a temporary PPU trial. Test recipients restricted to different data too. An author demonstration does not prove audience access. Repeat after changing content mode, source model or role.
- List authors, readers and required features.
- Locate report and model workspaces and their modes.
- Separate existing rights from new purchases.
- Check PPU dependencies and migration refresh.
- Test licences, roles and data as an ordinary recipient.
- Compare actual offers over the same period.
- Save the dependency map and operational owner.
Frequently asked questions
Is the author’s PPU enough for Free readers?
Not for content in a PPU workspace. Recipients need PPU; another report location does not remove a PPU model dependency.
Is moving the report to F64 enough?
Check the underlying semantic model and recipient access too. Free viewing needs qualifying capacity for both parts.
Can a Free reader use a report on F32?
Do not assume the F64+ entitlement for ordinary Power BI sharing. Below F64, readers need Pro, PPU or a suitable trial.
Does Viewer Build permission bypass RLS?
No. Microsoft says RLS still applies to Viewer with Build. Admin, Member and Contributor work differently.
Does Teams embedding remove the licence requirement?
No. Ordinary internal embedding preserves Power BI licensing and access requirements.
Does PPU automatically include a Fabric lakehouse?
PPU does not itself provide capacity for non-Power BI Fabric workloads. They require suitable F or trial capacity.
Prepare a user → report → model → workspace → capacity → permissions map for the quote. Add required features and load profile. This supports distribution and cost checks without confusing per-user PPU with Fabric capacity.








