Sharing a Power BI report with someone outside your organisation should be a five-minute job. In practice it's a maze of guest accounts, Pro licences, capacity decisions, and "you don't have permission" pop-ups. This guide cuts through it: five methods, when each one fits, and how the licensing maths actually works in the Microsoft Fabric era (2026).
TL;DR — five ways to share Power BI reports externally
Skip the long read if you just want the verdict:
Why this is harder than it should be
Power BI was built for in-tenant sharing. Every other use case — sharing with customers, partners, agency clients, vendors, suppliers — is bolted on. That's why you'll hit the same friction every time you try:
- External people have to be invited into your Microsoft Entra directory as guests.
- Each guest needs their own Pro or PPU license, unless the workspace sits on a capacity.
- Your tenant admin has to switch on external sharing before any of it works.
- Non-technical clients get stuck on the Microsoft login.
- The reports keep Microsoft's branding, not yours.
Method 1 — Direct sharing through the Power BI service (Entra B2B guest)
Upload your report from Power BI Desktop with the Publish button, open the workspace access settings in app.powerbi.com, and invite the external user. They'll be added to your Microsoft Entra directory as a B2B guest.
You may see this notice the first time:
To unblock it, your Power BI tenant administrator needs to toggle External data sharing on in the admin portal. Each invited guest then needs a Pro or PPU licence — unless your workspace sits on a Premium or Fabric capacity (more on that under method 4).
When this fits: a handful of named partners who are themselves comfortable with Microsoft 365. When it doesn't: client-facing dashboards at any meaningful scale.
Method 2 — Publish to Web
If your report contains only public information, this is the fastest option ever invented. Open the report and click File → Embed report → Publish to web.
You get a public URL anyone can visit. No authentication, no row-level security, no licence requirement. Treat it like publishing to YouTube: assume the world will see it.
When this fits: public marketing dashboards, conference KPIs, open data. When it doesn't: anything containing customer, financial, or proprietary information.
Method 3 — Static export (PDF, PowerPoint, scheduled email)
From the Export menu in Power BI Service, you can generate a PDF or PowerPoint of any report and email it manually. Or use Subscribe to schedule an automated email with a snapshot.
Recipients don't need a Power BI licence — they're just receiving a file in their inbox.
When this fits: weekly status snapshots to a fixed audience, exec digests, simple recurring reports. When it doesn't: anything that needs filtering, drill-through, or self-service.
Method 4 — Power BI Embedded on Microsoft Fabric capacity (DIY)
Power BI Embedded with the app-owns-data model is the gold standard for external analytics at scale. A service principal (an "app identity") connects to Power BI on behalf of all your viewers, so individual viewers never authenticate to Power BI directly. They authenticate to your application.
This means:
- Viewers never need a Power BI license.
- Viewers never need a Microsoft account.
- You control authentication, branding, and access inside your own app.
- Row-level security is passed through the embed token, so each viewer sees only their own data.
The catch: you need a Fabric capacity (F-SKUs start at around €256/month for F2, scaling up by workload), and you need developer time to build the embedding logic, authentication handoff, error handling, refresh tokens, and the portal UI itself. Plan on weeks-to-months of engineering for a production-grade implementation.
When this fits: SaaS products embedding analytics, internal dev teams with the bandwidth to own a portal. When it doesn't: teams without dedicated frontend developers, or anyone who needs to be live in a week.
Method 5 — White-label portal via DataTako (no-code)
DataTako is the shortcut for method 4. We've already built the embedding layer, the auth flow, the user management, the RLS mapping, the email subscriptions, and the white-label portal. You connect DataTako to your existing Power BI workspace, configure branding and access rules, and your external viewers get a fully white-label experience — typically live in hours rather than months.
The licensing model is the same as method 4 (Fabric capacity), so the savings are identical: no Pro/PPU licence per viewer, no guest accounts in your tenant. The difference is the time and cost to get there.
See the full feature list or compare plans.
Cost comparison: when does the no-licence model actually pay off?
For internal sharing of 5-10 people, Pro licences are cheaper. The break-even point for the capacity-based model (methods 4 and 5) is roughly 30 external viewers — past that, every additional viewer is effectively free, while every additional Pro licence costs around €10/month. At 100 external viewers the savings are ~60%; at 500+ the comparison stops being a comparison.
For more on the underlying capacity decision, see Which Fabric capacity do I need? and Microsoft Fabric features, capacities, and saving on Power BI Pro licences.
Decision shortcut
- Is your data public? → Publish to Web
- Just a handful of partners on Microsoft 365? → Entra B2B guest
- A fixed audience who only need a snapshot? → Scheduled PDF / PowerPoint export
- Private data, many viewers, you have developers? → Power BI Embedded on Fabric (DIY)
- Private data, many viewers, client-facing, no dev time? → DataTako white-label portal
Frequently asked questions
How do I share a Power BI report with external users?
The five methods above all work. The fastest is Publish to Web (30 seconds) if your data is public. The most professional for a small audience is Entra B2B guest sharing. For anything client-facing or at scale, embed via Fabric capacity — either DIY (method 4) or white-label via DataTako (method 5).
Can I share Power BI reports with external users without a Pro licence?
Yes, but only with two specific approaches: Publish to Web (which makes the report fully public) or by using Power BI Embedded on a Fabric/Premium capacity (which lets unlimited external viewers in without per-user licences). The standard Power BI Service "share with external user" flow does require a Pro or PPU licence per recipient.
Do external users need a Microsoft 365 account to view Power BI reports?
Only for methods 1 and (in some configurations) 4. With Publish to Web, static exports, or an embedded portal using app-owns-data (methods 2, 3, 4-with-app-identity, and 5), external viewers don't need a Microsoft 365 account. They authenticate to your app, not to Microsoft.
What's the cheapest way to share Power BI dashboards with many external viewers?
Past about 30 external viewers, Power BI Embedded on a Fabric F-SKU is consistently the cheapest model. The capacity cost is fixed; viewer count doesn't change it. Per-user Pro licences scale linearly forever. DataTako pricing includes the cost comparison calculator.
How do I share a Power BI report with free users?
"Free users" usually means people without a Power BI Pro licence. Three options: (a) Publish to Web for public data, (b) static PDF/PPT export for a fixed audience, or (c) embedded portal on Fabric capacity for unlimited interactive viewers without per-user licensing. See Power BI guest user access: pros, cons, and alternatives for the full breakdown.
What's the difference between Power BI Pro, Premium, and Embedded for external sharing?
Pro is per-user — every viewer (internal or external guest) needs a licence. Premium / Premium Per User (PPU) still has per-user variants but Premium capacity (P-SKUs, now F-SKUs under Microsoft Fabric) lets unlimited viewers consume content as long as the workspace sits on the capacity. Power BI Embedded uses the same capacity model but is intended for app-owns-data scenarios where viewers authenticate via your application, not Microsoft.
Is Publish to Web safe for sharing reports externally?
Only for genuinely public data. Publish to Web creates a public URL with no authentication and no row-level security. Anyone who finds or guesses the URL can view the report. Search engines can index it. Use it for marketing dashboards and open data; never for customer data, financials, or anything proprietary.
How does Microsoft Fabric capacity change Power BI external sharing?
Microsoft Fabric (the F-SKU capacity model that's replacing P-SKUs) keeps the same "no per-user licence for capacity-hosted workspaces" rule that Premium had, with more granular pricing tiers and pause/resume billing. For external sharing, this means F-SKU is now the standard underlying capacity for both DIY embedded portals and white-label tools like DataTako. Pay-as-you-go vs reserved capacity covers the cost trade-offs.
Can I share Power BI reports with users from another Microsoft 365 tenant?
Yes, via Entra B2B (method 1), but you'll need their tenant admin to allow guest access, and each guest will need a Pro or PPU licence. For multi-tenant scenarios with many external organisations, embedding via Fabric capacity bypasses the cross-tenant permissions problem entirely.
How do I securely share Power BI reports with external clients?
"Secure" means three things: authentication (only authorised viewers see the report), row-level security (each viewer sees only their data), and auditing (you can see who looked at what). Methods 1, 4, and 5 all support all three. Method 2 (Publish to Web) supports none. See Power BI external sharing without Microsoft 365 guest accounts for the secure-without-guests pattern.
How do I share a Power BI report outside my organisation?
Same five methods. The friction increases when "outside your organisation" means clients you don't control: guest invites bounce, Microsoft accounts confuse non-technical users, branding stays Microsoft. That's why for client-facing dashboards method 5 (white-label portal) tends to win on time-to-live and user experience.
What's the easiest way to share Power BI dashboards externally without involving IT?
Without IT: Publish to Web for public data, or scheduled PDF/PowerPoint export for a fixed audience. If you need interactivity and security without IT involvement on the embedding side, DataTako handles the IT layer for you — you only need access to the Power BI workspace and DataTako does the rest.
Get started
If you've decided method 4 or 5 is the right model and you'd rather skip the months of development work, start a free DataTako trial — full features, no credit card. Your viewers get a branded portal, you keep your Pro licensing for builders only, and you go live this week. Or book a 15-minute walkthrough to see it on your data.
