Azure Maps Visual ignores Conditional Formatting (FX) in Power BI Service (Works in Desktop)

[Saamy]

Description:
I am encountering a rendering issue with the Azure Maps visual in Power BI Service where point-level conditional formatting is ignored, reverting all bubbles to the default blue color.

Environment:

• Power BI Desktop: Colors render correctly.
• Power BI Service: Colors fail (show default blue).
• Visual: Azure Maps (Bubble Layer).
• Browser: Edge/Chrome (Hardware Acceleration is confirmed ON).

The Issue:
I have a DAX measure returning Hex codes for Bubble Colors. This works perfectly in PBI Desktop. When published to the Service, the Azure Map renders all points as default Blue. Furthermore, the "fx" (Conditional Formatting) icon/option often disappears from the Format Pane in the Service, suggesting the visual has entered a fallback rendering mode.

Troubleshooting Steps Already Taken (Isolation Tests):

1. Bing Maps Control Test (Crucial): I switched the exact same data and measure to the standard "Bing Map" visual. It works perfectly in the Service. This confirms the Data Model and DAX are correct.
2. DAX Verification: I displayed the color measure in a Table Visual in the Service, and it correctly outputs Hex codes (e.g., #FF0000).
3. Clean Slate Test: Created a new report page with a fresh Azure Maps visual, using only Latitude, Longitude, and the Color Measure (no tooltips, no extra filters). It still fails in the Service.
4. Legend Field: Confirmed the "Legend" bucket is empty (to avoid known rendering conflicts).
5. Data Volume: Tested with a filter reducing data to less than 100 rows. The issue persists.
6. Data Types: Confirmed Latitude and Longitude columns are set to "Decimal Number" and Data Category is set to "Latitude/Longitude".

[Shravan133 · Accepted solution]

That’s a known limitation. Many users face this issue. You’ll find similar posts in the forum too. 

Maybe use a calculated column instead of a measure ??

BubbleColorColumn =

IF( 'Table'[Value] > 0, "#00FF00", "#FF0000")

Then:

• Use Data colors → Field value
• Select the column (not a measure)

Or  Use categorical colors via Legend (limited but safe)

Instead of hex:

ColorCategory =  SWITCH( TRUE(), [Value] > 0, "Positive", "Negative")

Then:

• Put ColorCategory in Legend
• Assign colors manually

[Suzanne98]

We are facing the same problem with the Azure Maps visual.

• Conditional formatting (FX) does not work at all — not in Desktop and not in the Service
• The visual always shows the default blue color, regardless of the color measure
• Filters on the Azure Maps visual are also not working
• Switching to Bing Maps works correctly, so the data model and DAX are confirmed to be valid

It looks like Azure Maps is failing to render properly in both Desktop and Service.

[Saamy · Accepted solution]

Hello everyone,

I found a temporary solution: in the Power BI Service, the conditional formatting for the colors is empty by default. Once I configure it again, everything works properly. Note that this issue appeared recently — I believe it may be due to an update in the Power BI Service. Also, I have to redo this each time I publish updates to the report.

Thank you for your help.

Regards,
Samy

[Shravan133 · Accepted solution]

That’s a known limitation. Many users face this issue. You’ll find similar posts in the forum too. 

Maybe use a calculated column instead of a measure ??

BubbleColorColumn =

IF( 'Table'[Value] > 0, "#00FF00", "#FF0000")

Then:

• Use Data colors → Field value
• Select the column (not a measure)

Or  Use categorical colors via Legend (limited but safe)

Instead of hex:

ColorCategory =  SWITCH( TRUE(), [Value] > 0, "Positive", "Negative")

Then:

• Put ColorCategory in Legend
• Assign colors manually

[EvdMeij]

This is not a good solution for large datasets. MS needs to fix this issue quick. The color coding works for other visuals, but fails for the Azure Map visual.

[v-menakakota]

Hi @Saamy ,

Thanks for reaching out to the Microsoft fabric community forum. 

I would also take a moment to thank  @Shravan133 , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .

Yes, this is a known limitation of the Azure Maps visual in the Power BI Service.

Best Regards, 
Community Support Team