Fabric Workspace Settings - PowerBINotAuthorizedException

[Kaviraj11]

There's no issues to the workspace but we see the pop up as below:

 Any one encountered this?@workspace

[BenHickmanNHS]

Yes we see this as well, as you say doesn't seem to be causing any obvious issues

[v-yifanw-msft]

Hi @Kaviraj11 ,

Can you provide some detailed information such as when did this popup start appearing and did you do anything else before the popup appeared?
How is the appearance of the popup currently affecting your workspace and can you provide detailed error information. Detailed information can help us better understand and solve the problem you are experiencing.

Best Regards,

Ada Wang

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

[Kaviraj11]

In our case, we used to have an individual users as an Admin assigned to the workspace access. However, when we combined all the users into a security group and use that as Admin then we started seeing it. If we add back one individual users as admin, the error goes away. The error that is coming up currently doesn't impact anything at the moment. 

[SteelPaladin]

All of our workspaces currently have a combination of user and group admins, but I see the error in any workspace where my access is coming from a security group. If I am an individual admin in the workspace, it does not show up. As an additional note, the error shows up despite the workspace being assigned a Fabric Capacity and my account having a Premium Per User license for Power BI.

As others have noted, there is no other text/info beyond "PowerBINotAuthorizedException," and no functionality seems to be affected.

[blopez11]

Oh, that is interesting.  We have always used a security group to assign admin rights.

[blopez11]

For us, I noticed this happening about a month ago.  It is easy to reproduce.  Navigate to a workspace (it can be in shared on premium capacity, doesn't seem to matter), select Workspace settings and the error shows just as posted.  There are no additional details associated with the error, just the x to make the message go away.  It doesn't seem to impact anything that I can tell.  We do not have anything special setup for the workspace, like git integration, azure connections, etc.

Maybe @Kaviraj11 can provide more in their experience.

[blopez11]

We are seeing this as well.  Curious to know as well.