How to Export Power BI Data to Excel with Power Automate

A monthly extract should have a clear agreement: which rows belong in it, how values should be stored and what proves that nothing is missing. Here we use five columns—SaleId, Region, ReportMonth, Amount and DiscountRate—for September 2026.

The Power BI connector reference lists these separately. A model query does not inherit an open report’s slicers or transfer its page layout into Excel. Put the reporting scope into the query.

This workflow creates a new file in OneDrive for Business for each run and adds rows sequentially. An approved SharePoint document library can host the same Excel Online Business workflow. For a standard-report PDF instead, follow Microsoft’s report export integration guide and its capacity requirements.

Check the flow’s Power BI connection, not just your personal access. It needs Read and Build permissions, and the tenant’s Dataset Execute Queries REST API setting must be enabled. The query API requirements exclude models hosted in Azure Analysis Services or live-connected to on-premises Azure Analysis Services. Use the account’s authorized data scope, including applicable row-level security. Establish expected counts and totals from an approved baseline.

Prepare a valid XLSX in OneDrive for Business or SharePoint with an empty named table, ExportRows, and the five headers above. Format SaleId and ReportMonth as text, Amount as numeric and DiscountRate as a percentage. Keep the template unchanged; the flow will write a new copy.

Use the Synthetic Sales Template, Synthetic Sales Expected Output and Synthetic Query Response to inspect the mapping. The template has an empty ExportRows table; the expected workbook has four records. These synthetic files contain no customer data. Their local values and saved workbook were checked; no cloud flow was executed.

Execute Queries accepts one query and one result table per call, with at most 100,000 rows or 1,000,000 values, whichever comes first, and 15 MB of returned data. Limited data and an error can accompany HTTP 200. The Excel Online Business connector has a 25 MB workbook limit and 5 MB request limit. Confirm destination write access and use one writer; concurrent modifications are unsupported. These ceilings do not promise efficient large row-by-row exports.

Conceptual Power Automate flow — the native route remains the tutorial’s focus.

Illustrative DAX: replace Sales and its columns with your model schema.
EVALUATE
SELECTCOLUMNS(
  FILTER(Sales, Sales[ReportMonth] = "2026-09"),
  "SaleId", Sales[SaleId],
  "Region", Sales[Region],
  "ReportMonth", Sales[ReportMonth],
  "Amount", Sales[Amount],
  "DiscountRate", Sales[DiscountRate]
)
ORDER BY [SaleId]

SELECTCOLUMNS aliases return with brackets. Map the five Excel columns from [SaleId], [Region], [ReportMonth], [Amount] and [DiscountRate]. For Amount, an expression within Apply to each can read item()?['[Amount]']. Preserve the brackets in the property name.

Pass Amount and DiscountRate as numbers. With percentage formatting, 0.0123 displays as 1.23%. Test how the flow maps a source null to a blank cell, keeping it distinct from zero. Inspect the saved identifier too: 0001 must remain text rather than becoming 1.

The synthetic response has IDs 0001–0004, two North records and two South records, all for 2026-09. Amounts 1,200, 800, 900 and 600 total 3,500, with no currency assigned. The expected workbook stores text IDs and numeric amounts; one discount is zero and one is blank from a source null. Those checks establish the local fixture mapping, table and file. A controlled cloud run must still verify authentication, DAX execution, connector timing and delivery. Retain its run history and output.

Excel writes may take up to 30 seconds to appear, and file locks can last up to six minutes. Retries can insert duplicates. Check both missing and duplicate rows. List rows present in a table returns up to 256 rows by default; enable pagination when the expected table is larger.

After resolving a failure, deliberately rerun this append-only example into a fresh file. Appending the entire response to an uncertain partial workbook can duplicate records. Reconcile that output and stop delivery whenever validation fails.

When the workbook can come from PBRS

If your recurring requirement is a workbook from selected report visuals, compare this flow with a PBRS Excel job. Configure the required visuals, export type and template placement once, then let the application call that saved schedule. The PBRS Excel API guide covers the workbook settings.

For the September sales handoff, retain the same checks for IDs 0001–0004, zero versus blank discounts and the 3,500 Amount total. First establish that the selected visual actually supplies those records. PBRS visual export is a different source from the flow’s DAX query; it does not automatically execute that query or remove its limits.

The backend uses POST /api/Schedule/ExecuteScheduleAsync for the approved job and follows its returned ExecutionId through GetExecutionStatus. Check the execution result and received XLSX using the PBRS execution workflow. This is useful when you want PBRS to own the repeated workbook generation and delivery, while the application keeps control of access and the reporting period.

For the synthetic example, a passing cloud output has four unique text IDs, four data rows, September 2026 and an Amount total of 3,500. Check the zero discount, blank discount and percentage display in the retrieved XLSX, as well as the flow’s action results.

Then enable recurrence and retain the query, template version, output identifier and validation record. When the model schema changes, review the mappings. When the period changes, update both the query scope and expected controls.

For recurring data from selected visuals, consider PBRS report automation and the separate Excel automation workflow. Return to Power BI Questions for other export tasks.

Considering PBRS as an alternative for recurring Excel delivery? Share the guide with your colleagues to review deployment, licensing, security and your reporting requirements.

Download the PBRS Internal Evaluation Guide