Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now

danielpmaximo27

Azure Maps reference layer transparency behaves differently after publishing to Power BI Service

Submitted by Advocate I on ‎01-28-2026 07:40 AM

Hello everyone,

I’m facing an issue with the Azure Maps visual in Power BI after this new update and I’d appreciate any help or insights.

I added a reference layer to an Azure Maps visual. In Power BI Desktop, the reference layer behaves as expected: the transparency works correctly, allowing me to clearly see the base Azure Maps content behind it (street names, places, establishments, etc.).

However, after publishing the report to Power BI Service (web), the same reference layer appears as if its transparency were 0% (fully opaque). As a result, it completely hides the underlying Azure Maps details, such as street names and other map information.

Has anyone experienced a similar issue with Azure Maps visuals behaving differently between Desktop and Service?

Is this a known limitation or bug, or is there any workaround to ensure the transparency is respected after publishing?image.jpg

Status: Accepted

The issue has been identified and a fix will be out in 3-4 weeks, thanks for reporting.

The issue only occurs when the reference layer keys result in zero matches with the location field query results. It's an issue with "selection" interaction manager, clicking anywhere on the map should clear initial selection state for this case and render with expected transparency.

See more ideas labeled with:
1 Comment (1 New)
Comments
mattlee
Microsoft Employee
Microsoft Employee
‎02-19-2026 11:54 AM
Status changed to: Accepted

The issue has been identified and a fix will be out in 3-4 weeks, thanks for reporting.

The issue only occurs when the reference layer keys result in zero matches with the location field query results. It's an issue with "selection" interaction manager, clicking anywhere on the map should clear initial selection state for this case and render with expected transparency.

Idea Statuses