Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have a Microsoft Team called Distributors. It has 50 people in it.
Inside the Power BI service, there is an equivalent workspace called Distributors which was automatically created when we created the Microsoft Team. Distributors is set up as a group in the Microsoft admin center.
Inside the Distributors Team site, I made a private channel with just me and Distributor #1. Let's call her Sally.
I published a dashboard inside the private channel in Teams so that only Sally can see it. The other 49 people in the Distributors group cannot see it from within Teams.
However, when I log into the Power BI Service and view the Distributors workspace, access seems to be set at the workspace level, i.e. all 50 people can see this workspace. I see no channel-level structure equivalent.
How do I now restrict access to the one private dashboard which is stored in the Distributors workspace? It seems that the other 49 people, while they can't see the dashboard in Teams because it's in a private channel, would be able to log into powerbi.com and see the private dashboard.
How do I restrict access to this dashboard in powerbi.com? I'm trying to avoid having to create a Team site for every Distributor (50 Teams).
Thank you,
Tracey.
Solved! Go to Solution.
I would suggest you to enable 'Block the workspace creation' in Power BI Tenant settings so that whenever you create a new channel in MS Teams, it will not create Power BI Workspace.
For more information: Monitor usage metrics in classic workspaces - Power BI | Microsoft Docs
And to share a report with members of a private channel, I would suggest you publish your report to modern workspace and embed that report in your private channel. Since it's a modern workspace, which is not linked to Office 365 group, the members of your Teams channel will not have access to the workspace in Power BI.
Organize work in the new workspaces in Power BI - Power BI | Microsoft Docs
If you are looking for a solution regarding the existing reports, since they have access at the workspace level, the only way we can restrict them to not read the report data is by applying RLS.
Create a role without any filters and add the members of the private channel to the role. So that who are part of the role will be able to see the data and if other people try to access the report, Power BI will show a error dialogue box.
Row-level security (RLS) with Power BI - Power BI | Microsoft Docs
Did I answer your questions? Give a thumbs up and accept this post as solution!
I would suggest you to enable 'Block the workspace creation' in Power BI Tenant settings so that whenever you create a new channel in MS Teams, it will not create Power BI Workspace.
For more information: Monitor usage metrics in classic workspaces - Power BI | Microsoft Docs
And to share a report with members of a private channel, I would suggest you publish your report to modern workspace and embed that report in your private channel. Since it's a modern workspace, which is not linked to Office 365 group, the members of your Teams channel will not have access to the workspace in Power BI.
Organize work in the new workspaces in Power BI - Power BI | Microsoft Docs
If you are looking for a solution regarding the existing reports, since they have access at the workspace level, the only way we can restrict them to not read the report data is by applying RLS.
Create a role without any filters and add the members of the private channel to the role. So that who are part of the role will be able to see the data and if other people try to access the report, Power BI will show a error dialogue box.
Row-level security (RLS) with Power BI - Power BI | Microsoft Docs
Did I answer your questions? Give a thumbs up and accept this post as solution!
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
30 | |
20 | |
19 | |
13 | |
13 |
User | Count |
---|---|
29 | |
20 | |
19 | |
18 | |
16 |