Forum Discussion
RLS not wokring In OneLake security
if you're using OneLake security directly, then yeah, defining access roles like eastregion makes sense.
the reason I mentioned USERPRINCIPALNAME() is mostly for cases where RLS is applied via views or SQL logic, not just OneLake-level security. sometimes the identity resolution behaves differently depending on how the access is evaluated—especially if you're mixing workspace roles with SQL-based filters.
but if you're managing it all through OneLake access control and it's working as expected, then you're probably good đź‘Ť just make sure the role assignments are syncing properly and the column names match exactly in your views or queries.
let us know how it goes
Hi Viswanadh0110 ,
We would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
|
Please don't forget to give a "Kudos " – I’d truly appreciate it! |
Regards,
B Manikanteswara Reddy