How to Schedule Power BI Excel Reports by Email

The finance analyst has a familiar Monday routine: open the customer balances workbook, sort the overdue accounts and decide who needs a call. Before she can begin, someone else has to select the right Power BI data, export it, fix the spreadsheet and write the email.

Then a second request arrives. Could the regional managers have their own figures? Could the email include the reporting date? Could the balances and overdue invoices be separate tabs in one workbook?

PBRS can bring those requests into one repeatable process. It exports the report or selected visual data, prepares the workbook, applies the appropriate protection and delivers it with a message that makes sense to its recipient. The value is the time saved on the whole job, including the small finishing touches that otherwise keep coming back.

What a native Power BI subscription can—and cannot—send

A standard Power BI report subscription does not attach an XLSX workbook. Native full-report attachments are PDF or PowerPoint, require qualifying Premium capacity or PPU, and are limited to 20 pages and less than 25 MB. Paginated subscriptions can send Excel, subject to permissions, enabled formats and delivery requirements.

So full-report exports are not entirely absent from native Power BI. The missing piece for this Monday routine is a scheduled, usable Excel workbook from standard-report data, with the preparation and email controls around it. Microsoft’s subscription documentation describes the native options.

If one existing paginated subscription already gives finance exactly what it needs, it may be enough. When you need several reports, personalized workbook layouts or a richer email, PBRS gives you those choices in the reporting workflow.

Keep the reporting source that suits your business

PBRS works with published reports in Power BI Service, Power BI Report Server and SSRS. It does not export directly from Power BI Desktop. Supported Power BI Service workflows can work with Pro or PPU without dedicated capacity; the report type and export method still determine the requirements.

Recipients can receive static files without needing a Power BI account to open them. That is particularly useful when a customer or partner needs the workbook, but does not need access to your reporting portal.

For the balances review, the analyst needs customer codes, amounts and dates in usable cells. The manager may prefer the familiar report layout. PBRS lets you choose the output for each person’s work.

Choose data-only, report-page or paginated output

MS Excel Data Only exports data from selected Power BI Service visuals. Choose summarized data for the level shown by the visual, or underlying data when the report, permissions and source support it. Underlying data is not a promise to extract every row from the entire model.

PBRS also offers an Excel output for report-page presentation, including all or selected pages. Keep this separate from data-only export: preserving the visual report and producing editable rows are different requirements. For structured, detailed reports, a paginated-to-Excel export can retain the report’s designed layout.

The PBRS Excel format guide explains these choices. Test the actual workbook so you know what the recipient will be able to read, filter and calculate.

Remove the spreadsheet tidying from Monday morning

For supported visual-data exports, PBRS can apply fonts, colors and column formats, and add row and column totals. Customer codes can remain text, balances can use the right numeric format, and dates can be readable without anyone adjusting the columns after delivery.

If finance already has a workbook it trusts, populate an Excel template. Choose the worksheet and starting position, or the next available position, rather than asking the team to adopt a new layout. Keep the template’s formulas clear of the area that receives the exported data.

Put the whole review in one email

Suppose the review needs customer balances, overdue invoices and credit adjustments. A PBRS package can run those reports together and deliver several attachments in one message. If finance would rather work in one file, merge the supported Excel outputs into a workbook with separate tabs.

The package can also include a PDF overview alongside the workbook, combine PDF outputs into one document, or deliver files in a ZIP archive. A supporting document, such as instructions for the monthly review, can be added as an additional attachment. These are built-in packaging choices, rather than separate export-and-merge scripts to maintain.

See the PBRS report-package options for ways to assemble the final delivery. Choose the arrangement that makes the recipient’s next step easiest.

Name and protect each person’s workbook

For regional deliveries, the data driver can supply worksheet names, filenames and workbook passwords. A manager can receive a clearly named regional pack with tabs that match its contents, protected with the password assigned to that recipient.

A data-driven package can also group reports by recipient before merging them. In that grouping mode, report embedding in the email body is disabled; use the attachments as the report delivery.

Apply protection to the finished merged workbook where required. Workbook-opening protection and worksheet-editing protection serve different purposes; protecting a sheet is not a substitute for protecting access to the file. PBRS also supports encrypted ZIP output when that suits the delivery.

The attachment is only half the experience. A useful email tells finance what has arrived, which period it covers and what to do next. PBRS lets you prepare that message alongside the workbook.

Make the message look like it came from your team

Use HTML or plain text. The email editor supports formatted text, links, images and lists, so you can include your branding and a short explanation. Add an extra attachment when the recipient needs instructions or another supporting file.

Where appropriate, embed supported report output in the message. Power BI report output is embedded as an image; on-premises paginated and SSRS reports also offer HTML and other embedded formats. A formatted HTML email body and an HTML-rendered report are different options. The documented HTML report-embedding route uses SMTP.

PBRS also offers an optional AI summary, with prompt and length controls, using a configured ChatGPT account and accepted usage terms. Review its suitability for the report and audience before adding it to a recurring delivery.

Use Inserts to make one message work for many people

PBRS Inserts can draw on dates, constants, database values and, in a data-driven schedule, the current driver record. Use them in supported fields to supply the greeting, reporting period, subject, filename and other delivery details.

For example, the finished message might read:

Subject: Your September customer balances

Hello Alex,

Your September workbook is attached. The Balances tab shows the customer position at month-end; Overdue invoices highlights the accounts to review first.

Please send any corrections to the finance team before Thursday’s review.

This is an illustration of the received email, not literal Insert syntax. In PBRS, choose the values from the Inserts menu, so the greeting and period change with the delivery.

The driver can also supply To, CC and BCC addresses. Recipients may come from entered addresses, the PBRS Address Book, a database or a text source. For personalized reports, each recipient needs their own correctly filtered output; putting several people in BCC does not personalize the attachment.

Send through your own email setup

PBRS supports SMTP and a dedicated Office 365 mail option with modern, token-based authentication. Its configuration also includes Exchange/MAPI and Outlook routes. For unattended scheduling, note that the documented standalone Outlook option requires the user to remain logged in with Outlook open.

You can configure multiple SMTP servers, select the appropriate one for a schedule and designate backup servers if the primary is unavailable. That lets different reporting jobs use the intended sending account. Data-driven settings can also select supported mail-server details when deliveries vary by business unit.

Work with the mail administrator to authorize the sender. Changing a From address does not grant permission to send as that mailbox, and PBRS still follows your provider’s attachment-size, authentication and sending limits. The email-server setup guide covers connection testing and failed-email retries.

Begin with the customer-balances workbook and a test mailbox. Get one useful delivery working before adding the other reports or expanding the recipient list.

1. Select the published report and export. For sortable balances from a standard Power BI Service report, choose MS Excel Data Only and the appropriate titled visual. Confirm the intended filters and data level.
2. Prepare the workbook. Set formats, totals and template placement where needed. For several reports, use a package and decide whether to keep the attachments separate or merge the Excel outputs.
3. Build the email. Add the recipients, subject and HTML or text message. Insert the changing values, select the authorized mail configuration and apply the required file protection.
4. Choose the right time. Schedule after the relevant data is ready, with the correct calendar and time zone. Use an appropriate event or workflow condition when a fixed time cannot establish readiness.
5. Open the received delivery. Check the message, every attachment, tab names, reporting period, filters, customer count and totals. Test the password and make sure the workbook supports the recipient’s actual task.

The Email destination guide covers the message settings. Once the first delivery is correct, add an archive copy or another destination such as SharePoint or SFTP where needed. One reporting routine can serve both the people reading the report and the systems retaining it.

Handle the exceptions before they become missing reports

Decide what PBRS should do when an export fails or contains no data: retry, notify the owner or suppress an empty delivery, according to the requirement. Review schedule and delivery history when something goes wrong. A successful export is not proof that the recipient received the email.

Power Automate can support a custom workflow, but this richer process needs more than an email action. Querying data, constructing workbooks, applying formatting, merging files, protecting them and recovering failed deliveries can introduce extra actions, connectors or scripts. PBRS keeps those reporting tasks in the scheduling application.

For developers: let an application request the prepared email

The scheduled delivery does not require code. If a finance application needs a “Send balances” action, it can run the tested PBRS job rather than rebuild the workbook and email itself.

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

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Finance workbook request"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=YOUR_EXECUTION_ID

Next Monday, finance should be able to open the email and begin the review. The workbook has the right rows, its tabs are easy to follow, and the message explains what has arrived. Nobody needs to chase the person who normally exports it.

Start with that one delivery, then add personalized regional workbooks or a complete monthly pack. Explore PBRS Excel scheduling and Power BI Report Automation, or use the evaluation guide to plan the workbook and email your team needs.

Download the PBRS Internal Evaluation Guide