May 15 2020
- last edited on
Jul 24 2020
I've been looking at the AAD Signin Logs for a few things now and I'm finding an issue where sometime the Identity and UserPrincipalName fields contain a users ObjectID rather than their name or UPN. If I resolve the objectid it is an active user in my tenant. It appears that all the records that have this issue have an empty array for AuthenticationDetails. Is anyone else seeing this and how are you handling it for reports/dashboards? I'm being asked why I have GUIDs in my list of active users, I could filter our the records with object ID but don't want to do that if they reflect true user activity.
May 16 2020 12:43 AM - edited May 16 2020 01:13 AM
I found these in my tenant too, but they were all unsuccessful sign-ins associated with two unique error codes from the error code lookup page here:
16000 means "Either multiple user identities are available for the current request or selected account is not supported for the scenario."
In the case of the 50058 error, it means
"This means that a user is not signed in. This is a common error that's expected when a user is unauthenticated and has not yet signed in. If this error is encountered in an SSO context where the user has previously signed in, this means that the SSO session was either not found or invalid. This error may be returned to the application if prompt=none is specified."
about 20 seconds later from the same IP Address the same user signed in successfully with their normal user ID.
So in our case, we are going to filter these out, especially because the 16000 error code "remediation suggestion" is to "Hide in logs" per the error lookup tool.