Azure Map - Performance issue

Hi riccardo_ 

Yes! Azure Maps is currently heavier and slower than the old Bing Map.
What you’re seeing is known and widely experienced, not a misconfiguration.
Azure Maps is still evolving and has not reached performance parity with Bing Map yet. There’s no public timeline for full optimization.
What you can do now (practical fixes):
1. Reduce data points aggressively

• Pre-aggregate in Power Query
• Avoid row-level plotting
• Group by:
  • City / Region instead of Lat-Long
  • Buckets instead of raw points

2. Limit interactions

• Turn off unnecessary visual interactions
• Avoid cross-filtering Azure Map from many slicers

3. Use filters BEFORE the map

• Page / report filters
• Don’t rely on Azure Map to handle large result sets dynamically

4. Consider alternatives (very common)

• Icon Map (certified custom visual) → much faster
• ArcGIS Map → better performance for large datasets
• Keep Azure Map only for low-volume, high-detail use cases

Always Remember:

• Azure Maps = better features, worse performance (for now)
• If performance is critical:
  • Don’t do row-level or high-cardinality maps
  • Aggregate first, then map
  • Or switch visuals

=================================================================
Did I answer your question? Mark my post as a solution! This will help others on the forum!

Appreciate your Kudos!!

Jaywant Thorat | MCT | Data Analytics Coach | Super User
LinkedIn: https://www.linkedin.com/in/jaywantthorat/
Join #MissionPowerBIBharat: https://tinyurl.com/JoinMissionPowerBIBharat
#MissionPowerBIBharat
LIVE with Jaywant Thorat