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 connections 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 syncs this attribute to locate if a user is migrated or not and by this determine which connection to use.

Requirements

  • Connect service accounts for both On-prem and Exchange Online
  • Install AADFS
  • Insert identification code for Exchange On-prem connection to default and remote for Exchange Online connection
  • Contact AskCody to enable multi-connection setup

How it works 

AskCody Active Directory Forwarding Service supports sending attribute information (msExchRecipientTypeDetails) to AskCody and based on this marking if the user is migrated or not. The connection attribute on the synced 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 connection 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. 

Alternative method

Info

This method should only be used when fulfilling all of the following criteria:

  • You are currently migrating from Exchange On-Prem to Exchange Online
  • You are currently not using AADFS*
  • You will be migrating users in batches, and your migration will happen during an extended period of time
*If you are using AADFS, the user migration will be handled automatically, as long as you follow the requirements listed here.

In some cases, organizations perform migrations from Exchange On-Prem to Exchange Online in batches, which can make the migration process last for a long period of time. In order to make sure that all the users (both migrated, and non-migrated) have access to AskCody during the migration period, please follow these steps:

  1. Create a new connection in the AskCody Management Portal using Exchange Online (click here to learn how). Make sure to keep both the On-Prem, and Online connection during the whole migration period to prevent users from losing access to the platform.
  2. Migrate a user from Exchange On-Prem to Exchange Online.
  3. In the AskCody Management Portal, find that user's profile and click on the blue "edit" button found at the right end corner of the Users table.
  4. Please click on "Advanced configuration" to display advanced user features.
    Advanced configuration on user profile
  5. Please make sure that the following option is enabled:
    User Migrated to Exchange Online

By performing these steps, the system will be able to determine which connection (Exchange on-prem, or Online) to authenticate the user, providing access at all times during the migration period.

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 connection. In this way, you only keep the connections that you are currently using. To perform this, please go to the Admin Center in the AskCody Management Portal, and in the "Connections" section, find the on-prem connection, click on the blue "Edit" button located at its right end, and click on "Delete". If the connection 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.