{"id":21450,"date":"2023-09-05T04:28:05","date_gmt":"2023-09-05T04:28:05","guid":{"rendered":"https:\/\/www.insentragroup.com\/nz\/?p=21450"},"modified":"2023-09-05T04:28:06","modified_gmt":"2023-09-05T04:28:06","slug":"how-to-match-an-exo-mailbox-to-an-ad-user-object","status":"publish","type":"post","link":"https:\/\/www.insentragroup.com\/nz\/insights\/geek-speak\/secure-workplace\/how-to-match-an-exo-mailbox-to-an-ad-user-object\/","title":{"rendered":"How to Match an Exo Mailbox to an Ad User Object"},"content":{"rendered":"\n

During a recent Tenant-To-Tenant (let\u2019s call it \u201cT-to-T\u201d shall we!) migration project, the source environment we were presented with had no on-premises Exchange infrastructure, while the target environment had an Exchange hybrid configuration in place. The source mailboxes had already been provisioned in the target Exchange Online (EXO) environment, but we had an issue emailing these users due to the configuration of mail hygiene solution. <\/p>\n\n\n\n

To resolve the issue we needed to link the EXO mailboxes to their on-premises AD User object. The users were already matched from an identity perspective using Azure AD Connect, but their Exchange attributes needed to be matched too. <\/p>\n\n\n\n

To do this we needed to get the EXO GUID for each user and inject it into the on-premises AD user object attributes. I have listed the solution below which will hopefully help you too!<\/p>\n\n\n\n

Solution<\/h2>\n\n\n\n

To implement this solution you need to be an Exchange Administrator on M365 and on-premises Exchange, and be comfortable with PowerShell. <\/p>\n\n\n\n

The first requirement is to get the ExchangeGuid from the user\u2019s EXO mailbox using PowerShell <\/p>\n\n\n\n