Power BI offers five main ways to share dashboards and reports: direct link sharing, workspace access, Power BI Apps, embedding in SharePoint or Teams, and Publish to Web for public content. Each method has different license requirements and security implications. This guide covers all five with step-by-step instructions and a comparison table.
Key Facts
- Direct sharing requires both the sharer and recipient to have Power BI Pro or PPU licenses, or Premium capacity.
- Power BI Apps let you package multiple reports into a single branded app with controlled navigation.
- External users (outside your Azure AD tenant) need a Pro or PPU license to view shared reports unless you use Premium capacity.
- Publish to Web creates a public, unauthenticated URL — never use it for sensitive data.
- Row-level security (RLS) filters data based on the signed-in user — set it up before sharing reports with mixed-audience groups.
How to Share Power BI Dashboards and Reports
How to Share Power BI Dashboards and Reports
Power BI offers five main ways to share dashboards and reports: direct link sharing, workspace access, Power BI Apps, embedding in SharePoint or Teams, and Publish to Web for public content. Each method has different license requirements and security implications. This guide covers all five with step-by-step instructions and a comparison table.
Key facts
- Direct sharing requires both the sharer and recipient to have Power BI Pro or PPU licenses, or Premium capacity.
- Power BI Apps let you package multiple reports into a single branded app with controlled navigation.
- External users (outside your Azure AD tenant) need a Pro or PPU license to view shared reports unless you use Premium capacity.
- Publish to Web creates a public, unauthenticated URL — never use it for sensitive data.
- Row-level security (RLS) filters data based on the signed-in user — set it up before sharing reports with mixed-audience groups.
Sharing method comparison
| Method | License needed | External sharing | Best for |
|---|---|---|---|
| Direct link share | Pro or PPU (both parties) | Yes (guest users) | Ad-hoc sharing with known colleagues |
| Workspace member access | Pro or PPU | Yes (guest users) | Team-level access for collaborators |
| Power BI App | Pro or PPU (publisher), free for Premium viewers | Yes (guest users) | Broad org-wide distribution with navigation control |
| Embed in SharePoint | Pro or PPU (viewers) | Depends on SharePoint permissions | Intranet integration for M365 users |
| Embed in Teams | Pro or PPU (viewers) | Yes (guest Teams users) | Collaborative reporting in team channels |
| Publish to Web | None | Anyone with URL | Public data only — no authentication |
Method 1 — Direct link sharing
The fastest way to share a single report with colleagues.
- Open the report in Power BI Service. Click Share in the top menu bar.
- Enter email addresses or Azure AD group names.
- Choose permissions: Can view or Can edit. Decide whether recipients can reshare or download.
- Click Send. Recipients receive an email with a direct link to the report.
Limitation: each recipient needs a Pro or PPU license. For large audiences, use a Power BI App instead.
Method 2 — Workspace access
Add users to the workspace so they can access all reports and dashboards inside it.
- In the workspace, click Access in the top right.
- Enter a name or email and choose a role: Viewer, Contributor, Member, or Admin.
- Viewer — read-only. Contributor — can publish reports. Member — full access except workspace settings. Admin — full control.
Use Azure AD groups instead of individual users. Group membership changes take effect automatically without updating workspace access manually.
Method 3 — Publish a Power BI App
Apps are the recommended way to distribute reports to large audiences.
- In the workspace, click Create app in the top right.
- Configure the Setup tab: app name, description, logo, and contact email.
- In the Navigation tab, add the reports and dashboards you want to include. Set the order and create section headers.
- In the Permissions tab, add the audience groups (Azure AD groups or entire organization).
- Click Publish app. The app appears in the Power BI App catalog for assigned users.
Apps update automatically when you publish changes to the workspace. Audience members always see the current version without needing a new link.
Method 4 — Embed in SharePoint Online
- In Power BI Service, open the report and click File → Embed report → SharePoint Online.
- Copy the embed link provided.
- In SharePoint, edit the page and add a Power BI web part.
- Paste the embed link. Configure the web part size and display options.
- Publish the SharePoint page. Users with Power BI Pro licenses see the live report on the SharePoint page.
Method 5 — Embed in Microsoft Teams
- In a Teams channel, click the + tab button at the top of the channel.
- Select Power BI from the app list.
- Search for and select your report. Choose whether to post a notification to the channel.
- The report appears as a tab. Team members with Pro licenses can interact with it directly in Teams.
Security controls before sharing
Apply these controls before sharing any report that contains sensitive data.
- Row-level security (RLS) — filter data based on the signed-in user's identity. Set up RLS roles in Power BI Desktop before publishing. Test each role before sharing broadly.
- Sensitivity labels — apply a Microsoft Purview sensitivity label (Confidential, Highly Confidential) to the dataset. Labels restrict download, printing, and external sharing automatically.
- Tenant settings — review Power BI tenant settings in the Admin portal. Restrict external sharing, disable Publish to Web for non-admins, and limit export formats.
- Workspace access controls — use the least-privilege role. Viewers cannot publish or reshare. Contributors cannot manage workspace settings.
Frequently asked questions
Can I share a Power BI report with someone outside my company?
Yes. Add them as a guest in Azure AD, then share the report or add them to the workspace. External guests need a Power BI Pro or PPU license — either their own or one assigned in your tenant. Premium capacity removes the per-user license requirement for external viewers.
What is the difference between sharing and publishing an app?
Sharing gives access to a specific report or dashboard link. A Power BI App packages multiple reports into a single catalog entry with controlled navigation. Apps are better for large, stable distributions. Sharing is better for ad-hoc access to a single report.
Is Publish to Web safe for internal reports?
No. Publish to Web creates a completely public URL with no authentication. Anyone with the URL can view the report — including people outside your organization. Only use it for publicly available data like open government statistics or public product catalogs.
Do report viewers need Power BI Pro?
Yes, unless the workspace is on Premium or Fabric capacity. With Premium capacity, viewers with free licenses can consume content published as a Power BI App. Viewers never need Pro to see a Publish to Web report (because it is public).
Can I schedule automatic report delivery by email?
Yes. Use subscriptions in Power BI Service. Open the report → Subscribe → Add yourself or others. Set the delivery schedule (daily, weekly) and whether to include an image of the report page. Recipients need a Pro license to receive report subscriptions.
Get expert help with Power BI distribution
EPC Group designs Power BI workspace governance, app publishing, and embedded analytics solutions for Fortune 500 clients. Call (888) 381-9725 or request a 30-minute discovery call.
Why Organizations Choose EPC Group
EPC Group is a Houston-based Microsoft consulting firm with 29 years of enterprise implementation experience and over 10,000 successful deployments across Power BI, Microsoft Fabric, SharePoint, Azure, Microsoft 365, and Copilot. We serve organizations across all industries including Fortune 500, federal agencies, healthcare, financial services, government, manufacturing, energy, education, retail, technology, and global enterprises.
What sets EPC Group apart is our governance-first approach. Every engagement begins with a security and compliance assessment. Our team of senior architects brings hands-on delivery experience across HIPAA, SOC 2, FedRAMP, and CMMC environments. We own outcomes, not hours.
- Fixed-fee accelerators with predictable pricing and defined deliverables
- Senior architect engagement on every project, not rotating juniors
- Compliance-native delivery for regulated industries
- End-to-end coverage from strategy through 24/7 managed services
- 11,000+ enterprise engagements refined into repeatable, risk-controlled patterns
Call (888) 381-9725 or email contact@epcgroup.net for a free assessment.
Power BI Strategy: 2026 Considerations for How To Share My Power BI Dashboards And Reports
Power BI Copilot grounds itself on the semantic model, NOT the underlying source data. That means Copilot answers are only as accurate as the DAX measure definitions, the field metadata (display folders, descriptions, hierarchies), and the synonyms taxonomy. In practice, the difference between a Copilot deployment that drives 32% time-savings and one users abandon within 90 days is whether the semantic model was Copilot-prepared.
Power BI capacity sizing in 2026 starts with the F-SKU economics: F2 ($263/mo) covers small workloads with up to 4 GB of memory and roughly 30 reports, F4 ($526/mo) handles a typical mid-market deployment with semantic-model refresh windows under 10 minutes, and F64 ($5,257/mo) is the sweet spot for enterprises consuming Power BI alongside Microsoft Fabric data engineering, lakehouse storage, and real-time intelligence. Capacity right-sizing should be revisited every 90 days because Microsoft adjusts F-SKU memory allocations, paginated report performance, and Direct Lake mode availability with each major service update.
Decision factors EPC Group evaluates
- Copilot grounding quality assessment of semantic-model metadata
- Direct Lake mode adoption for Fabric-resident semantic models
- License optimization audit (Pro vs Premium Per User vs F-SKU)
- Row-level security via service principal authentication
- Capacity sizing decision (F2/F4/F64+) tied to peak concurrent users and refresh window
See related EPC Group services at /services or schedule a discovery call at /contact.