Insights / RLS in Power BI / Part 16
Part 16 of 20 · Test itDoes Copilot respect RLS in Power BI?
Yes. Copilot queries your model as the signed-in user, so their RLS role filters every answer.
The catch: Copilot follows your RLS exactly as it is, gaps included.
A sales manager asks Copilot for last year's targets. No report page ever showed the Targets table. But if that table isn't on the RLS filter path (Part 2), Copilot can answer with the whole company's targets. Report pages hide tables; Copilot can still find them.
Three places to check:
- Tables RLS doesn't reach. Put every table on the filter path, or block it with
FALSE(). - Admin, Member and Contributor. RLS doesn't apply to them, so Copilot answers from all the data. Give report users Viewer access.
- Fabric data agents on a lakehouse or warehouse. An agent on a semantic model uses the model's RLS. An agent on the lakehouse uses the lakehouse's security, not the model's. Secure the source too, with OneLake security or SQL RLS.
Before you turn Copilot on: sign in as a Viewer, and ask Copilot for data they shouldn't see. They should get nothing.
Check before go-live
- Every table is on the filter path or blocked Desktop
- Report users are Viewers Service
- Lakehouses and warehouses used by data agents are secured at the source
- A Viewer asked Copilot for data they shouldn't see, and got nothing
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.