Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
acprs
Frequent Visitor

RLS - working in desktop but only working for some users in service

 

I've managed to get RLS working on one report but on another with all the same settings I am finding that on service some users can see only their own relevant data (as planned) while other users can see everyone's data.  I can't see that any settings are different for the users.  I have added them under security and have also added them in manage permissions with read permission only.  They are not added to the shared workspace as I want them to acces some reports only. I've tried most things I can find suggested but nothing seems to explain why it might be working for some but not others.  In desktop using "view as" it works for everyone.

 

Would anyone have an idea as to why this migth be happening?

 

Many thanks

12 REPLIES 12
acprs
Frequent Visitor

Thank you - I have now spent some time testing and it seems taht once users have accessed the report twice clicking on the link I send, they are then able to see their own data only and rls appears to work - I don't know why but presume my admin rights are affecting things

v-jiewu-msft
Community Support
Community Support

Hi ,

Try to delete the RLS, recreate the new RLS on the report and refresh the service page to see if the user can see all the data.

You can also view the following links to learn more information.

Solved: RLS not working for one user on service - Microsoft Fabric Community

Solved: RLS security working in desktop but not service de... - Microsoft Fabric Community

Row-level security (RLS) with Power BI - Microsoft Fabric | Microsoft Learn

 

Best Regards,

Wisdom Wu

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

Poojara_D12
Super User
Super User

Hi @acprs 

If RLS works in Desktop but not in Service for some users:

Common Issues and Fixes:

  1. Workspace Permissions: Ensure affected users are not in the workspace, as workspace roles bypass RLS.
  2. Dataset Permissions: In Power BI Service, check Manage Permissions for the dataset. Ensure users have Read-only access.
  3. RLS Role Assignment: Verify users are assigned to the correct RLS role under the dataset's Security settings.
  4. Cache Issues: Clear browser cache, and ask users to log out and log back in. Republish the report if needed.
  5. App Sharing: If using an app, ensure dataset permissions respect RLS and users have no conflicting permissions.
  6. Groups: If using Azure AD groups, confirm affected users are correctly assigned.

Troubleshoot:

  • Use Test as Role in Power BI Service to verify RLS for specific users.
  • Create a test report with the same dataset and configuration to isolate the problem.

Next Steps:

  • Recheck permissions and RLS role assignments.
  • Republish the dataset if issues persist.
  • Contact Microsoft Support if unresolved.

 

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂

Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS 

Hi @acprs 

 

As @Poojara_D12 has mentioned, this will only happen if the end users have elevated permission to workspace or dataset i.e beyond read-only. If he user has admin/member/contributor role, then it will bypass rls. Please double check in case user has only view or read-only access.

And if you find there is no issue with permission level that is granted for user, then share your dax code written for RLS. We will look into that.

 

Thanks,

Pallavi

 

Thank you - this is the role I have set up (works in another report). acprs_0-1734095493383.png

 

In manage permissions under direct access - all users are set to red:

acprs_1-1734095589182.png

All users are added to the role in service

 

acprs_2-1734095630444.png

 

 

Thank you for coming back so quickly! I think I have tried all of this - when I try using "test as role" it works for one user but not another and they have the same settings. I'm sure I'm missing something I'm not checking correctly but I just can't see what it is

 

When you suggest creating a test report - what should the report do differently to my problem report?

 

Thanks 🙂

Hi @acprs ,

The RLS code looks straightforward. should not create any problems.

Quick question-

1. Are these 2 reports in separate workspaces? the one that is working and the one not.

2. Are they guest users?

3. Do they have separate domain of their email address different from regular one?

Thanks,

Pallavi

Hi @pallavi_r

 

1. They are in the same workspace but users don't have access to the workspace, just the reports as needed

2. They are all members of our organisation licence but I wonder whether if they are not set up correctly this affects things?  However same user can view another report where the filters work correctly

3. All using the same organisation domain

 

Many thanks 🙂

 

Hi @acprs ,

Thanks for quick reply.  One more important question. Please send the snapshot of relationship between RLS table and Primary Table. 

I would like to see the cardinality, cross-filter direction etc, the entire snapshot of the report that is not working.

And would be great if you share also for the report that works.

Thanks,

Pallavi

Hi, sorry for the delay, this is the relationship snapsho for the one that doesn't work:

acprs_0-1734439814209.png

This one does work:

acprs_1-1734439982723.png

 

acprs_2-1734440010220.png

 

 

Thanks

 

 

 

 @acprs 

To create a test report for troubleshooting RLS issues:

 

Use the Same Dataset: Create a simple report with just a table/matrix showing fields like Region, Sales, or CustomerID.

No Filters: Avoid report/page-level filters to prevent interference with RLS.

Test Each Role: Use "Test as Role" for individual RLS roles in Power BI Service.

Direct User Assignment: Add affected users directly to RLS roles instead of using Azure AD groups.

 

Helps identify if the issue is in RLS configuration or report design.

Simplifies the setup to pinpoint the root cause.

If the test report works but the original fails, check for hidden filters or conflicts. If both fail, review dataset permissions or contact Microsoft Support.

 

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂

Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS 

thank you for this - I set up a test report with no filters.  When I use "test as role" in desktop the results are filtered but in service they are not and all data is shown

 

I'll have another look at permissions but I have both that I know of in service set as here:

 

acprs_0-1734102816835.png

 

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.