How to Implement Row Level Security with Azure Data Lake

[Anonymous]

Hello,

I'm not sure if this is the correct location for this question but I have struggled to find documentation anywhere on how exactly to set up RLS when connected to Azure Data Lake. Is the syntax used exactly the same as what's used in on-premises dataset PBI files?

For example, below would be an example of a role we have set up within our on-prem:

[EmployeeName] = LOOKUPVALUE('EmployeeTable'[EmployeeName], 'EmployeeTable'[EmailAddress], USERPRINCIPALNAME())

This RLS DAX code is what's used within our RLS for Azure but business users are stating that they're able to see everything, not data specific to them as intended.

Are there extra settings that need to be performed within the PBI service to ensure the security filtering is activated? Or anything else that needs to be done beforehand?

[GilbertQ]

Hi there

You have to ensure that your underlying dataset is able to correctly show data based on a logged in user.

As far as I am aware Azure Data Lake is not capable of doing this?

[Anonymous]

Hello,

Thank you for the response. This is what I can see, which shows me there must be some kind of RLS possible with Azure but it's not actively filtering the data based on the user's login. Lookin gat the syntax this would work in an on-premises PBI model, so I wanted to know what the difference is. The below is an example of an employee's RLS. 

[GilbertQ]

Is your example use Azure Analysis Services?