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

Transitioning from a Microsoft Exchange Server to Exchange Online in AskCody

This article explains how to move your AskCody environment from Microsoft Exchange Server to Exchange Online, where AskCody connects through Microsoft Graph.

This guide is written for the IT Admin in an organization moving from an on-premises Microsoft Exchange Server to a Microsoft Exchange Online tenant. When your organization makes that move, your AskCody environment moves with it, and three things change:

  • Integration method: from an EWS service account to Microsoft Graph with admin consent.
  • Exchange Calendars: each calendar connected to AskCody is repointed from the Exchange Server integration to the Microsoft Graph integration.
  • User and host management: from the Active Directory Server Integration (ADSI) to Microsoft Entra ID (former Azure AD) with SCIM App Provisioning.

The steps below describe the general procedure.

Note: If your organization migrates to Exchange Online in stages, you will run Exchange Server and Exchange Online side by side for a period. That is a hybrid setup, and both integrations can run in AskCody at the same time. Read How to handle Hybrid Exchange Setups.

Step 1: Make sure your Users and Resources are migrated to Exchange Online

Before changing anything in AskCody, make sure the mailboxes are in place in Exchange Online: at least all Users and Resources that are currently synchronized to AskCody and that you want to continue working with on the platform.

Step 2: Establish the Microsoft Graph integration to Exchange Online

For Exchange Online, AskCody connects through Microsoft Graph. Your Microsoft 365 administrator grants consent to the AskCody enterprise application once, and no service account, password, or EWS URL is stored or shared with AskCody.

  1. If the integration has not been established yet, follow Integrating Microsoft Exchange with AskCody. When adding the integration, choose Microsoft Exchange Online (MS Graph).

Note: If you already have an Exchange Online integration running on EWS with Basic or Modern Authentication, do not reuse it as the target. Upgrade it to Microsoft Graph first by following How to upgrade your Exchange Online integration to Microsoft Graph. Microsoft retired EWS in Exchange Online as of October 1, 2026, so the Microsoft Graph integration is the destination for this transition.

Step 3: Connect each Exchange Calendar to the Microsoft Graph integration

Each calendar currently connected through your Exchange Server integration needs to be moved to the new integration.

  1. In the AskCody Management Portal, click on the Admin Center in the left panel.
  2. Click Integrations and choose MS Exchange Calendars.


    A screenshot of the Microsoft Exchange Calendars list in the AskCody Management Portal
  3. Under the Actions column, click Edit to open the settings for the individual Exchange Calendar.
  4. Find the option that says Microsoft Exchange Integration* and choose the Microsoft Graph integration you created in step 2.

    A screenshot of the Microsoft Exchange Integration type when editing a Microsoft Exchange Calendar in the AskCody Management Portal
  5. Accept the Terms* and press Update.
  6. Repeat this process for the remaining calendars.

If you need to add completely new resources, see Adding Microsoft Exchange Calendars to the AskCody Portal.

Step 4: Set up user and host management with Microsoft Entra ID

With your organization in Exchange Online, user and host management moves from the Active Directory Server Integration (ADSI) to Microsoft Entra ID using SCIM App Provisioning. Follow Integrate Microsoft Entra ID with AskCody (using app provisioning) to set it up.

Note: The Active Directory Server Integration (ADSI) may be known to you by its former title: AskCody Active Directory Forwarding Service (AADFS).

Step 5: Stop the Active Directory Server Integration and clean up

Caution: Do not run the Active Directory Server Integration and App Provisioning at the same time. Two active sources of user management can overwrite each other's changes.

  1. Stop the Active Directory Server Integration (ADSI).
  2. Start provisioning users through your new Microsoft Entra ID App Provisioning setup.
  3. Contact AskCody Support, sharing a compressed copy (.zip) of the State Folder, so AskCody can:
    • Delete the ADSI (AADFS) from your account.
    • Clean up any Users or Hosts that may be stuck between the two integrations.

You can find the State Folder at this path on the server running the service: %USERPROFILE%\AppData\Roaming\AskCody\ActiveDirectory\ForwardingService\State

Next step: Once every calendar is moved and user provisioning runs through Microsoft Entra ID, your Exchange Server integration is no longer in use and can be removed from the Admin Center. If you are unsure whether everything has been moved, contact AskCody Support before deleting it.