Inconsistency in behaviour of userId property of Client Principal Object for custom authentication providers

[will-0]

This documentation states, for the userId property of the client principal object:

"An Azure Static Web Apps-specific unique identifier for the user. The value is unique on a per-app basis. For instance, the same user returns a different userId value on a different Static Web Apps resource. The value persists for the lifetime of a user. If you delete and add the same user back to the app, a new userId is generated."

However, when using a custom authentication provider, it appears that the userId being returned from /.auth/me is actually the objectId of the user in my Entra External ID tenant.

I cannot find any documentation for this behaviour. In this instance, this is actually preferable behaviour, but it would be reassuring to know that it's not liable to suddenly change down the line.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 89705f24-082e-d4e9-547c-1992db4470cb
• Version Independent ID: 5df6b7d0-7e8a-f6c5-ea28-289b9a0ca84e
• Content: Accessing user information in Azure Static Web Apps
• Content Source: articles/static-web-apps/user-information.md
• Service: static-web-apps
• GitHub Login: @craigshoemaker
• Microsoft Alias: cshoe

[TPavanBalaji]

@will-0 Thanks for your feedback! We will investigate and update as appropriate.

[craigshoemaker]

Thanks for your feedback and your contribution to Azure docs.

Feedback for this repository is moving away from GitHub to a system specific to the Microsoft Learn platform. Issues for this repository will soon be disabled, and additional comments from GitHub will no longer be possible. However, we are now tracking and triaging this issue in the new feedback system.

To learn more about our feedback systems please see Provide feedback for Microsoft Learn content.

please-close