Power Pages

existing users prompted for a invitation code: changes in the system accounts?

(0) Share

Report

Posted on by Jerome P1

Hi,

in the past week we got message from our customers that they can't login on our power apps portal site.

they are prompted for an invitation code while they are already registered for many months now.

after some investigation I found that the system account used to access the dataverse tables has changed

from SYSTEM to "# Portals-name of the portal"

and the problem appear to be related to the adx_externalidentity records created when the SYSTEM account was used.

like if the new account "# Portals-name of the portal" is not able to read these records, not able to find the associated contact for the user and prompt him for a new invitation code.

so I just duplicate all the exiting records from the adx_externalidentity which were created be the SYSTEM account and the users are now able to connect properly.

is anybody else suffering this issue?

at least I have a work around, but is there another way to solve this?

Categories:

Security

All responses (3)

Answers (0)

Sort by

TS-19080709-0 3 on at

Like
a
(0)

Report
Copy link

Link copied!

We faced the same issue in one of our environments today, after some digging, we found that the application user did not have the right roles. After applying the role, the users were able to login.
Suggested answer

11manish 5,664 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
The issue is caused by a change in the portal runtime user (# Portals-<site>) not having access to existing adx_externalidentity records created under SYSTEM.

Your workaround works, but the correct fix is:

Grant proper table permissions to the portal user

Or reassign ownership of existing records instead of duplicating them
Suggested answer

M Bilal Khan 1,155 on at

Like
a
(0)

Report
Copy link

Link copied!
@Jerome P1,
I’ve seen this kind of issue when the ownership/context of the Power Pages system records changes.

The fact that existing users start getting the invitation-code prompt, while duplicating the adx_externalidentity records under the new portal account fixes the issue, strongly suggests that Power Pages is no longer able to read/resolve the existing external identity records.

I would check the following before continuing with the duplication workaround:

Check the owner of the affected adx_externalidentity records and compare it with newly created records.

Review the Dataverse security roles/permissions for the portal application/system user that is now accessing the records.

Check whether any changes were made to table permissions, ownership, or access teams around the time the problem started.

Compare an affected user's adx_externalidentity record with one created after the issue appeared.

Verify that the external identity still points to the correct Contact and authentication provider.

I would also avoid bulk-duplicating adx_externalidentity records as a permanent solution. Those are system-managed Power Pages records, and creating duplicate identities can potentially leave stale or duplicate associations behind.

The change from SYSTEM to # Portals-<site> is particularly interesting. If that change happened without any intentional configuration change, I'd check the Power Pages service/update history and consider opening a Microsoft support case with a couple of affected adx_externalidentity records.

A useful test is to take one affected user and one newly created user and compare:

External Identity → Contact → Authentication Provider → Owner → Created By/Modified By

If the only meaningful difference is the owner/security context, you've probably found the root cause rather than needing to recreate the identities.