One user's email fields not synchronizing from AD to AAD

thas 101 Reputation points

We are having an issue with synchronizing from on-prem AD to AAD using Azure AD Connect for only one user. For only this one user, the email fields are not synchronizing. All of the other fields for that user are successfully synchronizing, and email fields are synchronizing for all other users.

I noticed this issue this morning and attempted to run the troubleshooter, which failed to start. At that point I noticed that we were on an old version of the Azure AD Connect ( I upgraded to the current version ( and had to move to a new server since our old one was Server 2012. The new version is now running on Server 2019.

I ran the troubleshooter on the new server and the results showed me that the On-Premises Active Directory and the AADConnect Database agreed and were both correct. However, the Azure AD values were not correct. There are no errors shown in the Sync Service Manager.

We made other changes to this user, such as "Manager", this morning and that change did sync to Azure. This user was created using our normal procedure back in July:

  1. Created the user in local AD and waited for it to be synced to Azure
  2. Entered the user's default email address in the Email field and edited the proxyAddresses to add an alias in local AD.

The changes made in step 2 never took affect, although other changes have taken affect. On the old server I verified the Metaverse Object Properties show that most of the fields were updated when the user account was created on 7/15/21 at 11:27am. The mail attribute shows as being last updated on 7/15/21 at 11:57am and the proxyAddresses attribute shows as being updated on 7/16/21 at 11:57am.

Any ideas on how to get this corrected would be greatly appreciated!

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,771 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. thas 101 Reputation points

    Thanks for your reply, @Vasil Michev . I figured out the issue this morning.

    For the user in question, we had entered a proxyAddress. Since his first name is Michael, we entered an alias using Mike. It seems that when adding an alias using proxyAddress, we have to enter all needed aliases, including the and the default email address using the all-caps SMTP: notation.

    Thanks again!

    1 person found this answer helpful.

  2. Vasil Michev 96,436 Reputation points MVP

    Are you sure there are no sync errors for that user? Other than that check the value of the alias/mailnickname attribute - most Exchange related sync rules will be ignored if it's empty.

    0 comments No comments