Row Level Security issue in Service

[thalaridevika40]

Hi All,

We created a report with RLS using USERPRINCIPALNAME() and published in service in 2 different workspaces. 

1. DEV    2. UAT

The report consists of 3 different selection according to the user level. 

Ex: 1st user has 1 selection, 2nd user has 2 selections to see the data when they run the reports with their ID's. 

2nd, 3rd users are having viewer roles and 1st user is having Admin role and diplaying all 3 selections which is not correct.   

I have changed 1st User from Admin to Viewer role to effect RLS . 

RLS is working as expected in DEV environment for all 3 users when they run the report and for the same reports it's not working in UAT evnironment for the 1st user. 

Did any one faced the same issue , let us know the solution. 

[v-zhengdxu-msft]

Hi @thalaridevika40 

It's great to hear that you've identified the role of the user (Admin vs. Viewer) impacts the application of RLS, as RLS filters are indeed not applied to users with Admin, Member, or Contributor roles within a workspace. Changing the first user's role to Viewer in the DEV environment and observing the expected behavior was the correct approach.

Double-check that the first user's role is indeed set to Viewer in the UAT environment. It's possible the role change did not apply or save correctly.

Ensure that the RLS configuration (roles and DAX expressions) in the UAT environment exactly matches that of the DEV environment. Any slight difference in DAX expressions or role assignments can lead to different behaviors.

Sometimes, cached credentials or data in the Power BI Service can cause unexpected behavior. Ask the first user to clear their browser cache or try accessing the report in an incognito/private browsing window to see if the issue persists.

Best Regards

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

[Joe_Barry]

Hi @thalaridevika40 

To troubleshoot.

• RLS won't work if a user is a member of the Workspace where the report is stored
• Have you assigned the user to the role in the Dataset Security section?
• Not sure what your comany's licensing is, if it is Premium, then the Workspace needs to be Premium for someone to even be able to view a report stored there.

Hope this helps with putting you on the right path

Joe

[thalaridevika40]

Hi Joe, 

Thank you for the Reply. 

• User is not a member of the workspace and he is having the viewer role. 
• User addded to security roles in the Dataset and we are holding pro license. 
  
  But the in Dev environment for all 3 users RLS is working fine but for 1st user only RLS is not working in UAT. 
  
  Let us know any your ideas or some more option to implement if you have to check the issue. 
   

[Joe_Barry]

Check the settings in the Dev and duplicate them in UAT. Although the documentation says that a viewer role is ok in a workspace, try removing the User completely from the Workspace and just share the report with them using the Share button and see if it helps. Look into the Dataset permissions, maybe there are some build permissions added by mistake.. Maybe remove all permissions for the user before sharing with the user