USERPRINCIPALNAME used for personalisation but no security role
"USERPRINCIPALNAME used for personalisation but no security role" is one of the governance checks Auditabi runs on a Power BI semantic model. n measure(s) personalise the report with USERPRINCIPALNAME() while the model has no RLS. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Either add RLS driven by the same identity, or make it clear in the report that data is shared.
What is detected
n measure(s) personalise the report with USERPRINCIPALNAME() while the model has no RLS. The greeting is per user, the data is not — which is easy to misread as security.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Either add RLS driven by the same identity, or make it clear in the report that data is shared.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.