Azure Maps Data-Bound Reference Layer WITH Markers Issue

Hi bjuar,

Thanks for reaching out to the Microsoft Fabric Community forum. and thanks to rajendraongole1 for sharing valuable insights.

The Azure Maps documentation describes the following behavior:

• A data-bound reference layer uses the Location field to match the values in your dataset with the corresponding properties in the uploaded spatial file.
• To display data points, the Azure Maps visual supports either Latitude/Longitude fields or geospatial data in the Location field.

For more information, please refer to the below official documentation:

Get started with Azure Maps Power BI visual - Microsoft Azure Maps | Microsoft Learn

Add a reference layer to Azure Maps Power BI visual - Microsoft Azure Maps Power BI visual | Microsoft Learn

I hope this helps. Please feel free to reach out if you have any further questions.
Thank you.

Hi,

This is a known limitation of the Azure Maps visual. The Location field well is used for geocoding, and when multiple geographic fields (such as Region and Address) are added, the visual may prioritize one over the other, which can affect either the reference layer or the markers.

A few approaches you could try:

• Keep the Reference Layer driven by your region polygons, and use the Address field only in the Bubble/Marker layer (if supported by your visual configuration), rather than combining both in the Location well.

• Ensure there is a proper relationship between your Region and Address tables so that the slicer filters both the polygon layer and the marker data.

• If possible, use Latitude and Longitude for the markers while using the Reference Layer for the polygons. This is generally the most reliable approach if your dataset includes coordinates.

• As a troubleshooting step, create a simple Azure Maps visual with only the Region polygon and Address markers to determine whether the behavior is due to the visual's limitations or the data model.

Could you also clarify:

• Are the Region polygons coming from a custom GeoJSON reference layer?

• Are the Address records related to the Region table through your data model?

• Is the slicer filtering the Region table, the Address table, or both?

The Azure Maps documentation may also be helpful:

• https://learn.microsoft.com/power-bi/visuals/power-bi-visualization-azure-maps

If you've already confirmed the model relationships and the behavior still occurs, this may be a current limitation of the Azure Maps visual when combining data-bound reference layers with address-based geocoding.

If this reply helps, please consider giving it a Kudos. If it helps resolve your issue, marking it as the Accepted Solution will help other community members facing the same scenario.