Forum Discussion

edwardrmiles's avatar
edwardrmiles
Icon for Helper III rankHelper III
10 years ago

How do you avoid exposing data that's sensitive when personally identifiable?

I'm interested to hear any approaches I can use to avoid exposing data that's sensitive when personally identifiable but analytically interesting when aggregated   It's easy enough to remove or mas...
Need Help
Tutorial Requests
v-haibl-msft's avatar
v-haibl-msft
Icon for Microsoft Employee rankMicrosoft Employee
10 years ago

edwardrmiles

 

I think you can also try to use Row-level security (RLS). Just give a simple sample as below.

Assuming we have a similar table like below. We can create a calculated column to get the role count in one department.

RoleCount_Per_Depart = 
CALCULATE ( COUNTROWS ( Table1 ), ALLEXCEPT ( Table1, Table1[Department] ) )

 

Then we can create a non-admin role which can only see the data that belong to those departments which have more than 1 employee.

 

After publish to PBI Service, we can configure RLS to include ordinary employee into the Non-Admin group. Then employees in this group will not be able to see the data that belong to those departments which have only 1 employee.

 

Best Regards,

Herbert