How to Export Power BI Reports to PowerPoint

Every Monday, a sales manager reviews the completed week with the team. The same three report pages usually set up the discussion: an overview, regional sales and outstanding orders. Before the meeting, someone opens Power BI, chooses the right period, exports the pages and emails the presentation.

None of those steps is especially difficult. The problem is having to repeat them when everyone is busy—and discovering, just before the meeting, that the attachment is last week's copy.

With PBRS, you can save the report selection, supported filters, PowerPoint format and destination as a reporting schedule. The deck becomes a repeatable output rather than a small task that depends on someone remembering it. A dated filename also helps the manager recognize the correct version when it arrives.

For this meeting, a fixed snapshot is useful. Everyone discusses the same figures, and the presentation can be kept alongside the meeting notes. The manager can add commentary and action slides in PowerPoint, with time to think about the story behind the results.

If the discussion instead needs live filtering and drill-down, Power BI's PowerPoint add-in serves a different purpose. Choose the presentation experience first; then decide how to prepare and deliver it.

A fixed deck for a repeatable review

You can export Power BI reports to PowerPoint directly from the Power BI service. For an occasional presentation, choose Export → PowerPoint → Export as image. Each report page becomes a slide image. The figures stay fixed, and you can add commentary around them in PowerPoint.

That export does not turn the visuals into editable PowerPoint charts. If you need to change a chart's data or design, make the change in the source report and export again, or build a separate presentation chart. Microsoft's PowerPoint export guide explains the native options.

PBRS for the deck you need every week

PBRS is a better fit when the export is a recurring responsibility. It brings the report selection, output settings, timing and delivery together, so the sales manager receives the prepared file without someone repeating the export-and-email routine.

The PowerPoint output settings let you select all pages or a smaller set. For our weekly review, that means sending the pages that support the meeting instead of making the manager remove irrelevant slides every time.

Give the file a recognizable name and use date/time values to distinguish runs. PBRS also lets you set file-summary properties, which helps identify the document when it is stored or shared. These are small details, but they make a recurring deck easier to find and use.

If the slides contain confidential figures, PBRS can compress the output into an encrypted, password-protected ZIP. The recipient uses the ZIP password to extract the presentation, so this protects the packaged delivery. Check that the recipient can open the protected delivery using your organization's approved tools.

Deferred delivery lets PBRS generate the report at the scheduled time and send it later. That can be useful when you want a fixed snapshot prepared in advance but released at an agreed time. Remember that waiting to send the file does not refresh the figures inside it.

These choices are documented in the PBRS PowerPoint output guide. Together, they turn a recurring export into a prepared delivery the presenter can recognize and rely on.

Live content for a meeting that needs exploration

When someone asks “What happens if we look only at the western region?”, a static slide cannot answer by changing its filters. The Power BI add-in can bring live report pages or individual visuals into PowerPoint for that kind of discussion.

Live content still depends on report access, applicable Power BI licensing and a supported Office setup. Test it with the presenter's account and meeting equipment. A static exported deck is often more appropriate when you need a fixed record or a presentation that can be opened without a live report connection.

Start with one weekly sales deck and one test recipient. The aim is a presentation the manager would be comfortable opening at the next meeting. You do not need application code to set up a recurring PBRS schedule.

Choose the pages and reporting period

Select the supported report and configure the filters or parameters appropriate to that source. For the sales review, confirm that the overview, regional sales and outstanding orders all refer to the completed week.

An unattended schedule does not inherit the selections in the manager's open browser. Run a test and compare a familiar total with the source report. That is a more useful check than simply confirming that a file was created.

Prepare the PowerPoint output and delivery

In the destination setup, select PowerPoint (*.pptx) and choose the required pages. Configure the filename and delivery destination, then add date/time naming if you want to retain individual runs rather than replace an existing file.

If you use ZIP protection or deferred delivery, include those in the test. Open the actual attachment or saved file the manager will receive, not just an intermediate copy on the reporting server.

Leave room for the data and the presenter

Schedule the export after the reporting data is ready, with enough time for generation, delivery and the manager's preparation. A scheduled start time is not a promise that the attachment will arrive at that exact moment.

If the weekly data is sometimes late, coordinate reporting with confirmed data readiness rather than assuming that a fixed delay is always enough. The next chapter shows how an application can request the prepared job when it knows the figures are available.

Read the deck as your audience will

Open the delivered PPTX in slideshow mode. Check chart labels, legends and the reporting period at presentation size. A dense report page may need a simpler source layout before it makes a useful slide.

Pay particular attention to tables that scroll in Power BI. An image of the visible report page is not an assurance that every row has been exported. If the meeting needs detailed records, give the team an appropriate supporting report or data export rather than squeezing all the detail onto a slide.

Once the manager is happy with the sample, enable the routine and agree who will investigate a missed delivery. The presenter still owns the commentary and decisions; PBRS removes the repeated work of preparing and sending the report output.

Suppose the sales application finishes its weekly processing at a different time each Monday. Once the reporting data is ready, its backend can ask PBRS to run the saved PowerPoint job. The presenter receives the same agreed deck, while the application supplies the timing.

Keep the page selection, filename, output and destination in PBRS. The application starts and monitors that prepared job; it does not need to rebuild those reporting instructions for every request.

POST {pbrsBaseUrl}/api/Schedule/ExecuteScheduleAsync
Authorization: bearer {pbrsAccessToken}
Content-Type: application/json

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Weekly sales meeting deck"
}

GET {pbrsBaseUrl}/api/Schedule/GetExecutionStatus?ExecutionId={ExecutionId}
Authorization: bearer {pbrsAccessToken}

Show progress that means something to the presenter

“Preparing the weekly deck” is a useful message while PBRS runs. Only tell the manager the file is ready after you have confirmed the execution result and intended delivery. Retain the execution reference if support needs to investigate a missing attachment.

If the same job also has a recurring schedule, coordinate that schedule with the application trigger. Otherwise, a late data load could lead to two runs and two different copies arriving for the same meeting.

Next Monday, the manager should be able to open the right deck and spend the remaining time preparing the discussion. The report pages, filename and delivery should follow the routine you have already agreed.

Use a manual export for an occasional snapshot or the live add-in when the meeting needs interactive exploration. Choose PBRS when the same presentation output needs to be prepared and delivered reliably, week after week, with the appropriate naming and protection.

Explore automated Power BI report sharing with PBRS to plan the delivery, or see Power BI Report Automation for the wider workflow. Use the evaluation guide below to test your own weekly deck, recipient and preparation deadline.

Download the PBRS Internal Evaluation Guide