Blog Post
Power BI September 2026 Feature Summary
Hi mattlee ,
I've been eager to get my PBI desktop updated so I could check the same, and can now confirm I'm seeing the same issue. No changes in the report, and was working perfectly fine yesterday. I'm in the UK and everything in PBI service is still working okay for Azure map visuals (thankfully), but not showing in desktop. Screenshots below for reference.
PBI desktop:
Same visuals in same report in PBI service (I even republished it just to double-check, still appears as below):
Hope there's a fix soon, just glad it's not effecting our external customers (we distribute hundreds of reports in 'app owns data' embedded scenarios).
Following this thread, Azure maps visual displays as blank after publishing power bi report with September release.
Restoring to August release.
Reported 26 days ago by community.
- BEJCC4 days ago
Helper I
broken version 2.159.883.0
restoring July 2026 update (version 2.156.951.0)
Previous monthly updates to Power BI Desktop and the Power BI service - Power BI | Microsoft Learn- BEJCC4 days ago
Helper I
Azure Maps completely blank (no basemap, no markers) after working with Desktop 2.158.1177.0. In our case the visuals were blank in the Power BI Service too, across multiple users and browsers. Tenant region: North Europe.
- In browser DevTools (Network tab), the Azure Maps SDK files returned 400 Bad Request:
https://atlas.microsoft.com/sdk/javascript/mapcontrol/3/atlas.min.css (and atlas.min.js)
- The 400 was being served "from disk cache", meaning the browser had stored the failed response and kept reusing it. Without the SDK, the visual can't render at all.
- The same URL loads fine from outside our environment.
Fix: clearing the browser cache (Ctrl+Shift+Delete > "Cached images and files") resolved it for our affected users. No changes to the report were needed.
Tip for checking: open DevTools > Network, tick "Disable cache", reload, and filter on atlas.microsoft.com. If you see a 400 on the mapcontrol/3 files, this is likely the same issue.