Forum Discussion
Report Builder - Export failed
Hi everyone,
I’m having an issue exporting a paginated report (Report Builder) that is published in the Power BI Service (in an App). When I run the report and try to export it to PPTX or XLSX, the export fails with the following error message:
Export failed
We’re having trouble connecting to the service. Please check your network connection or VPN settings, then try again.
If the issue continues, there may be a network policy or firewall blocking required access.
However, exporting the same report to PDF or Accessible PDF works perfectly with no errors.
Has anyone experienced this?
Is there something specific about PPTX/XLSX export in the Power BI Service that could be causing this issue?
Thanks in advance!
Hey vshinto ,
This is a known type of issue with Power BI Paginated Reports where PDF works but PPTX/XLSX fails, and it’s usually not actually a “VPN problem” even though the error message suggests it.
Here’s what’s typically happening.
When you export a paginated report to PDF, the rendering is handled slightly differently than when exporting to PPTX or XLSX. Power BI Service uses additional backend services for Office-based formats (PPTX, XLSX). If something blocks those endpoints, the export fails while PDF continues to work.
The most common causes are:
First, network or firewall restrictions. PPTX and XLSX exports rely on additional Microsoft service endpoints. If your organization restricts outbound traffic using a firewall, proxy, or conditional access policy, those Office export services may be blocked. This is especially common in corporate environments with strict network rules.
Second, tenant-level settings in the Power BI Admin Portal. There are specific settings for:
- Export reports as PowerPoint presentations
- Export reports as Excel files
- Export data
If these are disabled for your security group, PDF will still work but PPTX/XLSX will fail.
Third, sensitivity labels or Microsoft Purview policies. If the dataset or report has a sensitivity label applied and your tenant enforces protection rules, Office exports may be blocked depending on policy configuration.
Fourth, large or complex reports. Excel export in particular can fail if:
- The dataset is very large
- There are too many rows per tablix
- Memory limits are exceeded during rendering
PDF rendering is sometimes more tolerant than Excel rendering.
Fifth, browser or session issues. Less common, but:
- Try InPrivate/Incognito
- Try another browser
- Clear cache
- Ensure no browser extension is interfering
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!
4 Replies
Hey vshinto ,
This is a known type of issue with Power BI Paginated Reports where PDF works but PPTX/XLSX fails, and it’s usually not actually a “VPN problem” even though the error message suggests it.
Here’s what’s typically happening.
When you export a paginated report to PDF, the rendering is handled slightly differently than when exporting to PPTX or XLSX. Power BI Service uses additional backend services for Office-based formats (PPTX, XLSX). If something blocks those endpoints, the export fails while PDF continues to work.
The most common causes are:
First, network or firewall restrictions. PPTX and XLSX exports rely on additional Microsoft service endpoints. If your organization restricts outbound traffic using a firewall, proxy, or conditional access policy, those Office export services may be blocked. This is especially common in corporate environments with strict network rules.
Second, tenant-level settings in the Power BI Admin Portal. There are specific settings for:
- Export reports as PowerPoint presentations
- Export reports as Excel files
- Export data
If these are disabled for your security group, PDF will still work but PPTX/XLSX will fail.
Third, sensitivity labels or Microsoft Purview policies. If the dataset or report has a sensitivity label applied and your tenant enforces protection rules, Office exports may be blocked depending on policy configuration.
Fourth, large or complex reports. Excel export in particular can fail if:
- The dataset is very large
- There are too many rows per tablix
- Memory limits are exceeded during rendering
PDF rendering is sometimes more tolerant than Excel rendering.
Fifth, browser or session issues. Less common, but:
- Try InPrivate/Incognito
- Try another browser
- Clear cache
- Ensure no browser extension is interfering
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!
Hi vshinto
I ran into the same behavior recently and it turned out not to be an issue with the RDL itself, but with how the export endpoints are being reached from the browser/network layer in the Service.
A few things to check/try that usually fix it:
Browser-specific issue:
- If you’re using Chrome, try the same export in Edge or another browser and see if PPTX/XLSX works there.
- If it works in Edge but not in Chrome, this is likely related to Chrome’s new “Local network access check” change. In Chrome, go to: chrome://flags/#local-network-access-check and temporarily disable that flag, then restart the browser and test the export again.
Network / VPN / firewall policies
- The PPTX/XLSX export uses a slightly different path than PDF in the Service, so it can be blocked even when PDF works.
- Try exporting from a different network (home vs corporate, or with VPN off) to see if it succeeds.
- If it works on a different network, you’ll need your network team to allow traffic to the Power BI Service export endpoints (same domains as normal Power BI, but some policies only affect file download endpoints).
Session / timeout edge cases
-
Make sure the report session is still active when you export (avoid letting it sit idle for long before exporting), as expired sessions can also surface as connectivity-type errors.
If PPTX/XLSX exports work in another browser or another network, it confirms that the issue is environmental (browser setting or network policy) rather than a problem with the paginated report itself. Once the Chrome flag/network rule is adjusted, the export to PPTX/XLSX should succeed just like PDF.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
Hi vshinto,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to MohdZaid_ & grazitti_sapna for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
Hello vshinto,
We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
