Forum Discussion
Directlake Row Level Security
steveplatz2 Current Workarounds
To avoid the error:Combine all RLS logic into a single role, or
Refactor the model to avoid N:N security filtering when multiple roles must be allowed, or
Use Import or DirectQuery mode, which do support merging RLS roles.
please mark this solution. Thanks
This is actually expected behavior with Direct Lake right now.
Even though the same RLS setup works in an Import model, Direct Lake handles security differently. At the moment, it cannot combine multiple RLS roles when one of them filters through a many-to-many relationship or uses SecurityFilteringBehavior = Both.
That’s why you’re seeing the error message about the user belonging to multiple roles.
So this isn’t a bug in your model—it's simply a Direct Lake limitation today. Hopefully Microsoft enables full multi-role RLS support in the future.
Thank you for the reply. I assume there is no workaround for this limitation today? Any chance you know if correcting this is something that's on their roadmap?
steveplatz2 Current Workarounds
To avoid the error:Combine all RLS logic into a single role, or
Refactor the model to avoid N:N security filtering when multiple roles must be allowed, or
Use Import or DirectQuery mode, which do support merging RLS roles.
please mark this solution. Thanks