E-mail aliases don't seem to sync with Office 365 using Azure AD Connect

Question

I'm having a bit of trouble getting e-mail aliases to sync with Office 365 when using Azure AD Connect. I have managed to get all the on-premise AD accounts to sync with Office 365 but cannot for the life of me get the e-mail aliases added. I have read countless forums that say edit the "proxyaddresses" field for each AD user account with "SMTP:[email protected]" for the primary address and "smtp:[email protected]" which I can do, however when I run the resync aliases are simply not synced. I can confirm the aliases I'm trying to add are verified domains within Office 365. Has anybody experienced this before? I've added a UPN for one of the domain names as we were using domain.local previously, I have set each user to use the UPN using the IdFix Tool which again has all worked fine but still aliases don't seem to be syncing!?

Any assistance would be greatly appreciated.

Solution

You have to include those extra domains in your configuration for Azure AD Connect. Re-run the wizard and there should be a section in there to add more domains.

Comments

[Jonathan Baird]

Hi, thanks for your response. I can confirm I have added the domains as part of the initial setup wizard.

[Jonathan Baird]

Hi, thanks for your response. I can confirm that the 2 domain names in question do appear in accepted domains and are showing as "Authoritative". I have moved the user out of the OU, ran a sync and the moved the used to Deleted Users in Office 365, i then put the user back into the OU and created an additional test user and both users sync'd fine. The user sync seems fine it just seems it is not picking up the "proxyAddresses" attribute from my AD. We have added a UPN for the domain name which is picked up by the wizard so I am at a loss as to why the aliases are not synced! :(

[Jesus Shelby]

If you search in the Azure AD Sync are the proxy addresses present? If "no" I would suggest installing a new instance of the Azure AD sync tool as that means it's not importing the values at all. If they are there, then the problem could simply be with the Azure AD connector or something more on the Microsoft side (either way you will probably need to contact Microsoft to go further).