Forum Discussion
Restrict sharing of Power BI Data to limited users
In the Power BI admin center, we have enabled the setting:
"Restrict content with protected labels from being shared via link with everyone in your organization".
As expected, this prevents users from generating "People in your organization" sharing links for content protected with sensitivity labels.
We only have one sensitivity label with protection enabled. However, due to Power BI’s limitations with labels that include "Do Not Forward" or user-defined permissions, this label is not usable in Power BI.
Our Power BI team wants to restrict sensitive data from being shared org-wide and instead limit access to specific individuals. One idea was to create another sensitivity label with encryption that works with Power BI and use that to enforce the restriction. However, such a label would also affect other Microsoft 365 apps like Word, Excel, and Outlook — which we want to avoid.
I looked into using DLP, but MS documentation mentions below limitations, that makes me unsure if this will meet the requirement.
1. DLP either restricts access to the data owner or to the entire organization.
2. DLP rules apply to workspaces, not individual dashboards or reports.
My question:
Is there any way to restrict sharing of Power BI (or Fabric) content to specific users within the organization without changing our existing sensitivity label configurations or creating a new encryption-enabled label that could impact other apps?
2 Replies
One option is to create a second label with encryption and assign permissions to a group of users. Then, create a second sensitivity labelling policy and publish the new label to a subset of users who need to be able to apply the label to content. That way, the majority of users who are not in the policy will not see the new label in the Office apps
This is the only solution that comes to my mind as well at this point. However, I was exploring if there's an alternative that doesn't require changing the current label configuration. Thanks for the suggestion, Nikki.
