Azure AD logins

Steve Ashman 21

We had an on-prem AD which synced users to Azure AD.

Trying to login into AzureAD but the user is shown as local\user rather than azure\user.

Any users that have been created in Azure show correctly.

How can I get old on-prem users to show as Azure users?

James Hamil 24,666 Reputation points Microsoft Employee

2022-02-18T22:03:53.587+00:00

Hi, we are investigating your issue and will update you shortly.

Best,
James
Steve Ashman 21 Reputation points

2022-02-19T17:44:12.72+00:00

Thank you,
Kind regards
Steve
James Hamil 24,666 Reputation points Microsoft Employee

2022-02-22T22:00:40.597+00:00

Hi @Steve Ashman , sorry for the delay. Are you using AD Connect Sync? Is the user signing in using the domain email or a different identity provider?
Steve Ashman 21 Reputation points

2022-02-23T15:37:34.6+00:00

No problem James

The users were originally AD Connect sync from local ad/domain to Azure ad/domain. The AD Connect sync has been turned off.

Local machine is joined to Azure AD and using domain email to login.

Users who were created by AD Connect Sync show as local-domain\user whereas users created in Azure Portal show as AzureAD\user.

Hope this helps

Steve
Bob Johnson 1 Reputation point

2022-02-24T03:04:42.477+00:00

@Steve Ashman - which user attribute are you seeing is different between the synced and new users? This sounds like a UserPrincipalName but the display format you reference is different. It would be helpful to clarify where you are seeing the AzureAD\user displayed.
Steve Ashman 21 Reputation points

2022-02-24T09:25:01.033+00:00

Hi Bob

The only attribute that I can see that is different is that "Password Never Expires" is ticked for users that were synced to Azure - there may be more but I can't see them.

UPN is the same in both cases - email address.

I first noticed it on the RMM software that I use, but can also see it in cmd > whoami, and also the C:\Users where the folder is called username whereas first 20 characters of the display name (minus the spaces)

Thanks

Steve
Bob Johnson 1 Reputation point

2022-02-24T16:51:47.877+00:00

Looks like this was an issue a few years ago - https://github.com/MicrosoftDocs/azure-docs/issues/38048#issuecomment-528570435. It was a product gap back then but I'm not sure if it has been fixed.
Steve Ashman 21 Reputation points

2022-03-02T09:24:17.207+00:00

Hi Bob

Thanks for looking into this and the information you have provided.

Kind regards

Steve

Accepted answer

James Hamil 24,666 Reputation points Microsoft Employee

2022-02-24T21:06:27.55+00:00

Hi @Steve Ashman , my colleague Bob did some digging and found that this is a known product gap, and unfortunately has been for a while. I've reopened the issue here and will reach out to the appropriate channels to bring it to their attention.

"Even though you have migrated the user from AD to Azure AD, the onprem SamAccountName is still intact on the user object, among other on-prem AD attributes. As a result, Azure AD picks those details and shows domain/user instead of AzureAD/user. This attribute cannot be modified or cleared through Graph APIs at this point, so there's no way to change the behavior"

I suggest submitting a new UserVoice feature request here so we can track the issue better. I'm really sorry about this! If I find a solution or learn of any updates I will post back here and let you know.

If you wouldn't mind, please mark this answer as "Verified" so other users may reference it.

Thank you,
James
Please sign in to rate this answer.

1 person found this answer helpful.
Steve Ashman 21 Reputation points

2022-03-02T09:25:41.497+00:00

Hi James

Thanks for the info.

There is no Verified option so I have accepted the answer instead.

Kind regards

Steve
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure AD logins

0 additional answers

Your answer