Power Pages: Testing External User Registration, Authentication and Account Linking
Diesen Beitrag auf Deutsch lesen
A testing guide for Power Pages external users: verify Contact association, unique emails, web roles and table permissions, plus negative tests that expose over-broad access.
TL;DR
A Power Pages site that signs in external users through Microsoft Entra External ID must be tested beyond login: confirm the identity links to the intended Dataverse Contact, no duplicate Contact is created, unique Contact emails are enforced, web roles and table permissions scope case access per Contact or Account, and denied-access scenarios are exercised.
Original by Softchief, on Softchief Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Test registration, repeat sign-in and account linking in a dev environment with three identities, record Contact IDs and verify no duplicate Contact is created.
- Admins/CoE: Enforce unique Contact emails, since duplicates including inactive records can block authentication, and keep external user testing out of production.
- Security/Compliance: Treat email matching as insufficient proof of identity, prefer invitation-based registration and validate Account-scoped permissions to stop cross-organisation record exposure.
Frequently asked questions
Why does Power Pages block sign-in when two contacts share the same email address?
Power Pages requires unique Contact email addresses, and duplicates, even on inactive records, can prevent authentication. Keep test and portal contact data free of duplicate emails.
How do I associate an external identity with an existing Dataverse Contact in Power Pages?
Use the contact-mapping-with-email setting in Microsoft Entra External ID or an invitation flow, then verify the Contact ID after sign-in. Email matching alone is never sufficient proof of identity.
How do I test that one Power Pages customer cannot see another customer's cases?
Sign in as both test customers and as an anonymous visitor, then confirm table permissions with Contact scope deny the other customer's records. Test the denied paths, not just the success path.