How to handle Hybrid Exchange Setups

Migrating from Exchange Server to Exchange Online often results in hybrid scenarios ex. Migrating meeting rooms before users. Learn how AskCody supports those scenarios.

AskCody handles these scenarios by supporting multiple integrations and detecting the user Exchange location using information from Active Directory.

In a hybrid Exchange setup, Exchange maintains an attribute in Active Directory that indicates whether a user’s mailbox has been migrated. This attribute is called msExchRecipientTypeDetails

AskCody AADFS (Active Directory Server Integration) connects this attribute to locate if a user is migrated or not and by this determine which integration to use.

Requirements

  • Connect service accounts for both On-prem and Exchange Online
  • Install AADFS (Active Directory Server Integration)
  • Insert identification code for Exchange On-prem integration to default and remote for Exchange Online integration
  • Contact AskCody to enable multi-integration setup

How it works 

AskCody Active Directory Server Integration supports sending attribute information (msExchRecipientTypeDetails) to AskCody and based on this marking if the user is migrated or not. The connection attribute on the synchronized user will be set to remote if the user is migrated, otherwise, it will be set to default. These codes correspond to the Identification codes set on connections in AskCody Admin Center and will then cause the correct integration to be used.

Example

Migrating from exchange 2013 on-prem to Exchange Online will require setting the Identification code default on the 2013 on-prem service account connection and the remote identification code on the Exchange Online connection. 

 

After performing the migration and making sure that all of the resources are migrated to Exchange Online, it would be a best practice to delete the on-prem integration. In this way, you only keep the integrations that you are currently using. To perform this, please go to the Admin Center in the AskCody Portal, and in the "Integrations" section, find the on-prem integration, click on the blue "Edit" button located at its right end, and click on "Delete". If the integration is not in use, you are able to delete it.

Tip

After performing the full migration, it is recommended to establish an automatic user synchronization between your organization's Azure Active Directory, and AskCody. This will greatly decrease the time and effort used to manage and synchronize users and hosts (in the case of the Visitor Management module), as they would synchronize automatically from your organization's Azure Active Directory. Click here to learn how.