Upgrading to Azure Map component breaks PDF Export

Example of a exported pdf page:

Example in power bi app after waiting a few seconds:

Hi RSousa​,

Your reading of the problem is plausible: a PDF export captures each page after a fixed amount of render time, and a map that is slower to draw than the old one can miss that window, especially in a 90-page report where nothing stays cached between pages. I have not reproduced this myself and I am not aware of a setting that lengthens the export wait, so what follows are workarounds to reduce the render time or to avoid relying on it, from lowest to highest effort.

1. Make each map page cheaper to render

Fewer points      -> aggregate before plotting (by city, region, grid) instead of one bubble per row
Fewer visuals     -> move other heavy visuals off the map page so the page finishes sooner
Simpler layers    -> turn off extra reference or terrain layers on the pages you export
Tooltips/animation-> remove page tooltips or other features that trigger extra queries on load
Data size         -> check the query behind the map in Performance Analyzer and fix the slowest part first

2. Export smaller pieces instead of 90 pages at once

If the export gives up on a page after a few seconds, exporting the map pages by themselves, or in small groups, keeps the load per request lower. With the export-to-file REST API you can request just the pages you need and run them separately:

POST https://api.powerbi.com/v1.0/myorg/groups/{workspaceId}/reports/{reportId}/ExportTo
{
  "format": "PDF",
  "powerBIReportConfiguration": {
    "pages": [
      { "pageName": "ReportSectionMap1" },
      { "pageName": "ReportSectionMap2" }
    ]
  }
}

The resulting PDFs can then be merged in order. This also lets you retry only the pages that came back wrong.

3. Compare the exports

Export from the service UI vs. the REST API vs. Desktop -> do they all drop data, or only one path?
Warm the cache first -> open the report and wait for the maps to finish before triggering the export
Same report, fewer pages -> does the problem disappear below some page count? That points at timing/load

4. If the output must be print-quality

For documents that have to be correct every time, a paginated report is the format built for PDF output, although map visuals there are a different, more limited feature, so check whether a static map or a table covers the requirement.

Since the notification asks you to move to the new component, it is also worth opening a support case with a small repro (page with the map, export result, time to render) and mention that the old component rendered correctly in export. That feedback is what gets timing issues prioritized.

So my overall approach would be:

Reduce  -> aggregate map data and lighten the pages that contain the map
Split   -> export map pages separately via the API and merge the PDFs
Verify  -> compare UI, API and Desktop exports to see where the data is lost
Escalate-> support case with a minimal repro and the old-vs-new comparison

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.