Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
Hi Power BI Community,
I’m facing an issue after the latest Power BI September update. I was using the basic map visual in my report, but following the update, I’m being prompted to switch to the new "Azure Map" visual since the old map visual is being deprecated.
In the old map visual, I could place the same field (e.g., Country) in both the Location and Legend sections, and then use a measure like Received_Quantity in the Bubble Size to display the data as needed. However, with the new Azure Map visual, I’m encountering a problem. When I try to put the same field (Country) in both Location and Legend, the visual breaks as seen in the below screenshot.
Is this a known issue, or am I missing a setting? How can I use both the Location and Legend fields together in the Azure Map visual to replicate the functionality of the old map visual?
Thanks in advance!
Solved! Go to Solution.
Thanks @v-sshirivolu for your repsponse. Will try out the workarounds if the Azure Map visual no longer supports the same.
Hi @Seadon ,
Thanks for reaching out on the Microsoft Fabric Community Forum.
What you're seeing with the Azure Map visual is expected behavior in the updated version, it no longer supports using the same field for both Location and Legend. This change is due to updates in how the new visual engine handles multiple data layers. There are a few workarounds to get things working the way you want - Create a separate field for Legend. In Power Query, just duplicate your Location column. For example:
= Table.AddColumn(Source, "Country_Legend", each [Country])Then, use Country for Location and . Country_Legend for Legend. This keeps everything compatible and restores the expected color grouping other option - Switch back to the classic Map visual. Go to File - Options - Preview Features and turn on Classic Map visual. This version still allows you to use the same field for both Location and Legend.Option 3: Use color by measure instead. If you're only looking to show color variation by value, you can skip the Legend field entirely and use a numeric measure in Color saturation or Bubble size or Use multiple layers in Azure Maps with the new visual, you can layer different visual types - like filled regions and symbols, to separate geography from category groupings more clearly.
Best regards,
Sreeteja.
Thanks @v-sshirivolu for your repsponse. Will try out the workarounds if the Azure Map visual no longer supports the same.
Hi @Seadon ,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Hi @Seadon ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
Hi @Seadon
The issue you’re facing is due to a change in the new Azure Map visual (Sept 2025 update).
In the old Map visual, you could use the same field (e.g., Country) in both Location and Legend without problems.
In the new Azure Map, this setup is not supported and results in the “invalid query / error fetching data” message.
This is not a bug on your side, but a limitation/behavior change in the updated visual.
To Fix: Keep Country only in Location and use a different field (like Category, Region, or Group) in Legend.
If you only need color by Country, you don’t need Legend at all.
If you want the same old behavior, you can still use the basic Map visual until it is fully retired.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 78 | |
| 48 | |
| 35 | |
| 31 | |
| 27 |