The Power BI Export to File API has a few hard edges: PDF, PPTX and PNG for Power BI reports, CSV only for paginated reports, a community-reported PPU export limit, and exactly one output file per call. Permission scopes and tenant settings are the usual cause of surprise failures. If your automation needs volume, bursting or fast turnaround, plan for these limits up front.
TL;DR:
- Regular Power BI reports export to PDF, PPTX, or PNG, while CSV is generally limited to paginated reports; test formats individually because PNG can fail.
- PPU supports occasional paginated exports, but reported per user limits make it unsuitable for bulk jobs; use dedicated or embedded capacity for frequent runs.
- A FeatureNotAvailable error usually points to disabled tenant settings or unsupported workspace capacity; verify workspace membership and API scopes before debugging request code.
- Each call creates one file; multiple report IDs produce one combined output, so loop over IDs for separate files and space batches with retries.
- When scheduled exports exceed delivery windows or require high volume and bursting, move scheduling and delivery to a server side automation tool.
Table of Contents
- Which formats does each report type support?
- What license or capacity do you need for reliable exports?
- Which permissions and tenant settings block exports?
- How does throttling show up in automated flows?
- How do you troubleshoot common export errors?
- How do you burst reports and scale around the limits?
- When should enterprise teams move past native Export to File?
- Automate Power BI exports without the API ceiling
- FAQ
- Sources
Which formats does each report type support?
Match the output format to the report type before you write any automation, because the same endpoint behaves differently for each.
- PDF, PPTX and PNG: the formats you will use most for Power BI reports.
- CSV: discussed in the developer community as available for paginated reports rather than regular Power BI report exports, as this Stack Overflow thread describes.
- Paginated reports: they follow their own format list, so test each format you promise to downstream consumers.
- PNG quirks: some developers report PNG export failing while PDF and PPTX succeed, so never assume format parity.
Exporting a rendered file through the API is also a different operation from downloading a .pbix. The API returns a snapshot of report output, not the model, so it cannot replace a PBIX download for backup or migration work. If you only need a simple PDF flow, this PDF export discussion shows common patterns.
What license or capacity do you need for reliable exports?
Paginated report exports work from a Premium Per User (PPU) workspace with a PPU license, but community guidance discusses export limits for PPU users. That is workable for an analyst pulling a monthly file. It is not workable for a job that sends dozens of reports every morning.
Use this rule of thumb:
- Ad hoc and low volume: PPU is enough when one person triggers an occasional export.
- Frequent or high volume: move to dedicated capacity or embedded capacity so export limits stop being your scheduler.
- Bulk or bursting: use a server-side automation product rather than stretching the native API past what it was built for.
Our walkthrough on Power Automate Export to File and when to go beyond it covers the licensing decision in more depth.
Which permissions and tenant settings block exports?
Before you debug code, validate the access chain. Most "mysterious" failures are permission or tenant problems.
- Confirm the identity (user or service principal) is a member of the workspace that holds the report.
- Confirm the app registration has the Power BI API permissions that Microsoft's Export to File documentation lists for report read access.
- Check the tenant admin settings for export features. A disabled setting commonly surfaces as a FeatureNotAvailable error.
- Confirm the workspace sits on a capacity that supports the export type you requested.
Pro Tip: Test with a delegated user token first. If that works and the service principal fails, the problem is permissions, not your request body.
How does throttling show up in automated flows?
Community reports describe export limits for PPU users. A flow that fires exports back to back may encounter failures or delays, rather than a clear "rate limited" message.
To catch it early:
- Log every export call with a timestamp, report ID, format and response status.
- Look for clusters of failures that start soon after a previous success.
- Add backoff and retry when the volume is small and the delay is acceptable.
- Change the architecture when retries pile up. If your queue regularly outlasts your delivery window, no retry policy fixes it, and dedicated capacity or an external scheduler is the right call.
How do you troubleshoot common export errors?
Work through these steps in order, from the cheapest check to most involved.
- Run a small test export of one page or one simple report to separate request problems from report problems.
- If you see FeatureNotAvailable, review the tenant settings that disable export or image features.
- If one format fails, try another. When PDF and PPTX succeed but PNG fails, you are likely hitting a format-specific quirk, not a global fault.
- Re-check the scopes on your app registration against Microsoft's documentation.
- Verify the workspace capacity and that the report belongs to a supported workspace type.
- Compare your call against Microsoft's sample script, Export-PowerBIReport.ps1, to rule out a malformed request.
How do you burst reports and scale around the limits?
The export action creates exactly one file per run. According to a Power Platform community thread, passing multiple IDs into one call combines the results into a single PDF. That is useful when you want one combined packet, and a trap when you wanted one file per recipient.
- To get separate files: loop over your IDs in Power Automate and call the export once per ID.
- To get one packet: pass several IDs in a single call on purpose.
- To stay inside the limits: schedule small batches, space them out, and add retry with increasing delay.
- To scale: move scheduling and delivery to a server-side tool.
For a closer look at the pattern, see our guide to Power BI report bursting. If you are estimating file sizes for a large run, a quick MB to GB conversion helps size your storage.
Pro Tip: Treat reported export limits as a design constraint. Build your batch schedule around them instead of discovering them in production.
When should enterprise teams move past native Export to File?
Native export is a good building block, and I would not tell anyone to skip it for a prototype. But once exports are scheduled, high volume and tied to an SLA, the constraints above stop being quirks and become your throughput ceiling. A dedicated automation layer centralizes scheduling, bursting, delivery targets and retries in one place. Ask honestly whether your delivery window and volume fit within the export limits. If they do not, you have your answer.
— Christian Ofori-Boateng
Automate Power BI exports without the API ceiling
When the limits above start dictating your delivery schedule, we built PBRS to take that work off your plate. It handles scheduling, bursting, formats and delivery so your team stops babysitting flows.
- Scheduled exports: run reports on a fixed or data-driven schedule.
- Bursting: generate a separate file per recipient without hand-built loops.
- Multiple formats and destinations: deliver to email, cloud storage, databases and collaboration tools.
- Automated error handling: failures are handled in the product instead of in your flow logic.
You can see how this works in our overview of automated exports without Power Automate, or compare approaches in Export to File API vs report automation. Ready to learn more? Explore PBRS on our site and see how it fits your reporting needs.
FAQ
Does the Export to File API support CSV?
CSV is generally associated with paginated reports, not regular Power BI reports. Developers discussing the REST API report that CSV export applies to paginated reports. Confirm with a small test before promising CSV to stakeholders.
Why do I get one PDF when I pass several report IDs?
The export action produces one file per run, and multiple IDs are combined into a single output. Community guidance in a Power Platform thread says separate PDFs require a loop that calls the action once per ID.
Can I export with only a PPU license?
Yes for paginated reports, with limits. Community guidance reports that export limits apply per user, which suits occasional use but not bulk automation.
What does FeatureNotAvailable mean?
It usually points to a tenant setting that disables export or image features, or to a workspace and capacity combination that does not support the request. Check admin settings and workspace type first.
Why does PNG fail when PDF works?
Some developers report format-specific behavior where PNG fails while PDF and PPTX succeed. Test each format separately and fall back to PDF or PPTX when needed.
Sources
- Power Platform Community Forum Thread Details
- PowerBI API ExportToFileInGroup, PNG format doesn't ...