Export and email a Power BI report with Power Automate

With Power Automate, you can automate exporting and distributing Power BI reports in different formats and scenarios. In this article, you create your own flow from scratch. Use the Export to File for Power BI Reports action to automatically distribute a Power BI report via email.

Screenshot of the Power BI Automate window showing create options.

Power Automate is a no-code way to interact with the Export To File API in the user interface. See Export to File for Power BI Reports to start interacting with the API directly.


To follow along, make sure you have the following prerequisites:

  • At least one workspace in your Power BI tenant backed by a reserved capacity. This capacity can be any of the A1/EM1 - A6/P3 SKUs. Read more about reserved capacities in Power BI Premium.
  • Access to the standard connectors in Power Automate which come with any Office 365 subscription.

Create a flow from scratch

In this task, you create a simple flow from scratch. The flow exports a Power BI report as a PDF, and attaches it to an email that is sent on a weekly basis.

  1. Sign in to Power Automate.

  2. Select Create > Scheduled cloud flow.

    Screenshot showing the Power BI create window and scheduled cloud flow is highlighted.

  3. In Build a scheduled flow, give your flow a name.

  4. In Run this flow, select the starting date and time for your flow and the repetition frequency.

  5. In On these days, select which days you want your flow to run, and select Create.

    Screenshot showing the build a scheduled cloud flow dialog.

  6. In Recurrence, select Edit > Show advanced options. Enter a value in At these hours and At these minutes to set a specific time for your flow to run.

    Screenshot showing the recurrence dialog.

  7. Select New Step.

  8. In Choose an operation, search for Power BI and select Export To File for Power BI Reports.

    Screenshot showing the Power Automate dialog for choosing an operation. Export to file for Power BI reports is highlighted.

  9. In Export to File for Power BI Reports, select a Workspace and Report from the dropdowns.

  10. Select the desired Export Format for your Power BI report.

    Screenshot of the export to file for Power BI reports.

  11. Optionally, indicate specific pages to export in the Pages pageName -1 field. The page name parameter is different from the display page name. To find the page name, navigate to the page in the Power BI service, and copy the last portion of the URL as shown in the example.


  12. Optionally, indicate a specific bookmark to display in the Bookmark Name field. You can find the bookmark name in the report URL after bookmarkGuid=, as shown in the example. Only report bookmarks are supported, not personal bookmarks. You can specify other parameters for the Power BI report. Find detailed descriptions of these parameters in the Export to File for Power BI Reports.


  13. Select New Step.

  14. In Choose an operation, search for Outlook and select Send an email (V2).

  15. In Send an email (V2), complete the To, Subject, and Body fields for your email.

  16. Select Show advanced options. In Attachments Name – 1, enter a name for your attachment. Add a file extension to the file name (for example, .PDF) that matches your desired Export Format.

  17. In Attachment Content, select File Content to attach your exported Power BI report.

    Screenshot showing the send an email dialog.

  18. When you're done, select Next step or Save. Power Automate creates and evaluates the flow, and lets you know if it finds errors.

  19. If there are errors, select Edit flow to fix them. Otherwise, select the Back arrow to view the flow details and run the new flow. When you run the flow, Power Automate exports a Power BI report in the specified format and sends it as an email attachment as scheduled.

Row-level security in Power Automate

Optionally, if you want to send the report based on row-level security (RLS), you need to add the following details:

Screenshot of updating Identities Username fields.

  • Identities Username - 1 = The effective username reflected by a token for applying RLS rules. For an on-premises model, username can be composed of alpha-numerical characters, or any of the following characters: '.', '-', '_', '!', '#', '^', '~', '\', and '@'. For cloud models, username can be composed of all ASCII characters. Also, username can be up to 256 characters, and can't contain spaces.

  • Identities Semantic model - 1 = You can get this value by going to the settings of the semantic model, and then copying the semantic model ID from the address bar, as shown in this example and in the following image:


    Screenshot of an example semantic model ID.

  • Identities Roles Item - 1 = RLS name defined in the report