How to Export Power BI Reports to PDF Automatically

Imagine an operations manager preparing for the morning meeting. She needs yesterday’s service figures and a list of unresolved exceptions. The full report contains other pages, but those two give her enough to decide where the team should focus.

A recurring PDF works well here because everyone can open the same dated document, including colleagues who are away from their desks. In PBRS, you can select the Summary and Exceptions pages and send them together, with a recognizable file name, each weekday.

The timing needs to follow the data. If the overnight load normally finishes at 7:45, allow time for the Power BI model to refresh and for the PDF to be generated before the 8:30 meeting. A schedule set to 8:30 starts work at that time; it does not promise an attachment in the inbox at that exact moment.

Put the reporting date on the report itself. That simple detail helps the manager distinguish yesterday’s completed figures from an older copy, without having to ask the reporting team.

Power BI’s built-in subscription is a useful starting point if you need an email attachment and the report qualifies. Open the report, choose Subscribe and look for the full-report attachment option. The subscription documentation explains licensing, recipient restrictions and attachment limits, including the 20-page and 25 MB limits for standard full-report attachments.

If the file also needs to go into a folder, or you want its selected pages, name and delivery managed together, PBRS gives you a dedicated reporting schedule. Power Automate is another option when your team already maintains flows and the report meets Microsoft’s export requirements.

Check eligibility before building a flow. Microsoft’s scheduled export example uses a reserved-capacity workspace. Adding the Power Automate connector does not remove that requirement. PBRS uses its own supported rendering options; try the actual report in your environment when comparing the approaches.

For the operations manager, the goal is a two-page PDF in her inbox before the meeting. Here is how to turn that request into a recurring PBRS job.

1. Choose the report. Create a Single Report Schedule, select the Power BI account, workspace and operations report, and give the schedule a name such as “Weekday operations pack.”
2. Select the pages. In Settings, use Pages To Render for Summary and Exceptions. Set any required filters and use Preview to see the result.
3. Choose PDF and delivery. Add an Email or Disk destination and select Acrobat Format (*.pdf). Give the attachment a name the team will recognize.
4. Set the timing. Choose Daily or Week Days and leave enough time after the data becomes ready. Check the time zone so the run follows the team’s working day.
5. Try the complete delivery. Run the job to a test recipient or folder before enabling recurrence. Open that copy and check its pages, reporting date and figures.

The Single Report Schedule guide walks through the controls. The PDF output guide covers the format settings.

Choose the file naming rule to suit the team. A dated copy helps someone look back at an earlier meeting. A “latest” copy can suit a shared folder where colleagues always want the current report. Remember that the date a file was generated can differ from the period its figures describe.

Sometimes the overnight load finishes at different times. In that case, your application can tell PBRS to run the operations pack when the load is ready, instead of relying only on a clock. The saved PBRS job still contains the page selection, PDF format and destination, so those reporting choices do not have to be rebuilt in application code.

Prepare and test the schedule first. Then use the following request pattern to execute that existing job. Replace the example ID and placeholders with your installation’s values.

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

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Morning operations pack"
}

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

Save the returned ExecutionId alongside the reporting date, then monitor the execution and inspect its result using the PBRS execution guide. If a request times out, check the existing execution before starting another; the first run may still be producing or delivering the PDF.

Choose whether PBRS recurrence or the application starts this particular job. Using both without coordinating them can send two copies. The schedule API guide and destination guide explain how to maintain the saved configuration.

For comparison, a direct Microsoft export integration submits an export, monitors it, retrieves the file and handles delivery separately. PBRS is useful when the application should supply the trigger while the reporting job remains manageable in PBRS.

Once the schedule is working, the operations manager can open the morning pack and get on with the meeting. The reporting team has a saved job to maintain, instead of a daily export-and-email task.

Start with one real report and its intended readers. If a native subscription covers the requirement, it may be all you need. If you want to manage selected pages, PDF settings, naming and delivery together, explore scheduled PDF delivery with PBRS. The Power BI Report Automation guide shows how that can grow into a wider reporting routine.

Download the PBRS Internal Evaluation Guide