topic Power BI Embed Errors in Developer

Power BI Embed Errors

fosters4him — Fri, 17 Jul 2020 00:19:54 GMT

It was noticed shortly after 7/1 that our production Power BI Embed webpage started returnning "Unauthorized access"I thought it was maybe the app registration secret had expired, nope, it is set to never. I used the production code and configured for http://localhost:13526/ and yesterday that was working fine, kept working with it and now I get . "The remote server returned an error: (401) Unauthorized." Tried created a new app registration using https://dev.powerbi.com/apps and set it up server side, usedd http://localhost:13526/ for the target and redirect urls. After request for credentials, I get the authorization to use the api, and then after that I know get "The remote server returned an error: (401) Unauthorized." I did notice the Embed samples are updated to .Net 4.8, I am not sure if that is what is causing my issue as I used the embed samples from about 3 years ago. Any insight into this is much appreciated. Rick

Re: Power BI Embed Errors

Anonymous — Fri, 17 Jul 2020 16:34:58 GMT

Hi @fosters4him

A couple of things come to mind...
Have you configured your app registration (in Azure) to have all required permissions for the actions you are trying to perform with the Power BI REST API?

In Azure you should be able to see something like the following.

If you are trying to fetch a list of dashboards for instance... then you will need 'Dashboard.Read.All' enabled.

If these are set correctly... and the generated secret hasn't expired, then it may be access to one of your workspaces in Power BI.
It is worth double checking that the workspace you are connecting through to - has got the registered account listed within the workspace access list.

I cannot remember if you still need to add the service account as an admin still - but that is what I have mine set to.

Let me know if any of this helps.
Cheers, Matt

Re: Power BI Embed Errors

fosters4him — Tue, 21 Jul 2020 22:32:37 GMT

Hi, The issue was resolved by upgrading the PBI code line to .Net 4.8 and adding SSL to the website (now required for redirect).