How to Customize Power BI Subscription Emails

Imagine your operations manager working through her inbox before the weekly meeting. There is a Power BI email among the replies and reminders. She recognises the report, but nothing in the message explains whether she needs to read it now or simply keep it for reference.

A few minutes later, she asks you which section the team will be discussing. You reply that it is the backlog and service-level figures. The report arrived on time; the explanation that would have helped her use it arrived separately.

That is a good reason to customise the email. A subject such as “Weekly operations — review before Monday’s meeting” gives it a place in her day. A short message asking her to review those two sections helps her prepare without another conversation.

PBRS lets you keep that message with the job that prepares and emails the report. You can format the body, include an approved link or company image, and maintain the attachment and sending account alongside it. Next week’s email can carry the same useful guidance without you composing it again.

If your manager only needs a clearer subject and a few lines of explanation, try the native Power BI subscription first. Its More options controls let you add a subject and message, choose the report-page preview and include a report link. That may be all this Monday email needs.

Suppose the reporting team also wants a consistent company heading, a link to the meeting notes and a PDF with a familiar filename. PBRS brings the accompanying message and file delivery into the same scheduled job. You can maintain the email without asking someone to forward the report with an explanation each week.

Before adding a logo, decide where you want it to appear. A logo inside the Power BI preview belongs in the report design. A logo above your instructions belongs in the email body. Changing one does not change the other, and a native subscription message is not a general HTML-template editor.

Start with the Operations Summary and a test mailbox. Before working on colours or images, write the message you would send your manager yourself:

Your weekly Operations Summary is attached. Please review the backlog and service-level sections before Monday’s meeting, and bring any questions you would like the team to discuss. You’ll find the reporting period at the top of the report.

Those words fit our example because they explain what has arrived, why it matters and what to do next. Adapt them to your own meeting and report. If the email contains a link rather than an attachment, say that instead.

If the native subscription is enough

Open the subscription, expand More options and enter the subject and message. Choose the preview page that will help the manager recognise the report, and include the report link if she needs to explore the figures. Save the subscription and use a controlled Run now test. That sends the subscription; it does not refresh the model.

If you are preparing the message in PBRS

Open the schedule’s Email destination and select the approved sending account. Address the first copy to your test mailbox, then add the subject and accompanying message. Choose HTML if you want formatting, or Text for a plain message.

Use the body editor to add your company heading and any useful links. Then configure the attachment’s format and filename separately. For our Monday email, the words “is attached” should lead to the Operations Summary file the manager expects to open. The PBRS Email destination guide explains the available controls.

Read the received copy together

Run the job to the test mailbox and open the message on the devices your manager uses. Can she recognise the subject on her phone, read the instructions without loading images and open the right attachment? Follow any report link using her intended access, too.

Once she is happy with the first copy, set the approved recipients and recurring delivery. Keep the subject useful next week: a fixed date will grow stale. Use a stable subject, or a supported PBRS constant whose resulting value you have checked in a test email.

If you help the reporting team with its email design, give them a small template they can understand and maintain. For the Monday Operations Summary, the useful parts are the report name, the request to review two sections and a clear indication of where to find the reporting period.

The example below is the accompanying HTML message for a PBRS Email destination. It does not change the Power BI report, and it is not code to paste into the native subscription message field.

<table role="presentation" style="width:100%;max-width:600px;border-collapse:collapse">
  <tr><td style="padding:16px;font-family:Arial,sans-serif;color:#143447">
    <p style="font-weight:bold">Operations reporting</p>
    <p>The Operations Summary is ready for review.</p>
    <p>Please check the backlog and service-level sections before the meeting.</p>
    <p>The reporting period is shown in the report.</p>
  </td></tr>
</table>

Next Monday, your manager spots the Operations Summary in her inbox. The subject tells her it is for the meeting, and the message points her to the backlog and service-level sections. She opens the report and makes her notes. Your first conversation can be about the figures, rather than where to look.

Try that improvement with one recurring email. Keep the native subscription if a clearer subject and message meet the need. When you want the formatted message, sending account and prepared file maintained together, use the same report to evaluate PBRS. The Power BI Report Automation page shows how that email fits into a wider reporting routine.

Download the PBRS Internal Evaluation Guide