How to Export Power BI Data to Excel with Power Automate

Picture the last working day of the month. Your sales manager asks for an Excel copy of the Power BI figures so she can add comments before the review. You set up a flow to collect the data, and the first workbook looks promising.

Then she asks for a regional summary on one tab, the sales behind those totals on another, and a second report in the same file. Finance wants consistent number formats. The finished workbook also needs a password before it leaves the team.

Those are reasonable requests. They are also the point at which a simple export can turn into a small application that someone has to maintain. Each query, worksheet mapping, formatting step and recovery rule becomes part of the monthly process.

PBRS is the better fit when the recurring deliverable is a finished reporting pack. It can export summarized or underlying data from supported Power BI visuals, combine compatible report outputs into one workbook, apply Excel formatting and protect the file before delivery. You configure the reporting job instead of building each piece of workbook production into a flow.

Power Automate remains useful for a small custom extract or a wider business workflow. The decision is how much of your time should go into maintaining the Excel handoff, once the Power BI reports already contain the information the team needs.

The first complication is easy to miss: Export To File for Power BI Reports does not produce XLSX for a standard interactive report. It produces PDF, PowerPoint or PNG. Paginated reports have a separate Excel export route; that does not turn an ordinary Power BI report into a workbook.

For a custom data extract, a common flow instead runs a DAX query against the semantic model, copies an Excel template and writes the returned records into its table. You have to express the required selection in the query; it does not automatically inherit the sales manager’s current report filters.

That approach can be perfectly workable for a modest, stable extract. As the monthly pack grows, though, someone must maintain the queries, keep the column mappings aligned with the model, and decide what happens if a run stops halfway through. A successful test with a few rows does not establish how the month-end volume will behave.

A few rows are different from a finished pack

Writing one row at a time adds an Excel action for each record. Turning on parallel writes to the same workbook is not a supported shortcut. File locks and delayed updates also complicate the moment when the flow can safely read back and send the completed file.

An Office Script can write data in batches and handle formatting, but now there is a script to develop and support as well as a flow. Combining reports and producing a password-protected workbook needs an explicit implementation too; the basic query-and-add-row sequence does not provide either outcome.

With PBRS, these are reporting settings and package options. For the sales manager’s recurring pack, that is the practical advantage: fewer workbook-building steps for your team to design and maintain. PBRS still needs a configured installation, authorised report access and a tested output, but it takes ownership of the export-and-delivery work.

Return to the workbook your sales manager asked for. Start with one closed month and a test destination, with automatic delivery disabled. That gives you a real reporting pack to review together before it becomes part of the monthly routine.

Give her both the overview and the detail

Choose the report and its titled visuals, then select MS Excel – Data Only (*.xlsx). Use summarized data for the regional overview and underlying data where the team needs supporting records. Underlying export depends on the visual, model, permissions and Power BI export rules; it does not mean unrestricted access to every model row.

Name the worksheets so the team can find its way around. PBRS can place visual data into separate tabs or into an existing Excel template. The PBRS Excel output guide shows the selection and format controls.

Bring the reports together and make them readable

If the sales pack draws on several reports, add them to a PBRS package and use Excel merging to combine their compatible outputs into one workbook. Your colleague receives one file for the meeting rather than assembling several attachments herself.

Set the required number formats, styles and totals, or use the team’s Excel template. An amount should remain a value she can sum; a discount should display as a percentage. Formatting belongs in the repeatable job, so she does not have to tidy the same columns every month.

Protect the workbook that will actually be sent

Apply password protection to the final workbook. For a merged pack, set the password at the merge stage so it protects the combined file, rather than only the individual inputs. The Power BI package guide explains the merge and password options.

Choose the recipient or folder and a filename that makes the reporting month clear. Run the job once, then open the delivered workbook with your colleague. Check every tab, reconcile its totals, test the password and confirm that the underlying records are the ones she expects.

Once she is happy with that result, enable the schedule after the source data is ready. Confirm that the date selection moves to the next reporting period. If completion time varies, an application can request the PBRS job after the month is closed, as described below.

Your application may already know when the sales month is closed. It can request a saved PBRS job at that point, while PBRS handles the workbook preparation and delivery. The reporting team can maintain the Excel settings without making the application responsible for writing rows and styling cells.

Use the PBRS Excel API guide for visual selections, summary or underlying data and template settings. For a pack containing several reports, use the report package API guide to configure the members and merging.

POST {pbrsBaseUrl}/api/Schedule/ExecuteScheduleAsync
Authorization: bearer {pbrsAccessToken}
Content-Type: application/json

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Monthly sales workbook"
}

GET {pbrsBaseUrl}/api/Schedule/GetExecutionStatus?ExecutionId={ExecutionId}
Authorization: bearer {pbrsAccessToken}

At the next review, your sales manager opens one workbook, checks the regional summary and moves to the supporting sales when a question comes up. The tabs are ready, the figures are readable and nobody has spent the morning merging files.

Keep Power Automate when a small custom extract or a broader workflow justifies maintaining the flow. Choose PBRS when the recurring job is to produce, combine, format, protect and deliver Power BI workbooks. Those requirements are central to the reporting process, and PBRS brings them together.

Start with the pack your team already uses. The PBRS Excel scheduling guide shows how to automate its delivery as part of your wider Power BI Report Automation routine.

Use the evaluation guide to plan a trial around that workbook and the people waiting for it.

Download the PBRS Internal Evaluation Guide