flowchart LR
A[Power BI Desktop <br> .pbix file] -->|Publish| B[Power BI Service <br> Workspace]
B --> C[Share via Link <br> or Email]
B --> D[Pin to <br> Dashboard]
B --> E[Embed in <br> Teams / SharePoint]
B --> F[Export <br> PDF, PPT, Excel]
B --> G[Publish <br> as App]
classDef default fill:#003366,color:#ffffff,stroke:#ffcc00,stroke-width:3px,rx:10px,ry:10px;
17 Publishing & Sharing Reports & Dashboards
Building an accurate, well-designed report in Power BI Desktop is the foundation. But a report that only exists on one person’s laptop delivers no organizational value. Publishing and sharing are the steps that transform a local file into a live, accessible resource that the right people can find, interact with, and act on.
This chapter covers the full publishing and sharing workflow: from sending a report to the Power BI Service for the first time, through the different ways to share it with colleagues, to embedding it in the tools your organization already uses every day and exporting it for offline consumption.
17.1 Publishing to the Service
17.1.1 Publishing from Power BI Desktop
Publishing sends your Power BI Desktop .pbix file to the Power BI Service. Behind the scenes, Power BI splits the file into two separate items that land in your chosen workspace: the dataset (the data model, relationships, Power Query steps, and DAX measures) and the report (the pages, visuals, and layout). These two items are independent once published. The dataset can power multiple reports and is refreshed on its own schedule. The report connects to the dataset and always shows data from the most recent refresh.
Publishing requires a Power BI account. To share content with others, both you and your recipients need a Power BI Pro or Premium Per User licence, or the content must be published to a Premium capacity workspace.
- Open your completed report in Power BI Desktop
- Go to the Home ribbon and click Publish
- If you are not already signed in, Power BI prompts you to sign in with your Microsoft organizational account
- The Publish to Power BI dialog appears, listing all workspaces you have access to. Select the destination workspace from the list
- Click Select. Power BI Desktop begins uploading the dataset and report. A progress indicator appears in the status bar at the bottom of the screen
- When the upload completes successfully, a dialog confirms the publication with a direct hyperlink to the report in the Service
- Click Open [report name] in Power BI to open the published report in your browser immediately
[Insert screenshot of the Publish to Power BI dialog showing a list of workspace names with one selected, and the Select button in the bottom-right corner of the dialog]
Each time you make changes in Power BI Desktop and click Publish again to the same workspace, Power BI prompts you to confirm that you want to replace the existing dataset and report. Clicking Replace overwrites both items with the updated version.
Any changes made directly to the report in the Power BI Service since the last publish (such as renamed visuals or page-level filters added in the browser) will be lost when you replace. For this reason, always treat Desktop as the source of truth and the Service as the distribution platform.
[Insert screenshot of the replacement confirmation dialog that appears when publishing to a workspace where the report already exists, showing the “Replace” and “Cancel” buttons with a message indicating the existing dataset and report will be overwritten]
Always double-check the destination workspace in the Publish dialog before clicking Select. Publishing to the wrong workspace exposes your report to the wrong audience. If you accidentally publish sensitive data to a shared workspace, remove the report and dataset from that workspace immediately using the workspace content management options in the Service.
A freshly published dataset contains a snapshot of the data at the time of publishing. Configure a scheduled refresh in the dataset Settings in the Power BI Service straight after publishing, so consumers always see current data. Do not leave a dataset without a refresh schedule in a shared workspace.
17.3 Embedding Reports
17.3.1 Embedding Reports in Teams, SharePoint, and Websites
Sharing a link to a report works when recipients are comfortable navigating the Power BI Service. But many organizations use Microsoft Teams as their primary collaboration hub and SharePoint as their intranet. Embedding Power BI reports directly inside Teams channels and SharePoint pages brings the data to where people already work, removing the friction of switching to a separate platform.
For public-facing data (published to the web), embedding allows reports to be surfaced on external websites without requiring viewers to have a Power BI account.
Embedding in Microsoft Teams
- Open the Microsoft Teams channel where you want to embed the report
- Click the + icon next to the tab bar at the top of the channel to add a new tab
- Search for and select the Power BI app from the tab gallery
- Sign in if prompted and select the report you want to embed from your workspaces
- Click Save. A new tab appears in the channel containing the fully interactive Power BI report
- Channel members can interact with the report (use slicers, drill down, apply filters) directly in Teams without leaving the application
[Insert screenshot of a Microsoft Teams channel with a Power BI report embedded in a dedicated tab, showing the report’s visuals rendered inside the Teams interface with the Teams navigation visible around it]
In addition to embedding in a channel tab, you can share a report directly in a Teams chat or channel message:
- Open the report in the Power BI Service
- Click Share in the toolbar and select Chat in Teams
- Type the name of the Teams channel or person you want to share with
- Add an optional message and click Share
- The recipient receives a message with an interactive preview card of the report. Clicking it opens the report directly
[Insert screenshot of the Chat in Teams option in the Power BI Service Share menu, alongside a Teams chat message showing the report preview card with the report thumbnail and a link to open it]
17.4 Exporting Content
17.4.1 Export Options
Interactive Power BI reports in the Service are always preferable for regular consumption because they stay current with data refreshes and allow full exploration. However, exports are necessary when: a recipient does not have a Power BI licence, an attachment is required for an email or regulatory submission, a static snapshot of a specific point in time must be archived, or a visual needs to be embedded in a presentation.
Power BI provides export options for four formats: PDF, PowerPoint, Excel, and CSV. All exports capture the report in its current filter and slicer state at the moment of export.
Export to PDF
A PDF export renders each report page as a static page in a PDF document, preserving the visual layout exactly as it appears on screen with all current filter selections applied.
To export to PDF:
- Open the report in the Power BI Service
- Click Export in the top toolbar and select PDF
- Choose whether to export the current page only or all pages
- Click Export. The PDF is generated and downloaded to your browser’s default download location
Each report page becomes one PDF page. Interactive elements such as slicers, drill-through, and tooltips are not functional in the PDF. Visuals appear exactly as they look at the moment of export.
[Insert screenshot of the Export dropdown menu in the Power BI Service toolbar with PDF highlighted, and the export options panel showing the page selection radio buttons and Export button]
Export to PowerPoint
A PowerPoint export converts each report page into a PowerPoint slide, suitable for presenting data in meetings or sending as an editable presentation file.
To export to PowerPoint:
- Click Export → PowerPoint in the Power BI Service toolbar
- Choose the export format:
- Export with current values — generates a static image of each report page as a slide. No Power BI connection is required to view the exported file. The data is frozen at the moment of export
- Export with live data — embeds the Power BI report as an interactive object within each slide. Viewing the live data version requires Microsoft Office and an active Power BI account. The embedded report can be refreshed within PowerPoint to show current data
- Click Export. A
.pptxfile is downloaded
[Insert screenshot of the PowerPoint export dialog showing the two export format options (current values vs. live data) as radio buttons with their descriptions, and the Export button]
Export Data to Excel
The Excel export option extracts the underlying data from a specific visual as a spreadsheet, allowing further analysis or manipulation in Excel. This is not a full dataset export: it exports only the data displayed in the selected visual, filtered to the current report filter and slicer state.
To export a visual’s data to Excel:
- Hover over the visual in the Power BI Service and click the More options menu (three dots) in the visual header
- Select Export data
- Choose the data format:
- Summarized data — exports the aggregated values shown in the visual (what is visible on screen)
- Underlying data — exports the row-level data feeding the visual before aggregation, if the report builder has enabled this option
- Click Export. An
.xlsxfile is downloaded
[Insert screenshot of the More options menu on a visual in the Power BI Service showing the Export data option, alongside the export format dialog showing the Summarized data and Underlying data options with radio buttons and the Export button]
Export to CSV
The CSV export works in the same way as the Excel export but produces a plain .csv file rather than a formatted .xlsx spreadsheet. CSV is the preferred format when the exported data will be imported into another system, database, or analytical tool rather than read directly by a human.
To export to CSV:
- Click the More options menu on the visual
- Select Export data
- In the export dialog, select CSV as the file format (available as an option alongside Excel in the file format dropdown)
- Click Export
[Insert screenshot of the Export data dialog with the File format dropdown open showing both Excel and CSV as options, with CSV selected]
All export formats capture the report in its current filtered state. The table below summarizes what each format preserves and what it loses.
| Feature | PowerPoint (Static) | PowerPoint (Live) | Excel / CSV | |
|---|---|---|---|---|
| Visual layout | Yes | Yes | Yes | No (data only) |
| Current filter state | Yes | Yes | Yes | Yes |
| Interactivity | No | No | Yes (requires Power BI) | No |
| Data freshness | Frozen at export | Frozen at export | Live on refresh | Frozen at export |
| Suitable for printing | Yes | Yes | No | No |
| Suitable for further analysis | No | No | No | Yes |
Before clicking Export, ensure all slicers and filters on the report page are set to the state you want captured in the output. The export engine captures exactly what is visible on screen at the moment of export, including any slicer selections, active page-level filters, and visual-level filters. A common mistake is exporting without realizing a slicer is still set from a previous exploration session, producing an export that shows only a subset of the intended data.
17.5 Publishing Best Practices
17.5.1 Publishing Best Practices
Before publishing a report and sharing it with others, work through the following checklist to ensure the report is ready for a wider audience.
- All data source credentials are saved in the dataset Settings and a scheduled refresh is configured
- The report is published to the correct workspace with the appropriate audience access
- Row-Level Security roles are defined and users are assigned if the report contains data that should be restricted by user
- All visuals have meaningful titles and tooltips configured
- The report has been tested in Reading view in the Power BI Service (not just in Desktop)
- Slicers are reset to their default state before sharing so new viewers open the report in the intended starting view
- If embedding in Teams or SharePoint, the embed has been tested by a user who is not the report owner
- If exporting, the export was reviewed for correct filter state and data completeness before distribution
Every published report is a representation of your data and your organization. A report with incorrect numbers, stale data, or misconfigured access is more damaging than no report at all, because it erodes trust in data-driven decision-making. Treat publishing as a deliberate act: validate the data, confirm the audience, test the access, and communicate to recipients what the report shows, how often it refreshes, and who to contact with questions.
Summary
| Concept | Description |
|---|---|
| Distribute Content | |
| Publish to Service | One-click PBIX publish from Desktop to the Service |
| Workspaces | Choose where the content lives and who collaborates on it |
| Apps and Audiences | Audience-based variants of the same app |
| Direct Sharing | Sharing reports with named users or security groups |
| Engagement and Governance | |
| External Sharing | Sharing with guests in other tenants under tenant settings |
| Subscriptions | Scheduled email digests with snapshots of report pages |
| Email Alerts | Threshold-based alerts on KPI cards |
| Sharing Best Practices | Right-size workspace roles and avoid public links |