Forum Discussion
Harry Dubois
Oct 06, 2016Brass Contributor
No mailalias in Exchange after sync with Azure Connector
I have a problem with creating mailaliasses. We have two domains: the primary domain / mailaddress from the user is (example) testdoc@corderius.org. The second domainname is testdoc@corderius.nl. I h...
Harry Dubois
Oct 06, 2016Brass Contributor
I used this resource: http://serverfault.com/questions/546127/adding-alias-to-an-office-365-mailbox-with-dirsync.
Victor_Ungureanu
Microsoft
Oct 06, 2016Try to force a delta sync. A delta sync only from the AAD connector is not importing the changes from the AD into the metaverse.
https://blogs.technet.microsoft.com/nawar/2016/02/25/forcing-synchronization-with-azure-ad-connect-1-1-aad-connect-1-1/
To force a delta sync:
Import-Module ADSync
followed by
Start-ADSyncSyncCycle -PolicyType Delta
https://blogs.technet.microsoft.com/nawar/2016/02/25/forcing-synchronization-with-azure-ad-connect-1-1-aad-connect-1-1/
To force a delta sync:
Import-Module ADSync
followed by
Start-ADSyncSyncCycle -PolicyType Delta
- Harry DuboisOct 07, 2016Brass ContributorI have done this, but no success.. Opened a ticket.
- Victor_UngureanuOct 07, 2016
Microsoft
Do you have this issue only for one test user or for multiple users? If it's only for one user, you should try with another one.
When syncing users from onpremises, they are synced by AAD Sync to Azure AD and from there there is another sync process that has to happen between Azure AD and Exchange Online. There is a chance that the failure accurs at this stage. You could check in the O365 Admin center (https://portal.office.com/adminportal/home#/users) to see if the respective user has all the addresses there.