Insights / RLS in Power BI / Part 17
Part 17 of 20 · Deploy itRLS in deployment pipelines: Dev, Test, Prod
The problem. RLS works in Test. In Prod, the visuals are blank.
Why. Deployment pipelines move your roles, but not the people in them.
| Travels to the next stage | Stays behind |
|---|---|
| Role definitions and their DAX rules | Role members |
| Report pages and visuals | Workspace access |
| Data source settings and parameters | Data, including the security table |
| Credentials and refresh schedule |
So on the first deployment, Prod's roles have no members. Users who aren't in any role see no data.
Check in Prod after you deploy:
- Refresh the model. The security table only has rows after a refresh.
- Direct Lake models don't rebind to Prod on their own. On the SQL endpoint, add a data source rule once. On OneLake, check the model's lineage after every deployment and rebind if needed.
- Give report users Viewer access. Members and Contributors skip RLS.
The habit: add security groups as role members, once in each stage. Later deployments keep them, because anything that isn't copied stays as it was in the target stage.
Check before go-live
- Each stage's roles have their security groups
- Prod was refreshed after the first deployment
- Prod models read Prod data (check lineage)
- The same "Test as role" checks pass in Test and Prod Service
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.