Skip to content
Submit support ticket
  • There are no suggestions because the search field is empty.

How to handle Hybrid Exchange Setups

This article explains how to connect AskCody when your organization runs both Exchange Server on-premises and Exchange Online

In a hybrid Exchange setup, some mailboxes and resource calendars live in Exchange Online and some on your on-premises Exchange Server. AskCody supports this by running two integrations side by side: a Microsoft Graph integration for Exchange Online and an EWS integration for the on-premises server. This article is written for the IT Admin managing the setup.

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 ADSI (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

  • A Microsoft 365 Global Administrator to grant consent for the Microsoft Graph integration. See Integrating Microsoft Exchange with AskCody.
  • A service account on the on-premises Exchange Server with the ApplicationImpersonation role, for the EWS integration. See Create a service account using PowerShell.
  • An overview of which resource calendars live where. Every calendar you add to AskCody must be connected through the integration that matches where its mailbox lives.

How to set it up

  1. Set up the Microsoft Graph integration for Exchange Online, following Integrating Microsoft Exchange with AskCody.
  2. Set up the EWS integration for your on-premises Exchange Server, using the service account and your EWS URL.
  3. Install ADSI (Active Directory Server Integration)
  4. Insert identification code for Exchange On-prem integration to default and remote for Exchange Online integration
  5. Contact AskCody support to enable multi-integration setup
  6. When adding calendars, select the integration that matches where the mailbox lives: Microsoft Graph for Exchange Online mailboxes, EWS for on-premises mailboxes.

 

Note: When you migrate a mailbox from on-premises to Exchange Online, make sure to move its calendar to the Microsoft Graph integration in AskCody.


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 2019 on-prem to Exchange Online will require setting the Identification code default on the 2019 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". 

Tip

After performing the full migration, it is recommended to establish an automatic user synchronization between your organization's Entra ID, 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 Entra ID. Click here to learn how.

In hybrid scenarios, for on-prem users, platform access is determined by the configuration in ADSI, whereas users on Exchange Online, get their access determined by the configuration on the Entra ID integration.