Insights / RLS in Power BI / Part 9
Part 9 of 20 · Build itSSO vs fixed identity: what it does to RLS
The problem. Someone changes a model's connection to fix a refresh error. Next morning, restricted users can see salary and national ID.
Why. Your model reaches the data as an identity. There are two options:
- SSO: each user's own identity reaches the source, so security at the source (OneLake security, SQL RLS, CLS) can tell users apart.
- Fixed identity: one identity reaches the source for everyone. The source can't tell users apart, so per-user security has to live in the model (RLS and OLS).
The trap: switching from SSO to a fixed identity is a reasonable fix for a connection problem. But if that identity has broad access, every user suddenly gets what that identity can see. Nothing at the source changed. The identity reaching it did.
The fix.
- Decide on purpose where per-user security lives: at the source (needs SSO) or in the model (works with a fixed identity).
- A fixed identity is a valid design: stable refresh, and users don't need access to the source. Then RLS and OLS in the model must cover everything.
- Don't change the connection identity on a model you don't own. Treat it as a security change, not a settings tweak.
Check before go-live
- You know which identity each model uses to reach its source
- If it's a fixed identity, the model's RLS and OLS cover every sensitive row and column
- Changing a connection identity goes through the data owner
Want a second pair of eyes on your own model? The RLS review checks your roles, relationships and workspace access against this checklist, at a fixed price.