How to Share Power BI Reports Without a Pro License

There are two honest ways to share Power BI reports without a Pro license for every viewer. Either the report leaves Power BI's security model — a public link, a PDF, a copied file — or it is served from capacity that carries the viewers: a Fabric F64 or larger capacity, or Power BI Embedded inside an application you build. Everything in between, including putting the report in a Microsoft Teams tab or on a SharePoint page, still checks each viewer's license. This page walks through every route, what it costs you in security or effort, and where the line sits.

It is deliberately narrow. If you own a Power BI Premium P SKU and the renewal is what brought you here, read Power BI Premium to Fabric migration first, because the capacity you move to decides whether your free viewers keep access. If the question is Copilot rather than viewing, see Power BI Copilot licensing requirements. And for the whole budget rather than the viewer line alone, see Power BI implementation cost for small business.

Who needs a Pro license to view a Power BI report?

In most organizations, everyone who opens a shared Power BI report needs a Pro or Premium Per User license, and so does the person sharing it. The exception is capacity: when the report sits in a workspace on Fabric F64 or larger, or a Power BI Premium P SKU, viewers with a free license can open it.

A free license is not useless. A free user can build reports in Power BI Desktop, which costs nothing, and publish them to their own My workspace. What they cannot do is share that content or collaborate on it with anyone else. Sharing, apps, workspace roles and email subscriptions to other people are all paid features unless the workspace is on capacity that covers its viewers.

Before you look for a workaround, check what you already own. Some Microsoft 365 plans, such as Microsoft 365 E5, include Power BI Pro for every licensed user, and the Microsoft 365 admin center shows which licenses are assigned to whom. Microsoft keeps the current per-user and capacity figures on its Power BI pricing page; we do not repeat them here because they change.

Does Publish to web avoid the license, and what does it expose?

Publish to web removes the license requirement by removing security entirely. It generates a public link and embed code that anyone on the internet can open, with no sign-in. Microsoft warns the report can be found and viewed by anyone, so it is only for data you would happily post on your public website.

In practice that means published statistics, public-sector open data, or a marketing chart — never sales figures, payroll, customer lists or anything under a confidentiality agreement. The link can be forwarded and indexed, row-level security cannot be applied to it, and a Power BI administrator can switch the feature off for the whole tenant, which many organizations do by default.

Do not confuse it with the secure Embed report in a website or portal option. That one also produces an embed code, but every viewer has to sign in and is checked for permission and license exactly as in the Power BI service, so it solves a placement problem rather than a licensing one.

Can you share a report as a PDF, PowerPoint or .pbix file instead?

For a handful of readers, a PDF or PowerPoint export is often the honest answer. A licensed author exports the report and sends it like any document. The reader needs no Power BI license, but gets a static snapshot: no filters, no drill-through, and figures that are only current as of the export.

That trade is fine for a monthly board pack or a client summary where the reader wants the answer, not the tool. It is a poor fit for anyone who needs to slice the numbers themselves, and once the file leaves your mailbox you cannot revoke it, so treat it with the same care as any spreadsheet export.

Sending the .pbix file itself is the riskier cousin. Power BI Desktop is free, so the recipient gets a fully interactive report — and the entire data model behind it. Row-level security does not protect data from someone who holds the file, the refresh needs credentials they should not have, and there is no record of who has a copy. We advise against it for anything beyond test data.

Does embedding in Teams or SharePoint get around the license?

No. Embedding a report in a Teams tab or a SharePoint page changes where it appears, not who may open it. Power BI checks each viewer's permissions and license exactly as it does in the Power BI service, so a free user cannot open it unless the workspace is on F64 or Premium capacity.

This is the most common error in the advice that circulates on this question. Several explainers present a Teams tab or the SharePoint Online Power BI web part as a way to reach colleagues who have no Pro license. Microsoft's own documentation on licenses for business users says otherwise: free-license users can view and interact with content only when it is hosted in Premium or Fabric F64-or-larger capacity, wherever that content is displayed.

Teams and SharePoint are still worth using. They put the report where people already work and reduce the number of links to manage. They just do not change the licensing arithmetic, so make that decision first and choose the surface second.

When does Fabric F64 capacity make free viewers cheaper?

F64 is the point at which licensing flips from per viewer to per capacity. On a Fabric F64 or larger capacity, people with a free license can view content shared with them, while authors still need Pro or Premium Per User. Below F64, on F2 to F32, every viewer still needs a paid license.

Whether F64 is cheaper is arithmetic you do with Microsoft's current figures: the number of people who only read reports, multiplied by the per-user license, set against the cost of an F64 capacity billed through Azure. A team of report readers numbering in the dozens rarely gets there; an organization handing dashboards to hundreds of frontline staff often does. Measure the viewer count from real usage before you decide, not from the org chart.

Two details catch people out. A smaller F SKU bought for compute reasons does not carry free viewers, so a business that right-sizes from a P1 to an F32 can find it suddenly needs a paid license for every reader — the subject of our Premium to Fabric migration guide. And free viewers on F64 are viewers only: anyone who edits, publishes or shares still needs Pro or Premium Per User.

What about clients and other external users?

External users follow the same rule as staff. A client invited as a Microsoft Entra B2B guest needs a Pro or Premium Per User license, either from their own organization or assigned by yours, unless the content sits on F64 or Premium capacity. Building the report into your own application with Power BI Embedded is the other route.

Power BI Embedded in the embed for your customers pattern lets your application authenticate to Power BI on the user's behalf, so the people using your portal need no Power BI license and never sign in to Power BI. It runs on a capacity you pay for, and it is a development project: an application, a service principal, and row-level security mapped to your own users. Microsoft designs it for software and portals offered to customers; for your own employees, the embed for your organization pattern applies and each user is licensed as usual, so check Microsoft's product terms before using it to sidestep internal licenses.

When each client should see only their own figures, the security model matters more than the delivery route. Our Power BI row-level security implementation guide covers how to build that filtering so it holds up in either case.

How we help you pick the right route

Most of these decisions are made once and then paid for every month. We start from what you already own — the licenses assigned in the Microsoft 365 admin center, any existing capacity, where your workspaces sit, and who actually opens which report — and recommend the smallest setup that reaches your readers without exposing data you need to protect.

Work is led by Edward Pinela, MBA, and delivered remotely; the person who scopes it is the person who does it. For a bounded piece of work like this, Power BI Flex Support is usually the right vehicle: it starts at $2,500 for 20 hours at $100–$125 per hour, in prepaid blocks whose hours never expire. If the answer turns out to be a broader rebuild, that belongs in a Power BI consulting engagement with its own scope.

Further reading: Microsoft Learn — licenses and subscriptions for Power BI business users.