How do I synchronize my Azure Active Directory objects to Office 365?




  • Avatar
    Nick Lloyd

    Unlike most BitTitan documentation I didn't find this article at all clear. To clear the GUID attribute you need to edit the connector in ADConnect as per this blog post.  If, like me, you synchronised with AD Connect before removing the GUID attribute  you won't be able to create mailboxes in 365, it's designed to use the Microsoft migration tools. I ad to change the OU that was being synced to an empty to delete the existing accounts and then remove them from the Recycle Bin via PowerShell.  I was then able to re-add the accounts by changing back to the original OU and this time they didn't take the ExchGUID with them. This didn't go smoothly though and the GUID attribute added itself back on at some point and I had to repeat this process.

  • Avatar
    Rob Latino

    Hi Nick Lloyd,

    We're aware of the challenges with this process and we're working to update this article and a few others related to this. As soon as they're updated, we'll let you know. We appreciate your feedback and thank you for sharing your workaround with us.

  • Avatar
    Systems Admin

    Is this only applicable if the user at some point had an on-premise mailbox?  The majority of my users don't have this attribute poplulated and my assumption is that their mailbox was created and has always been in exchange online.  The users that do have this attribute populated migrated from on premise exchange to the cloud.  

  • Avatar
    Wayne Plotkin

    This article here helped me fix this problem since I had already sync my users to O365 and assigned the licenses.  After following this article and then running the below power shell commands all my mailboxes populated.


    I had to run this command before I was able to delete the Connector Space:  Set-ADSyncScheduler -SyncCycleEnabled $false

    After deleting it I ran this to reschedule the sync:  Set-ADSyncScheduler -SyncCycleEnabled $true

    This one is noted in the article and I ran it last:  Start-ADSyncSyncCycle -PolicyType Initial

Please sign in to leave a comment.