Power BI Report Server Email Delivery for PBIX and Paginated Reports

It is nearly time for the morning operations meeting. The team needs yesterday’s production figures, finance wants the latest invoice pack, and someone has asked for another copy of the report you sent last week. All the information is already in Power BI Report Server. You are simply the person who has to turn it into something everyone can use.

PBRS gives that last part of the job a home. Connect it to your existing Report Server, choose the reports, decide how the files should look and tell it where and when to deliver them. Your operations PDF can arrive before the meeting, while finance receives its own scheduled output.

Why one report has a subscription option and another does not

A PBIRS portal can contain both Power BI reports saved as PBIX files and paginated reports saved as RDL files. They live together, but their native delivery features differ.

Microsoft supports native email subscriptions for paginated reports on Report Server. It does not provide the equivalent native email subscription for PBIX reports hosted there. If you cannot find that option on your operations report, changing SMTP settings will not create it. Microsoft’s Report Server and Service comparison explains this distinction.

PBRS supports both reporting needs. It adds scheduled exports and delivery for PBIX reports, and it can also take responsibility for paginated reports when you want richer packaging, distribution or automation. You do not have to leave finance on a separate process simply because its report already has a native subscription.

Keep the reports on your server

You can use PBRS with reports hosted in PBIRS without moving them to Power BI Service just to automate delivery. That is useful when your reporting environment needs to remain on premises. PBRS still needs an authorized connection to the server, and your existing Microsoft licensing and report permissions still apply.

PBRS works with published reports in Power BI Service, PBIRS and SSRS; it does not schedule exports directly from Power BI Desktop. Publishing gives the automation a managed report location that can be maintained independently of someone’s laptop.

The operations manager wants a quick view of production. Finance needs a document it can retain. An analyst wants something to work with in Excel. Sending everyone the same attachment may be convenient for the sender, but it rarely serves all three well.

Choose the output for the task

For on-premises PBIX reports, PBRS documents PDF, Excel, Word, PowerPoint, HTML, EPUB and image outputs. For paginated reports on premises, options include PDF, Excel, CSV, Word and other supported formats. The PBRS output-format guide separates these sources so you can select the right route.

Use a PDF when the operations team needs a finished report to read. Choose a paginated report when the requirement is a carefully laid-out invoice, a long detailed list or a structured spreadsheet export. Check an actual sample before promising that a visual report exported to Excel will behave like a table of underlying data.

For the operations PDF, PBRS lets you adjust rendering dimensions, margins, cropping and page selection. That matters when a report looks comfortable in a browser but cramped in an attachment. A few minutes spent on the first export can save everyone from zooming and scrolling through the same awkward file every morning.

Send a complete pack instead of a string of emails

Once the daily report is working, the weekly management pack is a natural next step. Put the production overview, quality report and exceptions report into a PBRS package. Recipients can receive separate attachments, a ZIP archive, a combined PDF or supported Excel outputs assembled into one workbook.

PBRS’s on-premises package workflow supports delivering the reports together. Each report can have its own settings, so the pack reflects what the meeting needs rather than what happens to be on a single report page.

Let one run serve more than one destination

The same reporting routine can email the team and retain a dated copy in a shared folder. PBRS also offers destinations such as FTP, SFTP and SharePoint through its supported destination configuration. You can choose the format and naming for each destination instead of asking someone to copy files around afterwards.

Where the selected PDF output supports them, PBRS adds built-in encryption, an opening password, a permissions password, printing and copying controls, watermarks and document properties. These are part of preparing a useful deliverable, without a separate PDF-editing script. Match the protection to the audience and test it in the viewer they use.

Start with the operations report you already send each morning. Keep the first delivery familiar: the same audience, the same reporting period and a PDF they recognize. Once that works, add the improvements people have been asking for.

Connect PBRS to the published report

In the PBRS desktop application, choose Single → PowerBI on Premise → Dashboards & Reports. Select the configured reporting-server account and browse to the PBIX report. Give the schedule a useful name, such as “Operations — weekday morning PDF.”

Use the appropriate paginated/SSRS scheduling route for an RDL report. The shared portal location does not make the two report types interchangeable. Verify that the account PBRS uses can open the report and access its data without an interactive sign-in prompt.

Fit the schedule around the data and the meeting

If the meeting starts at 8:30, aim for an earlier delivery that leaves time to respond to a problem. PBRS supports daily, weekly, monthly and other scheduling patterns. A weekday report and a month-end finance pack can follow different calendars.

Do not assume that reaching the scheduled time means yesterday’s data has finished loading. Coordinate the run with the upstream process, or use an appropriate PBRS event or automation condition. The report should show the period the recipients expect, not merely the latest data available when the clock reaches eight.

Make the first PDF worth opening

Select the pages the team needs, apply the relevant report filters and review the rendered file. In the documented on-premises page-selection setting, use actual page titles separated by a pipe, such as Operations|Exceptions. Leaving that setting blank selects the current page; it should not be treated as “export every page.”

Add an email destination with a clear subject and filename. Include the reporting date so someone returning to the message next week can identify the right copy. If you also add a portal link, remember that opening the link still requires report access.

Use a test destination first. Open the received attachment, check both pages, compare the reporting period with the source and confirm that the intended filters took effect. The PBIRS single-schedule guide walks through the application settings.

Personalize when the audience grows

When several sites need their own figures, data-driven scheduling can replace a growing collection of near-identical jobs. A driver supplies values for the recipient, report selection or filters, filenames and other supported settings. Data-driven packages can assemble the reports each person needs before delivering their pack.

For example, each plant manager could receive the local production and quality reports, while head office receives the wider overview. Test the mappings with two deliberately different sites before expanding the audience. A filtered file is a separate copy of your data, so getting the recipient-to-content relationship right matters.

The first successful email is a good start. The real benefit arrives when the process keeps working next week, and someone else can understand it when you are away.

Decide what should happen when the report is late or empty

PBRS provides exception handling, retries and actions for failed or blank exports. Set these deliberately. A production report with no rows could mean there was no activity, or it could mean the upstream load has not finished. Those situations deserve different responses.

Keep the schedule history, inspect the output and check the destination result. A report can render correctly while its email is rejected. Equally, an email can arrive with the wrong reporting period. Treat file creation, content accuracy and delivery as separate checks.

If you retain a native paginated subscription alongside PBRS, its reporting-server credentials, scheduling services and email configuration still need to work. PBRS uses its own configured delivery process; changing the Report Server mail settings is not the universal fix for every failed job.

For developers: trigger the tested PBRS schedule

You do not need code for the routine above. If an existing business application needs to request the report after a process finishes, it can call the PBRS API and reuse the schedule you have already tested.

POST /api/Schedule/ExecuteScheduleAsync
Content-Type: application/json

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Operations workflow"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=YOUR_EXECUTION_ID

The next morning, the useful question is no longer “Who has time to export these?” It is “What do these figures tell us?” That is the change the automation should make possible.

Choose the PBIRS report that interrupts your morning most often. Set up its export in PBRS, send a test copy and let the person who uses it confirm that it is ready for their day.

Then build from that success: add the archive destination, bring related reports into a package or personalize the delivery for each site. You can improve distribution while keeping the reporting investment you already have.

Explore Power BI Report Automation with PBRS and automated report packages, or use the evaluation guide to plan your first PBIRS delivery.

Download the PBRS Internal Evaluation Guide