Power BI export flows need the right connector action
Reviewed by Helen Jones
Microsoft’s current Power BI connector reference lists separate Power Automate actions for exporting regular Power BI reports and paginated reports. Regular reports can export to PowerPoint, PDF or PNG, while paginated reports support a wider set of outputs including Excel, Word, CSV and accessible PDF. The connector uses a non-shareable connection, so a person who uses a shared flow can be prompted to create a connection of their own. The reference does not announce a retirement or a remapping deadline for an older Power BI export action.
A recurring report-pack flow can look like one job—refresh, export and send—but the export step has different capabilities depending on the report type. Choosing a paginated-report action for a standard report, or expecting an unsupported file type, can turn into a brittle monthly process before anyone checks the action configuration. The important correction is that this is an action-and-format check, not a documented retirement alert. The connector reference is useful for validating an existing flow, but it is not fresh enough to justify a time-sensitive Pulse claim about a change or deadline. Treat the draft as held until a current official retirement announcement is available.
Analysis
Open one production report-pack flow and confirm its export action matches the report type and required file format. Then run a controlled export using the flow owner’s connection before the next scheduled send.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Power BI export flows need the right connector action", Collab365 Spaces. 1 source referenced.