Forum Discussion
Azure map performance in Share to Web
Hi all,
I have a client that uses a report to share information about their organisation on their website.
Part of this is a map. We recently replaced the original map visual with the new Azure map.
It was performing very well with the old map visual. It seems a little bit slower with the Azure map when you use it in Power BI desktop and a regular published report but still ok.
The published report that has been shared to web however is extremely slow. The rest of the report works fine. Its just the Azure map and only in Share to web.
Anyone else experience this? Any tips to change performance? I cannot really reduce datapoints as that would make the whole map useless.
Thanks
7 Replies
Hi jeroendekk
What happens if you had to go back to the previous map? Does the performance come back? If it does, then clearly there is a problem with the Azure map.
Yes, it is definately the Azure map. The default maps are going away so those are not a long term alternative. But maybe I should look at custom map visuals instead.
Hi jeroendekk
Thank you for reaching out to the Microsoft Fabric Forum Community.
GilbertQ Amar_Kumar Thanks for the inputs.
jeroendekk Inputs from users are useful. As you mentioned, are you using a custom map visual now? Has your issue been resolved? Please let us know if you experience any further issues.
Thanks.
Yes, this is a known and fairly common issue with Azure Maps, especially when used with Share to web.
What is happening:
Azure Maps relies on external tile and service calls
In Share to web, the report runs in a more restricted, anonymous environment
Azure Maps loads tiles, layers, and data slower there than in Desktop or normal published reports
The old Map visual is simpler and lighter, so it performs better
Why it only happens in Share to web:
No user authentication
No premium capacity
Stricter throttling and caching
Azure Maps requests are slower and sometimes serialized
Things you can try (limited options):
Reduce visual complexity (not data points)
Turn off unnecessary layers
Disable clustering if enabled
Reduce bubble size variation
Remove tooltips that use heavy measures
Pre-aggregate data
Aggregate at the highest usable geographic level
Avoid raw row-level plotting if possible
Disable auto zoom and auto fit
Fixed zoom levels load faster
Test with “Filled map” or old Map visual
For Share to web specifically, old Map often performs better
Many teams keep Azure Maps only for authenticated users
Separate public vs internal reports
Use old Map visual for Share to web
Use Azure Maps for internal or app-based sharing
Important note:
There is no real “performance tuning” for Azure Maps in Share to web
This is a platform limitation, not your report design
