How to Share a Power BI Report With Colleagues (Without Breaking the Licence Rules)

Scenario: The Sales Performance Report That Nobody Can See

You’re the analyst for a regional sales team.

• You build a Sales Performance Power BI report in Power BI Desktop.
• Your organisation uses Microsoft 365 and has started rolling out Power BI.
• You have a Power BI Pro licence, but most of your sales managers only have the free licence.

You:

1. Publish the report to the Power BI service.
2. Hit Share and send access to the sales managers.

They click the link and see:

“To view this report, you need a Power BI Pro licence.”

IT says “we don’t want to buy Pro for everyone,” and you’re stuck between licence cost, governance, and a team that just wants to see the numbers.

We’ll use this scenario throughout and map it to the main sharing patterns.

The Three Core Questions Before You Share Anything

Before you decide how to share a Power BI report, answer these three questions:

1. Where will the report live?

   • My Workspace
   • A shared workspace in a shared capacity (default)
   • A workspace in Premium capacity (Power BI Premium per capacity or Fabric capacity)

2. What licence do viewers have?

   • Power BI free
   • Power BI Pro
   • Power BI Premium Per User (PPU)

3. Are viewers internal, external, or anonymous?

   • Internal users in the same tenant
   • External users (B2B) from other organisations
   • Public/anonymous viewers (no sign-in)

Most confusion about “Does everyone need a licence?” comes from mixing these three.

Licence Basics: Who Needs What to View a Report

Power BI Free

Free licence users can:

• View content in workspaces backed by Premium capacity, if they have permission.
• Use Power BI apps or report links pointing to Premium-backed content.

Free users cannot:

• View content in a Pro-only workspace.
• Use the standard Share feature to receive reports from Pro users in shared capacity.

Power BI Pro

Pro users can:

• Publish to and share from shared capacity workspaces.
• View content in any workspace they have access to (shared or Premium).
• Create and manage Power BI apps.

In non‑Premium environments, every user who consumes shared content must have Pro.

Power BI Premium Per User (PPU)

PPU adds extra capabilities (larger dataset sizes, some advanced features) but for sharing:

• Content in a PPU workspace can only be viewed by users with PPU.
• Pro or free users cannot consume PPU content.

PPU is useful for advanced workloads, but it does not solve the “free viewers” problem.

Power BI Premium Capacity / Fabric Capacity

When a workspace is assigned to Premium or Fabric capacity (with Power BI enabled):

• Authors still need Pro to publish and manage content.
• Free users can view reports and apps hosted in that Premium-backed workspace, if they have access.

This is the main way to avoid buying Pro for every viewer.

Mapping the Scenario: Sales Report + Mixed Licences

Back to our sales team:

• You (author): Power BI Pro
• Sales managers: Power BI free
• Workspace: A normal shared workspace in shared capacity (default, no Premium)

In this setup:

• When you share the report, each manager must have Pro to view it.
• If they don’t, they’ll see the “need Power BI Pro” message.

There are only three reliable ways out:

1. Give all viewers Pro licences.
2. Move the report to a workspace in Premium/Fabric capacity and share from there.
3. Use Publish to web (only for truly public content; usually not acceptable for internal sales data).

Let’s walk through the main sharing methods and where licences bite you.

Method 1: Direct Sharing From the Report (Pro → Pro)

This is the simplest pattern when everyone has Pro.

Steps

1. Publish the report from Power BI Desktop to a shared workspace.
2. In the Power BI service, open the report.
3. Click Share.
4. Add users or groups (preferably security groups or Microsoft 365 groups).
5. Choose permissions:
   • Can view (default)
   • Optionally allow Share or Build permissions
6. Send.

Licence Rules

• Workspace in shared capacity.
• Author: Pro.
• Viewers: Pro.

If any viewer doesn’t have Pro, they’ll be blocked.

When to use

• Small teams where everyone already has Pro.
• Early-stage deployments before Premium is in place.

For our sales scenario, this works only if IT agrees to give Pro to the sales managers.

Method 2: Power BI Apps (Pro authors, Pro or free viewers depending on capacity)

Apps are the main scalable pattern for business users.

Why apps

• Stable URL, versioned bundles of reports and dashboards.
• Easier permission management via groups.
• Cleaner experience for non‑technical users.

Steps to publish an app

1. Put the dataset and report in a workspace.
2. Make sure you have Admin / Member rights in that workspace.
3. In the workspace, click Create app.
4. Configure:
   • Content: select which reports/dashboards to include.
   • Audience: choose users/groups, or multiple audiences.
5. Click Publish app.

Licence Rules

• Workspace in shared capacity:

  • Author: Pro
  • Viewers: Pro

• Workspace in Premium/Fabric capacity:

  • Author: Pro
  • Viewers: free or Pro

So for our sales team, if IT moves the Sales workspace to Premium capacity:

• You keep your Pro licence.
• Sales managers with free licences can access the app and view the report.

This is usually the cleanest setup for widely shared internal reports.

Method 3: Share in Premium Capacity (Free Viewers Allowed)

The key shift is where the workspace is hosted, not how you share.

Moving a workspace to Premium/Fabric capacity

(Exact UI wording can vary slightly by tenant, but the pattern is consistent.)

1. In the Power BI service, go to Workspaces.
2. Open the workspace that holds your report.
3. In Workspace settings, find Advanced or Capacity.
4. Set Capacity to a Premium or Fabric capacity that your tenant owns.

Once the workspace is Premium-backed:

• Reports and apps in that workspace can be viewed by free users.
• Sharing via Share or Apps respects this: viewers with free licences can open content.

Governance considerations

• IT controls which workspaces can be Premium.
• Capacity has limits (memory, refresh, concurrency); don’t move everything blindly.
• Use separate workspaces for different business domains and data sensitivity.

For the sales scenario, this is the typical outcome:

• IT enables a Premium/Fabric capacity.
• The Sales workspace is moved to that capacity.
• Sales managers (free licence) get the app and can finally see the report.

Method 4: Publish to Web (Public, Anonymous Access)

Publish to web is often misunderstood as a way around licences. It is not a general solution for internal reporting.

What it does

• Generates an anonymous public URL and an embed code.
• Anyone with the link can view the report without signing in.

Licence rules

• Author: Pro.
• Viewers: no licence required, but content is publicly accessible.

Risks and constraints

• Intended for public, non‑sensitive content (e.g. website visuals).
• Many organisations disable Publish to web at the tenant level.
• Not suitable for internal sales data, HR data, finance, etc.

For our sales team scenario, Publish to web is not appropriate unless the data is fully anonymised and intended for public consumption.

Method 5: External Sharing (B2B) and Licence Impact

Sometimes your colleagues include partners or contractors in other tenants.

Azure AD B2B sharing

• You invite external users as guest users to your tenant.
• They sign in using their own organisation account.

Licence rules

• If the content is in a shared capacity workspace, external viewers need Pro.
• If the content is in a Premium/Fabric capacity workspace, external viewers can be free.

External sharing doesn’t change the fundamental licence logic; it just adds identity and governance overhead.

Method 6: Share to Teams or SharePoint (Still Licence‑Driven)

Embedding reports in Teams or SharePoint often creates the illusion that licences don’t matter. They still do.

Teams

• You add a Power BI tab to a Teams channel.
• You select a report or app.

Viewers:

• Must have access to the report/app in Power BI.
• Must meet the same licence rules as if they opened the report directly:
  • Shared capacity workspace → Pro viewers.
  • Premium/Fabric workspace → free or Pro viewers.

SharePoint Online

• You use the Power BI web part to embed a report.

Same pattern:

• SharePoint permissions are not enough.
• Power BI licence + workspace capacity still control who can see the report.

Embedding is a UX decision, not a licence workaround.

Common Failure Modes and How to Fix Them

1. “You need a Power BI Pro licence to view this report”

Cause:

• Workspace is in shared capacity.
• Viewer has free licence.

Fix options:

1. Give the viewer a Pro licence.
2. Move the workspace to Premium/Fabric capacity and keep sharing.

2. Viewer sees nothing in the app

Cause:

• App audience doesn’t include that user or group.
• Or workspace permissions don’t align with app audience.

Fix:

• In the app settings, add the user/group to the Audience.
• Ensure they have at least Viewer role on the workspace or appropriate permissions via app.

3. External users can’t open the report

Cause:

• Not added as guest users.
• Sharing settings for external users disabled at tenant level.
• Licence mismatch (PPU vs Pro vs free).

Fix:

• Work with IT to enable B2B and add guests.
• Ensure workspace capacity and licences align with the external sharing pattern.

Practical Patterns: Choosing the Right Sharing Model

For experienced teams, the decision usually falls into one of these patterns.

Pattern A: Small team, mostly authors

• Everyone has Pro.
• Use shared capacity workspaces.
• Share via Apps or Share.

Pattern B: Large audience of business users

• Authors: Pro.
• Many viewers: free.
• Use Premium/Fabric capacity.
• Publish via Apps.

Pattern C: Public reporting

• Authors: Pro.
• Viewers: no licence.
• Use Publish to web for non‑sensitive content only.

Our sales scenario fits Pattern B once the organisation invests in Premium/Fabric.

One Concrete Takeaway: Decide Licence Model Before You Build Sharing Flows

The fastest way to avoid the “nobody can see the report” situation is to answer one question up front:

Will most viewers have Pro, or do we need free viewers to access reports?

If most viewers will be free:

• Push for a Premium/Fabric capacity.
• Plan workspaces and apps around that capacity.

If most viewers will be Pro:

• Keep things in shared capacity.
• Use direct sharing or apps as needed.

Aligning your workspace capacity and licence model early saves you from re‑architecting sharing later when the access errors start appearing.