Forum Discussion
Azure map visual doen't show bubbles (pizza chart) when published
Hi mmatteSP , Thank you for reaching out to the Microsoft Community Forum.
The issue is likely due to Azure Maps-specific settings. Please ask your admin to check Tenant settings in Power BI Service to ensure Azure Maps visuals are enabled and that any required Azure Maps API keys or credentials are configured correctly. In Power BI Desktop, confirm the "Estado" column is categorized as State or Province under Column Tools and test with a simplified Azure Map before republishing. Try viewing the report in a different browser or incognito mode to rule out rendering issues.
Regarding Bing maps, I apologize for the confusion, I didn’t read the heading and just saw your screenshots which resembled a Bing Maps style, which is the default in Power BI and assumed it was the map provider in use.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.Hi mmatteSP , Thank you for reaching out to the Microsoft Community Forum.
Thanks for the update and the screenshot. Hope admin gets back to you soon. Since merging tables didn’t help and the issue persists after publishing despite verified data, the problem is likely due to network restrictions rather than the report or API credentials, Power BI Service handles Azure Maps keys internally. Ask your admin to ensure endpoints like atlas.microsoft.com, *.azureedge.net, and *.maps.azure.com are not blocked by firewalls or proxies, as these are required for Azure Maps rendering. For a quick test, try viewing the published report from a personal device or outside your network, if it loads, it confirms a network issue. As a fallback, recreate the Azure Map with just Estado and a measure in Desktop, republish and check again.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi mmatteSP , Thank you for reaching out to the Microsoft Community Forum.
The issue is likely due to Azure Maps-specific settings. Please ask your admin to check Tenant settings in Power BI Service to ensure Azure Maps visuals are enabled and that any required Azure Maps API keys or credentials are configured correctly. In Power BI Desktop, confirm the "Estado" column is categorized as State or Province under Column Tools and test with a simplified Azure Map before republishing. Try viewing the report in a different browser or incognito mode to rule out rendering issues.
Regarding Bing maps, I apologize for the confusion, I didn’t read the heading and just saw your screenshots which resembled a Bing Maps style, which is the default in Power BI and assumed it was the map provider in use.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi v-hashadapu . I confirmed that the settings are enabled for Azure Maps visuals:
The column "Estado" is is categorized as State. I have done another test, this column was in a related table, so I merged to the data table, aiming to buildo a unique table in the model. This has the same result again. I must wait the answer from the Admin about Maps Azure API or credentials...
I am very gratefull for your attention
Hi mmatteSP , Thank you for reaching out to the Microsoft Community Forum.
Thanks for the update and the screenshot. Hope admin gets back to you soon. Since merging tables didn’t help and the issue persists after publishing despite verified data, the problem is likely due to network restrictions rather than the report or API credentials, Power BI Service handles Azure Maps keys internally. Ask your admin to ensure endpoints like atlas.microsoft.com, *.azureedge.net, and *.maps.azure.com are not blocked by firewalls or proxies, as these are required for Azure Maps rendering. For a quick test, try viewing the published report from a personal device or outside your network, if it loads, it confirms a network issue. As a fallback, recreate the Azure Map with just Estado and a measure in Desktop, republish and check again.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.