Blog Post

Azure Data Explorer Blog
2 MIN READ

Row Level Security (RLS) - get more control over your data

slavikn's avatar
slavikn
Icon for Microsoft rankMicrosoft
Mar 01, 2020
We are excited to announce a new Azure Data Explorer (Kusto) feature: Row Level Security (RLS) policy, which gives you fine control over who can access data inside your tables. You can now prevent sp...
Updated Sep 29, 2020
Version 6.0
jamesbdarcy's avatar
jamesbdarcy
Copper Contributor
Sep 29, 2020

Hi Itay

 

Thanks for your reply.

 

Can you explain the 'not easy' way to do what I am looking? A table full of users is not out of the question.

 

SSO is not an option for embedded PBI users.

 

If I could pass a parameter (a user id for example) from the PBI java script embedded environment through to the ADX Kusto query then I would.  However, to the best of my knowledge there is no way to update PBI data-source query parameters from the java script environment. To be as clear as possible, I know that you can update slicers and filters via the java script API and update filters via the URL parameters of the embed URL but neither of these mechanisms seem to allow the updating of data-source query parameters that would be sent through to the kusto query. I would imagine that this is probably not implemented due to data security concerns. 

 

Make sure you have a look at https://docs.microsoft.com/en-us/power-bi/developer/embedded/embedded-row-level-security to see where I'm coming from. Note especially how Analysis services uses a method CUSTOMDATA() to access a value passed to it from the token created via EffectiveIdentity.CustomData property. I am imagining that would be the way in which ADX (kusto) would somehow access a value to perform row level filtering.

 

JBD