All insights
GrowPower BI & FabricHow-To Guide

Sharing Power BI without overspending: workspaces, apps, and who needs Pro

A walkthrough of Power BI workspace roles, publishing a polished App to a wide audience, who actually needs a Pro license to view versus build, and how Fabric capacity changes the math.

Wired CIOMay 23, 2026
The short version
  • Use workspace roles (admin, member, contributor, viewer) to control who builds versus who reads.
  • Publish a polished App to a wide audience rather than handing out the raw workspace.
  • Most viewers need a Power BI Pro license, so count your audience before you promise access.
  • Fabric capacity changes the math only at higher volume; below that, per-user licensing is cheaper.
Bottom line: Share through an App with the right workspace roles, and license per user until your audience is big enough to justify a capacity.

Sharing a Power BI report sounds like it should be one click, and then the licensing questions start. Who needs to pay? Why can some people open the report and others get a wall asking them to start a trial? This guide is for the person standing up Power BI (Microsoft's reporting and dashboard tool) for a growing team. By the end, you'll know how workspace roles work, how to publish a clean App to a wide audience, exactly who needs a Power BI Pro license to view versus build, and the point where Microsoft Fabric capacity changes the cost math.

Before you start

You'll want a few things in place first:

  • A Power BI workspace where your reports already live, and the Admin or Member role on it.
  • A short list of who needs to see reports versus who needs to build them. That split drives the whole licensing decision.
  • A rough headcount of viewers. Once you cross a few dozen, the Fabric capacity option below starts to pay for itself.
  • Permission to involve whoever manages your Microsoft 365 licenses, since assigning Pro seats is a billing change.
Workspace role or App Build, or just read? Build Read Workspace role + Pro Authors edit and publish RECOMMENDED Publish an App Viewers still need Pro
Readers get an App, not a workspace seat.

Step 1: Understand the four workspace roles

A workspace is the shared container where reports, dashboards, and semantic models (the data behind a report) live. Every person you add gets one of four roles, and each role is a bundle of permissions:

  • Admin: full control, including adding and removing other people and deleting the workspace.
  • Member: can publish, edit, and share content, and add people at Contributor or below.
  • Contributor: can create and edit content in the workspace but can't manage access.
  • Viewer: can open and read content, and nothing else.

A good rule: your report authors get Member or Contributor, and almost nobody else should be in the workspace at all. The workspace is your workshop, not your storefront. To set roles, open the workspace, click Manage access in the top right, then Add people or groups.

Use Groups, Not Names

Add Microsoft 365 security groups, not individual names. When someone joins or leaves a department, you change one group membership instead of editing every workspace by hand.

Step 2: Publish an App for your wide audience

Don't hand the whole audience Viewer access to your working workspace. Publish an App instead. An App is a clean, read-only package built from the workspace: you choose which reports go in it, arrange them with navigation, and push it to a defined audience. Your half-finished drafts stay hidden.

  1. Open the workspace and click Create app (top right). If you've published before, the button reads Update app.
  2. On the Setup tab, give the App a name, a description, and optionally a logo and theme color.
  3. On the Content tab, add the specific reports and dashboards you want included, and drag them into the order and navigation sections you want.
  4. On the Audience tab, name the audience and add the security group that should see it. You can build more than one audience (for example, a leadership group that sees extra pages) from the same App.
  5. Click Publish app, then copy the App link to share.

When you change a report later, those edits don't reach the audience until you click Update app again. That's a feature: it lets you stage changes and release them on your schedule.

Step 3: Sort out who actually needs Power BI Pro

This is where the bill comes from, so be precise. The default rule, without any Fabric capacity in the picture:

  • Anyone who builds or publishes content (your report authors, the Member and Contributor roles) needs a Power BI Pro license. As of 2026, Pro is about 14 US dollars per user per month.
  • Anyone who only views shared content also needs Pro under the default model. This is the part that surprises people: in a plain workspace, a viewer with no license hits a prompt to start a trial and can't open the report.

So if you have five authors and eighty viewers, the naive answer is eighty-five Pro licenses. That's almost never the right answer, which brings us to Fabric.

Step 4: Use Fabric capacity to stop paying per viewer

Microsoft Fabric is Microsoft's broader data platform, and you can buy capacity (a block of compute, sold as SKUs from F2 up to F64 and beyond) instead of per-user licenses for viewing. The threshold that matters: at F64 capacity and above, viewers with only a free Power BI license can open content, as long as both the report and its underlying semantic model live in a workspace assigned to that capacity, and the person has the Viewer role.

The trade-off:

  • Below F64 (F2 through F32), viewers still need Pro. Capacity at those sizes buys you performance and Fabric features, not free viewing.
  • At F64 and above, you stop buying Pro for viewers entirely. You still need Pro (or Premium Per User) for the people who build.

The math tips when the cost of one F64 is less than buying Pro for all your viewers. With eighty-plus viewers, that crossover often arrives. Run the numbers for your actual headcount before you commit either way.

Step 5: Share with external or guest users

To share with someone outside your tenant (a client or a partner), they're added as a guest in Microsoft Entra ID (Microsoft's cloud identity service), and the default rules still apply: they need their own Pro license unless your content sits on F64-or-higher capacity. External sharing also has to be allowed in the Power BI admin portal under Tenant settings > Export and sharing settings. If guests hit an error, that tenant switch is the first place to look.

Step 6: Verify it before you announce it

Don't trust your own admin account as the test, since you can see everything anyway. Instead:

  1. Ask one person from the target audience (ideally someone with only a free license) to open the App link.
  2. Confirm they can read every page you intended and can't reach anything you didn't include.
  3. Check that nobody outside the audience can open it.

If a free-license viewer gets a trial prompt, your workspace isn't on F64-or-higher capacity, and you're back to needing Pro for that person. That's the signal to revisit Step 4.

What to do next

Decide your split: count your builders, count your viewers, and price Pro-for-everyone against one Fabric capacity. Then publish through Apps with group-based audiences so access stays easy to manage as people come and go. If you'd like a second set of eyes on the licensing math before you buy, that's exactly the kind of question we're glad to walk through with you.

Filed under
How-To Guide
Read more insights
Free strategy session

See where you stand. Then move forward.

Book a free intro call. We'll talk through where you are today and map a strategic plan for growth, protection, automation, and alignment.

A 30-minute discovery call, no obligationA full team of specialists at a fraction of in-house costA clear next step before you spend a dollar
Loading scheduler…