Forum Discussion
Power BI react client embed Azure maps
Hello everyone,
It seems that the Power BI react client cannot display Azure maps anymore. Is it something changed silently by Microsoft? In more detail, I found that the issue lies in the following request, done by the powerbi-client itself. The report is embedded correctly and only the Azure Maps visual is not shown. Everything is enabled (tenant setting for Azure Maps and in Power BI desktop the Preview features were enabled when publishing the report). Below is a screenshot from the AzureMapToken request. As you can see the "authorization" header is wrong. It contains the embed token instead of "Bearer {access token}".
For comparison the same request from Power BI service contains the correct value:
For reference: powerbi-client
PS. The Azure Maps visuals were working as expected a couple of weeks ago.
Any ideas? It seems to be a Microsoft issue.
Hi panosmir ,
Although Azure maps happened to work for App Owns Data embed in preview, the documentation has always clarified that we do not officially support Azure maps for apps owns embed yet. See the screenshot below.
Get started with Azure Maps Power BI visual - Microsoft Azure Maps | Microsoft Learn
We are working on ways to support this in the future.
Best regards,
Community Support Team_yanjiang
27 Replies
This certainly is disappointing. But what is even more annoying is that I now have to see "CONVERT OVER TO AZURE MAPS" popup every time I open a PBI file likely another 500 times until you guys deliver this for embedding. I feel as an embedded user we are always on the back burner of the developers minds. Why force this down our throat when we can't use it. Please get rid of the popup.
We noticed the same thing start last Wednesday (5/3) when they had been working the day before. Hopefully this gets resolved quickly.
amitchandak Greg_Deckler ibarrau lbendlin GilbertQ,
Could you please share any information if came across any update.
Have you heard any updates? We use the Azure maps a lot because of the ability to add GeoJSON reference layers and if they are no longer being supported we need to make the switch to another visual.
We have observed the same issue (incorrect header authorization). It works for us in Power BI but not when embedded and the authorization is "EmbedToken" not "Bearer". The issue started for us (UK South) around 12th May on this call:
https://wabi-uk-south-c-primary-redirect.analysis.windows.net/metadata/v202212/azureMapToken
We are using .net/Javascript to embed.
Any news?
Update from the ticket we created with MS Support
Have some unfortunately bad news to share. Per Product Team, Azure Maps visual has been shifted from preview to production. Part of this change is the different authentication mode for Azure Maps. What this entails is that embedding reports with this visual are no longer supported and can only be used under some limitations. They supplied the following link
We asked for a workaround, and they replied with this:
There is no workaround for embedding the Azure Maps visuals at this time. You could use the regular map visual or the ArcGIS visual to get some of this functionality back. See the following pieces of documentation for more details:
https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-map-tips-and-tricks
https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualizations-arcgis
If anyone finds a fast way to implement something that can replace the functionality, please report back. Thanks.
It's interesting that they suggested the ArcGIS visual when that is also blocked for embedded maps. This is incredibly frustrating; the ability to add geojson reference layers was very valuable for us.
Is there any admin here to inform us if it's a bug or intended behavior? As this is blocking to our solutions and it's not that easy to change all the map visuals.
Same issue here. We noticed it May 4. A team member found this thread. Looking for solution as well. Thanks
Same issue here as well. We noticed it stopped working at the 4th, hope it will be fixed soon
Still the same here, it would be nice someone to give as a proper reply with an explanation of the reason and a proper solution or workaround
