Power BI articles

Share Power BI Reports With External Users

There are five ways to share Power BI reports with external users: guest access through Microsoft Entra B2B, a Power BI app shared with those guests, scheduled PDF email subscriptions, publish to web, and embedded analytics on Fabric F or Power BI Embedded capacity. Each trades per-viewer licensing against security and effort, and most SMBs need only one or two.

Guest access via Microsoft Entra B2B (formerly Azure AD B2B)

Guest access is the default way to give a client, partner or board member a live, interactive report. You invite their email address into your Microsoft Entra tenant as a B2B guest, share the report or workspace with them, and they sign in with their own work account. Every view is authenticated, logged and revocable.

How it works. Your Fabric admin turns on the tenant setting that allows inviting external users, and whoever invites needs a Pro or Premium Per User license. You can send planned invites from the Entra admin center, or ad hoc invites simply by sharing a report or subscribing a guest. Workspace access lists only accept people who are already guests, so add them first if they will sit in a workspace role.

Licensing cost. On an ordinary Pro workspace, each guest needs Pro or Premium Per User — either a license their own company already assigned to them, or one you assign from your tenant. Move the workspace onto Premium capacity or a Fabric F64 or larger capacity and guests can view with a free license. Microsoft’s guide to distributing Power BI content to Entra B2B guests (opens in new tab) sets out the full consumer-by-workspace licensing matrix; contact Microsoft for current pricing on either path.

Security posture. Strongest of the self-service options. Row-level security applies to guests exactly as it does to staff, Conditional Access and multifactor authentication policies can be enforced, and removing the guest account cuts access everywhere at once. Guests on social identities such as Gmail can use the browser but not the Power BI mobile apps.

Best SMB use case. A handful to a few dozen named external people who need to filter, drill and explore — an outsourced finance team, a franchise owner, a key customer reviewing service levels.

Power BI apps for external audiences

A Power BI app bundles several reports and dashboards into one branded, read-only package with its own navigation. Shared with B2B guests through the app’s access list, it gives an external audience a curated portal instead of a raw workspace, and you can publish updates without touching their permissions.

How it works. You build the content in a workspace, publish an app from it, and add guests or a security group containing guests to the app audience. One catch: guests cannot install an app published to the entire organization, so external audiences must be named explicitly. Audiences let one app show different sections to different groups.

Licensing cost. The app does not change the licensing rule — it follows the workspace. On a Pro workspace every guest viewer still needs Pro or Premium Per User; on Premium or Fabric F64-plus capacity they can view free. Capacity is what turns an app into an unlimited-viewer channel, which is why apps and capacity are usually discussed together.

Security posture. Same identity controls as guest access, with less exposure: app viewers never see the workspace, the semantic model or unpublished drafts. Keep guests on the Viewer role at most if they also need workspace access.

Best SMB use case. A recurring client pack — a monthly portfolio, project or service review — delivered to the same external group with several related reports.

Scheduled email subscriptions (PDF export)

Email subscriptions send a report snapshot on a schedule, optionally with the full report attached as PDF or PowerPoint. They suit recipients who want numbers in their inbox rather than a login. The catch is licensing: external email addresses are only supported from workspaces on paid capacity, not Pro or Premium Per User workspaces.

How it works. A Pro or Premium Per User user with Contributor, Member or Admin rights opens the report, chooses Subscribe, adds recipients and sets a frequency. Full-report PDF or PowerPoint attachments need a Premium or PPU workspace and are capped at 20 pages and under 25 MB. Microsoft’s email subscriptions documentation (opens in new tab) lists the tenant settings involved.

Licensing cost. Recipients need no license to read the email. The subscription owner needs Pro or Premium Per User, and any external recipient requires the workspace to be on paid, non-PPU capacity — trial capacity is excluded too. Without capacity, the honest fallback is exporting the report to PDF by hand and emailing it like any other file.

Security posture. Moderate, and easy to underestimate. Once the email lands, the PDF is outside your control and can be forwarded. The preview image renders with the subscription owner’s permissions, not the recipient’s, so a report with row-level security can leak rows the recipient should never see. Sensitivity labels apply to attachments but not to the email body or preview image.

Best SMB use case. A fixed monthly statement to a lender, investor or parent company that reads the numbers but never needs to interact.

Publish to web (free but public — security tradeoffs)

Publish to web generates a public link and embed code that anyone on the internet can open without signing in. It costs nothing per viewer, which makes it tempting, but Microsoft is explicit that it exposes the report’s underlying data. It is a publishing tool for public information, not a sharing tool for clients.

How it works. An admin must enable the Publish to web tenant setting. A report author with edit rights then chooses File, Embed report, Publish to web, and pastes the resulting iframe into a website. Query results are cached for up to an hour, so it is a poor fit for frequently refreshed data.

Licensing cost. Viewers need nothing. Publishing from a shared workspace requires the author to hold Pro or Premium Per User, and that author must keep access for the embed code to keep working.

Security posture. None by design. Microsoft’s publish to web documentation (opens in new tab) warns that viewers can reach detail-level data in the model even when visuals do not display it. Reports using row-level security, DirectQuery or live connections are not supported. Restrict the tenant setting to a small security group and review active embed codes regularly — a control we build into every Power BI governance consulting engagement.

Best SMB use case. Genuinely public data: a nonprofit’s impact figures, a municipal-style dashboard, a marketing chart on your own website.

Embedded analytics (Power BI Embedded / F-capacity)

Embedded analytics puts Power BI reports inside your own web application or portal, where your customers sign in with your app’s credentials instead of a Microsoft account. Microsoft calls this “embed for your customers” or app owns data. Viewers need no Power BI license, but you need developer effort and paid capacity.

How it works. Your application authenticates to Power BI with a service principal, generates an embed token for each session, and renders the report through the Power BI JavaScript client. Row-level security is passed in the token, so each customer sees only their own data. Free trial tokens work for development, but production requires a purchased capacity.

Licensing cost. No per-viewer licensing. You pay for capacity instead — an Azure Power BI Embedded A SKU or a Microsoft Fabric F SKU — sized to the query load rather than the number of users. Contact Microsoft for current capacity pricing, and size it from real usage rather than the SKU name. Microsoft’s embedded analytics overview (opens in new tab) compares the customer and organization embedding models.

Security posture. Strong when built well, because access control moves into your application and every token is scoped. The risk is in the build: a bug in how tokens or row-level security roles are issued is your responsibility, not Microsoft’s.

Best SMB use case. A customer portal or software product where reporting is part of the offer and the external audience runs to hundreds or thousands of viewers.

The five methods side by side

The table compares all five delivery methods on what each external viewer costs, how the data is protected, how large an audience it handles comfortably, and where it fits best. Capacity figures as a cost in three rows because it is the lever that removes per-viewer licensing; pricing for it changes, so confirm current rates with Microsoft.

MethodPer-viewer costSecurityAudience sizeBest for
Guest access (Entra B2B)Pro or PPU per guest (theirs or yours); free on Premium or F64+ capacityStrong: signed-in, row-level security, Conditional Access, revocableA handful to a few dozen named peoplePartners and clients who need to explore live data
Power BI appSame as guest access; capacity makes viewing freeStrong, and viewers never see the workspace or modelDozens of named guests; more on capacityA curated, multi-report client pack
Email subscription (PDF)None for recipients; external addresses need paid capacityModerate: files can be forwarded; preview uses the owner’s permissionsAny mailing listFixed statements to lenders, investors or a parent company
Publish to webNoneNone: public, no sign-in, underlying data reachableUnlimitedPublic, non-sensitive data only
Embedded analyticsNone per viewer; you pay for A or F capacityStrong if built well: your app’s sign-in plus scoped tokensHundreds to thousandsCustomer portals and software products

Not sure which of these applies to your external report sharing? Ask a senior engineer.

Ask a question →

Choosing a method and getting it built

Start from the audience, not the feature list. Named partners who need to explore get guest access or an app; people who only read numbers get a subscription or a PDF; the public gets publish to web; paying customers at scale get embedded analytics. The internal side of the decision — whether your own staff sit on Pro or Premium Per User — is covered separately in Power BI licensing for small business, and it is worth settling first because the guest rules inherit from it.

Whichever route you choose, the tenant settings, guest lifecycle and embed-code reviews need an owner, or external access quietly sprawls. Our Power BI governance consulting scopes put those controls in writing, and our Power BI dashboard builds are designed with the external audience and row-level security in mind from day one. Every engagement is a fixed-fee, scoped project delivered by senior US-based Microsoft engineers. Microsoft Made Easy is a Lightray Solutions brand based in Orange County, California, serving clients across the US remotely.

FAQ

External sharing questions we hear most

Yes, in three cases. Guests can view with a free license when the workspace sits on Premium capacity or a Fabric F64 or larger capacity. Publish to web needs no license at all because it is public. Embedded analytics in your own app needs no viewer license, because you pay for the capacity instead.

On a Pro workspace, every guest needs Pro or Premium Per User. Microsoft accepts either a license their own organization already assigned to them or one you assign from your tenant. If the workspace is on Premium or Fabric F64-plus capacity, a free license is enough for viewing.

No. Microsoft warns that anyone on the internet can view a publish to web report with no authentication, including detail-level data in the model that the visuals never display. Row-level security is not supported, so it cannot show each client only their own rows. Reserve it for data you would publish anyway.

Scheduled subscriptions reach external addresses only from a workspace backed by paid, non-PPU capacity; trial and Premium Per User workspaces are excluded. The person creating the subscription needs Pro or PPU. Without capacity, the fallback is exporting the report to PDF yourself and attaching it to an ordinary email.

When reporting is part of what you sell: a customer portal, a SaaS product or a client extranet with too many viewers to license individually. Viewers sign in to your app, not Power BI, and you pay for A or F capacity. For a few dozen named partners, guest access is cheaper and far simpler.

Have a question about your external report sharing?

Book a free consultation and tell us what you’re trying to solve. You’ll get a written proposal with one fixed price, clear deliverables and a timeline, then you decide.

Free consultation · Written fixed price before any work starts · Reply within one business day

Book a free consultation

See what your Power BI project would take

Tell us what you’re trying to fix. We reply within one business day, and you get a written fixed-fee proposal to approve before any work begins.

Step 1 of 2: What do you need?

How can we help? Pick one

Tap to add, or type your own:

Step 2 of 2: Where should we reply?

Used only to contact you about this inquiry.

We reply within one business day. Fixed price approved before any work begins. We don’t sell your information.

Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.

  • Fixed-fee scope agreed before any work starts
  • Senior, US-based Microsoft engineers — no handoffs
  • Typical 2–4 week delivery
  • 30 days of post-delivery hypercare included
Book my free consultation