Forum Discussion
Maps exported as PDF / PowerPoint are not displayed as expected from Power BI Service
Hi Community,
In a Power BI report with three filters applied to all pages, we discovered discrepancies between the original visual in Power BI Service and the exported version, in which:
- Fewer items are shown in the exported version.
- Some of the exported items are outside of Germany.
Original Azure Map Visualisation in Power BI App:
Export as PDF / PowerPoint
What could be the underlying reasons?
Could it be an issue with the applied filters?
Or a problem with the export function in Power BI?
Or an issue with the visual display in Azure Map / Filled Map?
Are there any settings needed to ensure that the visual is displayed correctly?
Any suggestions are welcome. Thank you!
3 Replies
The export issue with Azure Maps in Power BI is likely due to limited support for map rendering during export, delayed tile loading, zoom level differences, or incomplete filter application.
To fix this:Use Shape Map or Basic Map for reliable exports
Ensure visuals fully load before export
Set a fixed zoom and center
Use Sync Slicers or Bookmarks to apply filters consistently.
Hi fy_value ,
Thanks for sharing the issue. I tried reproducing this using sample data with filters applied at the report level (across pages) and an Azure Map visual. In the export to both PDF and PowerPoint from the Power BI Service, the visuals rendered as expected with only the filtered locations (e.g., Germany) shown correctly, and no discrepancies in zoom or markers.
Report in Service:
Exported to PDF:
However, there have been similar user reports in the past where Azure Map exports behaved inconsistently--such as markers missing or the map defaulting to a global view.
Azure Maps Not Displaying Locations Properly in Po... - Microsoft Fabric Community
Azure Maps (or Bing Maps) not showing values when ... - Microsoft Fabric Community
Also a known issue was noted in May 2025 and were marked as fixed, but edge cases may still occur depending on model complexity or filter behavior at runtime.
If you're still seeing incorrect locations or fewer data points in the exported file, try the following as a workaround:
-
Create a separate page with the same filters applied directly at the visual level, instead of relying on report-level filters.
-
Try exporting from Power BI Desktop to see if the issue is specific to the Service.
-
If possible, test the same setup using a Filled Map or Shape Map to check for more stable export behavior.
If none of these resolve it, please consider logging the issue in the Power BI Issues forum along with screenshots, so it can be investigated further or you can also raise a support ticket.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly.
Thank you.Hi fy_value ,
Just checking in to see if your query has been resolved and whether any of the responses were helpful. If so, kindly consider marking the relevant reply as the Accepted Solution to assist others who may have a similar question.
Otherwise, feel free to reach out for further assistance.
Additionally, could you please confirm whether the issue has been addressed through the support ticket with Microsoft?
If the issue is now resolved, we’d greatly appreciate it if you could share any key insights or the resolution here for the benefit of the wider community.
Should you need further assistance in the future, please feel free to create a new post in the Microsoft Fabric Community Forum. We’ll be glad to support you.
Thank you for your time and participation.
-
