esri ArcGIS Map Power BI Desktop Permissions

[hathouse]

We have used the ArcGIS map, one of the standard Power BI visuals in Desktop for years.  Today, the map stopped showing and instead we see a screen that reads "Access to this content requires permission.  Sign in below, or contact the content's owner for access".  No sign in was required before and there is no "sign in" options in the displayed visual.  What gives?!  This is for a production dashboard and now one of our visuals doesn't function.

[Dhuyvetter]

I'm still having this issue. Has the fix been rolled out at any version of Power BI yet?

[Anonymous]

Yes, there have been 2-3 releases since this post. Please clear your caches and restart Power BI if you are still seeing issues accessing the map.

https://doc.arcgis.com/en/power-bi/get-started/clear-browser-storage.htm#ESRI_SECTION1_E57387BD989D4...

[Anonymous]

What else could be causing the issue? I'm still recieveing the same issue on multiple computers and multiple versions (2.99 and 2.10). I've removed the CEF and Cache folders, restarted computer, and still see the "access to this content requires permissions. Sign in below, or contact the content's owner for access." message when trying to use ArcGIS Maps for Power BI.

[Dhuyvetter]

Yep, I removed the CEF and Cache folders and am still getting the error as well.

[mikeyG]

I am still experiencing this issue in Jan 2024. Has there been any solution for this issue?

[laurenmarar]

I too have removed the CEF and Cache folders, restarted computer, and still see the "access to this content requires permissions. Sign in below, or contact the content's owner for access." message when trying to use ArcGIS Maps for Power BI.

[v-stephen-msft]

Hi @hathouse ,

Maybe you can try the below solutions

• Clear Browser Cache (both Chrome and Edge)
• Upgrade Power BI Desktop to the latest version or re-install Power BI Desktop
• Change the default Browser (both Chrome and Edge not work)
• Clear Desktop Cache
  https://community.powerbi.com/t5/Desktop/Esri-Arcgis-Maps-Power-BI-error-after-february-update/td-p/...

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous · Accepted solution]

There was a bug in the release that went out yesterday. Good news is that we have a fix for it, but it will take some time to deploy. If you need an ArcGIS Account for a temporary fix I can set you up with one.

Once you have an account

1. Edit the report

2. Add a new tab

3. Add the ArcGIS Visual

4. Sign in with the account

5. Save the report

6. Edit the report again

7. Delete the tab.

8. Save the report

You can email me with your contact info at astauffer(AT)esri.com and I will get you a temporary account.

[Anonymous]

I'm getting the same issue. Is there an ETA on the fix?

[Anonymous]

Getting the same error.  Can I get a temporary account as well please.

[Anonymous]

Same issue occuring for me in production dashboard. No ability to sign in given, blocking production UI. 

Is this a licensing change from Esri? If this is no longer supported with Power BI Pro we will move to a different application. 

[clayk]

To overcome "Access permission" issue in my production reports, I edited the reports on the PBI service, created a new report tab, hid the tab, added a new ArcGIS viz, signed in with the temp acct @Anonymous helped me setup.  ... then my existing ArcGIS visuals on existing tabs rendered

[hathouse]

ctucker93 - if you find a solid map replacement, please share the visualization details.  We have yet to find a viable alternative that doesn't require lat/lon for our 4000+ locations.  Thanks!

[Jglenn]

We are experiencing the same issue. It was actually working for a bit after I did the latest update (Version: 2.96.1061.0 64-bit (August, 2021)), then stopped working when I went back to that report.

[AdamBr]

For anyone still suffering from this problem, I found that the problem persists only in old reports. If you are having this problem after clearing the caches, try creating a brand new report, you should find it works there.