Insights / RLS in Power BI / Part 4
Part 4 of 20 · Share itPower BI RLS for guest users and #EXT# UPNs
The problem. Your investor's email is in the security table. They open the report and see nothing.
Why. For a B2B guest, USERPRINCIPALNAME() usually returns the email they were invited with. In some tenants it returns the long form:
name_partner.com#EXT#@yourtenant.onmicrosoft.com
If that's what comes back, your security row doesn't match, and RLS filters out everything. "Test as role" won't show you this, because it runs as you, not as the guest.
The fix.
- Put a small card on a test page that shows what Power BI sees:
UPN Check = USERPRINCIPALNAME()
- Ask the guest what the card says. Store that exact value in the security table.
- If a guest gets access through a security group, test with that guest. If their rows don't show, add them to the role directly by email.
- Test with a real guest account before go-live, every time.
Check before go-live
- Guest rows in the security table match what the UPN card shows for that guest Desktop
- Guests who get access through a group were tested, or added to the role directly
- A real guest has opened the report and seen the right rows
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.