Azure Maps Reference Layer in Power BI won’t load GeoJSON from Azure Blob (URL works in browser)

[MagdaS]

I’m trying to add a Reference layer to the Azure Maps visual in Power BI using a GeoJSON hosted on Azure Blob Storage. The direct URL opens fine in the browser (also in incognito), but the layer doesn’t render in Power BI—no shapes appear.

What I’ve tried

• Content-Type on the blob is set to application/json.

• File opens as raw JSON in the browser (no login), including in Incognito.

• Ensured HTTPS.

• Checked the GeoJSON structure: FeatureCollection → Feature with Polygon, coordinates are [longitude, latitude], outer ring closed (last point equals first).

• SAS URL with Read (sp=r), Blob (sr=b), HTTPS only, future expiry.

  CORS on the Storage Account → Blob service:

  • Allowed origins: https://app.powerbi.com

  • Methods: GET

  • Allowed headers: *

  • Exposed headers: *

  • Max age: 360

[v-echaithra]

Hi @MagdaS ,

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Best Regards,
Chaithra E.

[v-echaithra]

Hi @MagdaS ,

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-echaithra]

Hi @MagdaS ,

Thank you @Shahid12523  for your response.

I hope the information provided is helpful. I wanted to check whether you were able to resolve the issue with the provided solutions. Please let us know if you need any further assistance.

Thank you.

[Shahid12523]

Power BI’s Azure Maps reference layer won’t always load GeoJSON from a SAS blob even if the URL works in a browser. Common issues:

1.CORS/SAS: Power BI may not handle SAS URLs well. Test with a public blob or add https://*.powerbi.com to allowed origins.

2.GeoJSON format: Must be FeatureCollection, polygons as [ [ [lng, lat], … ] ], outer ring clockwise.

3.HTTPS & direct response: No redirects; Content-Type = application/json; inline response.

4.File size: Very large or many features can fail silently.

Workarounds:

Make blob public temporarily.

Host on GitHub or Azure Static Website.

Embed small GeoJSON directly in Power BI.