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.
- 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.
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.
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*(Active Directory Server Integration)
- You will be migrating users in batches, and your migration will happen during an extended period of time
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:
- Create a new integration in the AskCody 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.
- Migrate a user from Exchange On-Prem to Exchange Online.
- In the AskCody Portal, find that user's profile and click on the blue "edit" button found at the right end corner of the Users table.
- Please click on "Advanced configuration" to display advanced user features.
- Please make sure that the following option is enabled:
By performing these steps, the system will be able to determine which integration (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 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.
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.