Forum Discussion
Teams and RLS
Hi everyone,
I have set up RLS and it works fine when people are accessing the Dashboard and reports online. However, when I add my dashboard on the MS Teams, the RLS fails and anyone who is a member can see the full report. What do I need to do to maintain the RLS?
20 Replies
- AnonymousNot applicable
Jawed Are the members in the workspace read only / viewers in the PBI workspace?
- Jawed
Helper III
That is right Anonymous
- v-juanli-msft
Community Support
Hi Jawed
1.You publish datasets and reports to an App Workplace, then you set RLS in the datasets for the members of this Workplace.
Right?
2. "I add my dashboard on the MS Teams"
what does MS Teams refer to? A workplace?
Is this dashboard a new dashboard or an exsit dashboard in that App Workplace?
Which dataset does the dashboard come from? does this dataset set up RLS alreadly?
for example, when i pin a tile from a report A(its dataset doesn't set up RLS) to a daskboard A, then RLS fails for that tile.
3. Based on my test, the dataset which the dashboard use need to set RLS so members with read permission could see limited data.
Best Regards
Maggie
Best Regards
Maggie
- Jawed
Helper III
I have my dashboard, report and its dataset in the workspace. I have set up the RLS and have shared it with my team. Up to here is all fine and when team members are accessing it, it works fine.
The issue arises with MS Team. MS Teams is similar to Skype and you can collaborate with your colleagues and is part of Office 365. In the Teams, you can share Sharepoint folders, calendars and Power BI dashboards. So, when I share it in the Teams, the RLS completely fails. The same person who has limited access to the Dashboard in Power BI can now access the same file through Teams but can see the whole dataset.
I hope it makes sense.
- v-juanli-msft
Community Support
Hi Jawed
Not sure about what steps you have applied.
According to this article, to let RLS work, you need to add MS Team in the dataset->Security->add members
If you previously defined roles and rules in the Power BI service, you must re-create them in Power BI Desktop.
Please review this thread, i hope thia may give you some idea
https://community.powerbi.com/t5/Service/Microsoft-Teams-Pro-Licence-Required/td-p/90339
Best Regards
Maggie
- AnonymousNot applicable
Jawed ,
Did you get a solution for your problem ? did MS confirm reagrding this restriction? i am also looking for a solution on the same.
- Jawed
Helper III
Hi Anonymous. No, I have not been able to find a solution to it. Currently, if you share the report on the Team, the RLS fails.
- AnonymousNot applicable
Hi Jawed , I am also hanging with the same issue. did you get any confirmation from Microsoft consultant on the same?
are they working on the vote of this issue ? any idea would be helpful. Bcz y clients want the reprot over Teams with RLS mechanism.
- AnonymousNot applicable
I have yhe same problem with Teams and Power BI RLS with Roles.
I Wonder when this will be fixed for Teams.
- Jawed
Helper III
I havent heard anything. I hope they do take this seriously.
- AnonymousNot applicable
No Luck yet.
- KevinFromWpgFrequent Visitor
Hi all,
I am new to this same issue, and have played around a bit. I don't know if this is an official solution, but the way I "seem to" have gotten it working is with the following steps:
1. Publish the report to a different workspace (I used "My workspace").
2. Add a new tab in the team you want to share it with and select the PBI report from My Workspace.
3. In the PBI service, go to the PBI report and share it with the necessary users (I only gave them READ access)
4 In the PBI service, add the users to the role under SECURITY for the dataset
5. As a double check - ensure the users have READ access under the MANAGE PERMISSIONS for the dataset
I did that, and it seems to be applying the proper RLS from within the team tab now. I have not done very thorough testing of this yet, so thought I'd share and see if it resolves the issue for some of you as well.
- v_mark
Helper V
This is also the same scenario I have. In the Service, everything works fine. In Microsoft Teams, all data points are being exposed.