When you’re using B2B (Entra ID guest) authentication, row‑level filtering in Power Pages does work, but only if the Contact record is correctly linked to the signed‑in user. The behaviour you’re seeing — everything disappearing when you switch from Global Access to Contact‑based permissions — usually means the relationship between the logged‑in user and the Contact table isn’t set up the way Power Pages expects.
Here are the key things to check:
1. The B2B user must be mapped to a Contact record
Power Pages authorisation is always based on Contact, even if authentication is via Entra ID. Make sure:
-
The user has a Contact record
-
The Contact record has the Azure AD B2B user’s Object ID stored in the adx_identityprovider fields
-
The Contact is marked as External and Enabled for portal login
If the mapping is missing, the user will authenticate successfully but will have no Dataverse permissions, which results in empty lists.
2. Your table permissions must use the correct relationship
For row‑level filtering, the Table Permission should be:
Make sure the relationship selected in the permission matches the actual Dataverse relationship name, not just the display name.
3. The Web Role must include the Table Permission
Check that:
If the user has no Web Role, they will see nothing.
4. B2B users work fine — External ID is not required
You do not need Microsoft Entra External ID for row‑level filtering.
B2B guest users work perfectly as long as:
-
They authenticate via Entra ID
-
They map to a Contact
-
The Contact has a Web Role
-
The Web Role has the correct Table Permissions
So your setup is supported — something is just missing in the mapping or permissions.
Most common cause
The most frequent issue is:
The B2B user logs in successfully, but the Contact record is not linked to their Entra ID identity.
When that happens, Power Pages treats them as an authenticated user with no permissions, so all lists appear empty.
