How Do You Send Power BI Reports to a Distribution List?

Yes. Send the report to the distribution list’s email address, and your mail system passes it to the group’s members. Everyone receives the same report.

Picture a weekly operations PDF sent to operations-reports@example.com. When a manager joins the team, the group owner updates the mailing list. The report schedule keeps the same address. The example address is illustrative.

PBRS, ChristianSteven’s report automation software, makes that weekly routine easier to manage. It generates the report file and emails it from your configured account on the schedule you choose. You set up the report, output and delivery together, instead of exporting and emailing the PDF each week. Jump to the PBRS setup if that is the job you need to automate.

When a native Power BI subscription is enough

Use a native subscription when the group needs a report preview or link and your workspace and group are eligible. In a Premium-capacity workspace, Power BI supports distribution groups, dynamic distribution groups and mail-enabled security groups. Microsoft 365 groups and ordinary security groups are not supported group aliases.

A Premium Per User (PPU) workspace does not support subscribing group aliases. To subscribe other people, you also need a Power BI Pro or PPU licence, a Contributor, Member or Admin workspace role, and your organisation’s subscription settings enabled. Guests cannot subscribe other people.

1. Open the report, select Subscribe, and create a subscription.
2. Add the eligible group email address, choose the report view and set the frequency.
3. Choose the preview, link or eligible attachment, save the subscription and test it with the group.

External recipients need an eligible paid capacity that is not PPU. Trial capacity does not qualify. Check Microsoft’s subscription requirements before choosing this route.

When the group needs a recurring file

Use a PBRS Email destination to send the exported report to the group address. Native Power BI group-alias rules apply to native subscriptions; PBRS uses your configured mail account for delivery. The report still needs the right source-account permissions, licences and rendering setup.

Power Automate is another option if you already maintain an export-and-email flow. Microsoft’s export-and-email example uses reserved capacity for the standard Power BI report export. Emailing a file that already exists does not remove the requirements for generating it.

The group address answers who gets the email. It does not decide how Power BI generates the report, or whether every member may see its contents. Choose the delivery route around the report your team actually needs.

A changing mailing list is not a personalised report

A dynamic distribution group chooses members using mail-directory details such as department. The mailing list can change automatically, but everyone still receives the same attachment.

Personalised reporting changes the report itself. An East manager might receive East figures, while a West manager receives West figures. PBRS data-driven schedules can use each data row to supply the recipient and report instructions. Microsoft also offers dynamic subscriptions for eligible setups.

For our weekly operations example, a shared PDF is appropriate only if every member should see the same information. Native subscription previews use the subscription owner’s data context; they do not create a separate view for each group member.

Paginated reports, designed for a fixed page layout, have their own formats and parameter options. Check the settings for your actual report, rather than applying a standard-report limit to every report type.

For configuration details, see PBRS Email destination settings, Microsoft dynamic subscriptions and PBRS data-driven schedules.

You can give an authorised manager a “Send weekly operations report” action in your application. Behind that action, your server calls the PBRS API to run an approved schedule. The manager does not need to rebuild the report-and-email job.

This section is for the developer implementing that action. If you only need scheduled weekly delivery, continue to the next step.

Keep the group address in the approved schedule

In EmailDestinations, configure an Email destination with a To array such as ["operations-reports@example.com"]. That is one field example, not a complete create-or-update request. The mail directory controls group membership; PBRS controls the report instructions.

When updating a schedule, preserve its destination IDs, filters and other intended settings. Do not send only a replacement To field or assume a retrieved object is a valid write payload. Follow Create and Update Single Schedules, then retrieve the schedule to verify the saved configuration.

Execute the schedule and follow its result

Keep the access token on your server and use HTTPS with your installation’s API base URL. Authorise the caller and map the action to an approved schedule. In this illustrative request, 101 is a placeholder schedule ID:

POST /api/Schedule/ExecuteScheduleAsync
Authorization: bearer YOUR_ACCESS_TOKEN
Content-Type: application/json
Accept: application/json

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "API"
}

Keep the returned execution ID and use it to check the run:

GET /api/Schedule/GetExecutionStatus?ExecutionId=YOUR_EXECUTION_ID
Authorization: bearer YOUR_ACCESS_TOKEN
Accept: application/json

Poll with a time limit. Follow Schedule Lifecycle Reference for status and result handling. An accepted or queued request does not mean the email arrived. Inspect Status and parse the string-valued ResultJson separately, even when the status is Completed. An empty result is not success. Combine the execution result with mail trace and recipient checks when investigating delivery.

Make repeated requests predictable

Use separate approved configurations, or controlled isolation, when departments need different recipients or filters. Changing one shared schedule while other requests use it can send the wrong content to the wrong audience.

Record the application request, schedule ID, execution ID, destination and report period. If the application times out, reconcile that execution before retrying. Repeated clicks or retries can send the same report again.

If an eligible native subscription already gives your group the preview or file it needs, it may be enough. A maintained Power Automate flow can also serve an established export-and-email process.

Choose PBRS when the recurring report job needs more coordination. Bring report selection, output, timing, approved sender and exception handling into one schedule. Your group owner maintains membership; your analyst maintains the report workflow. The weekly export and email become a repeatable job.

Start with one report and a controlled group. Check the file’s data and member delivery before enabling the production schedule. If recipients need different views, choose data-driven delivery instead of sending a combined attachment.

See how PBRS can automate your report distribution. If an application will trigger the job, explore the PBRS report automation API.

For the wider options, visit Power BI Report Automation.

Requirements reviewed: 8 October 2026. Confirm the settings for your report type, workspace and installed PBRS version.

Considering PBRS for recurring delivery to a distribution list? Share the guide with your colleagues to review deployment, licensing, security and your reporting requirements.

Download the PBRS Internal Evaluation Guide