Forum Discussion
Getting Operation returned an invalid status code 'Unauthorized' while trying to embed a Power BI ap
Hi, peterhvogel
Regarding the issue you raised, my solution is as follows:
1.First, in Workspace role assignments, we recommend that you assign members and above roles to the security group of the service principal app.
Here is a screenshot of the official documentation:
For more information, please refer to the following links:
Embed content in your Power BI embedded analytics application - Power BI | Microsoft Learn
2.Secondly, if you want to go into production, it is recommended that you upgrade your capacity.
Here is a screenshot of the official documentation:
For more information, please refer to the following links:
Move your Power BI embedded analytics app to production - Power BI | Microsoft Learn
Capacity and SKUs in Power BI embedded analytics - Power BI | Microsoft Learn
Of course, if you have any new ideas, you are welcome to contact us.
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I'll try assigning the member role to the security group that my principal belongs to and see if it helps.
Hi, peterhvogel
Looking forward to your reply and hope your problem can be solved.
If you have any relevant experiences during this period, you are also welcome to share them with us.
If his post is helpful to you, you can consider accepting it as a solution.
Thank you in advance.
Of course, if you have any new ideas, you are welcome to contact us.
Best Regards,
Leroy Lu
OK, so I started off by working through the whole process (turning on dev access to service principals, setting up the App Registration -- granting even more permissions than before, setting up the security group, managing access to the workspace) and I used Member status for the security principal's security group.
And it worked! First time! Yay!
But having a nasty, suspicious mind, I tried setting the security group's access to the workgroup to Viewer. And it still worked! <grump/>
So, it seems to me, that there are three possibilities:- Workspace access doesn't matter -- I did something wrong the last time, never spotted it, and did it right this time
- Specifically (most likely): I granted some permission this time that I didn't grant on the previous time and granting the permission this time made it work
- It is the workspace role...but it takes time for that change to propogate through to my app and, if I run the application again in (say) 60 minutes with access set to Viewer, it will fail
- It is the workspace role...but only the settings that are in place when the app first executes matter so if I don't have it right the first time, I'm doomed
Remembering that I'm testing this on a trial license, it's possible (I guess) that the last option is the correct one but that seems the least likely.
Of the two remaining options, the second seems most likely: I was testing, having a failure, changing something, testing again before the change had propogated, getting another failure and assuming my change wasn't helping. To test that, I'm going to walk away from the keyboard for an hour and see what happens when I run the app again with workspace access set to Viewer.
If the app continues to run with workspace access set to Viewer, I'm going to have to test the first option by creating a series of App regisrations with different sets of permissions. <fun/><sarcasm/>I left the application alone for the rest of the day and when I ran it, it failed with the "Unauthorized" message. I changed the Power BI workspace access for the security group that my principal is part of back to Member and, on my next run, the program ran just fine. I've marked the answer as the solution because it sure was!
- Workspace access doesn't matter -- I did something wrong the last time, never spotted it, and did it right this time