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

How to Migrate from AADI or ADSI to SCIM-Based App Provisioning

Learn how to migrate from legacy user sync services to the latest version

This guide is designed for customers currently using ADSI (Active Directory Server Integration, or AADFS) or AADI (AskCody Active Directory Integration) to manage user synchronization.
The goal is to help you migrate to the new App Provisioning (SCIM-based) integration using Microsoft Entra ID.

SCIM-based App Provisioning is only supported for environments using Exchange Online.
It does not support hybrid environments, where some user mailboxes remain on on-premises Exchange Servers.

Permission Requirements

To set up and run App Provisioning, you need the following permissions in Microsoft Entra ID and AskCody:

In Microsoft Entra ID

  • Global Administrator permissions are required to:

    • Register and configure the AskCody Enterprise Application

    • Approve required API permissions (for SCIM and Graph access)

    • Start the provisioning service

In AskCody

  • AskCody Administrator access is required to:

    • Access the Admin Center

    • Navigate to Integrations → Entra ID Integration

    • Complete the migration and approve authentication flows

The migration process is very similar for both AADI and ADSI users.
The main difference is that ADSI customers must stop the ADSI service running on their Exchange Server before starting the setup.

Contents of this guide

Step 1 - Create and Configure the Enterprise Application

Start by setting up the Enterprise Application in Microsoft Entra ID.
This creates the connection that allows AskCody to automatically manage users and groups through SCIM. 

To create the application, follow this guide. However, it is important to not start the provisioning service until after step 4 of this guide, as it may slow the first sync cycle down.

Step 2 - ADSI(AADFS)-Specific Step

If your organization is currently using ADSI, there’s one extra step before you proceed:

  1. Stop the ADSI service from your Exchange Server.
    This ensures there’s no overlap or conflict between the legacy ADSI sync and the new SCIM-based provisioning.

  2. Once stopped, continue following the same Entra ID setup guide linked above (click here to go directly to it)

Do not restart the ADSI service after migration. The SCIM integration fully replaces it. After having successfully migrated to the SCIM-managed user synchronization, it is safe to uninstall the AADFS (AADI) service from your organization's Exchange Environment.

Step 3 - Migrate from AADI to App Provisioning

If you’re currently using AADI, the process is nearly identical, but you should not start the provisioning service from Entra ID yet.

Once you’ve completed the Enterprise Application setup:

  1. Log in to your AskCody Admin Center

  2. Navigate to Integrations → Entra ID Integration. You should see the following page:

    Screenshot 2025-10-06 at 10.01.13

  3. Click Upgrade to App Provisioning

  4. In the confirmation flow, choose “Copy existing Entra ID groups and their access rights” if you want to reuse your existing group and access configurations (if you will give users the same level of access as you have been giving them until today).

    image-Oct-06-2025-09-42-39-2187-AM

  5. Click Upgrade to continue

  6. Approve the authentication flow, which must be accepted by a Global Administrator in Exchange

After completing these steps, you’ll be redirected to a Groups table in AskCody.
Initially, the table may appear empty. That’s expected. Make sure to refresh the page after a few minutes, as your existing groups will start appearing.

Step 4 - Wait for Groups to Populate

Check back after about 5 minutes to see the synchronization progress.

  • If you see a warning banner, the migration is still running.

  • When the banner disappears and all groups are listed, the migration is ready for provisioning.

The time required depends on the number of groups in your organization. Large environments may take slightly longer to complete.

Step 5 - Start the Provisioning Service from Entra ID

Now it’s time to start the new provisioning process in Entra ID:

  1. Open Microsoft Entra ID

  2. Go to Enterprise Applications

  3. Locate the application created for AskCody

  4. Click Start provisioning

The provisioning service will now begin matching users and groups with AskCody and run its first full synchronization cycle.

The first sync takes longer because it performs a complete match between users, groups, and roles.
Future incremental syncs will run much faster.

Step 6 - Verify the Migration

You can monitor the status of each group directly in the AskCody Admin Center.
Each group will display whether it’s:

  • Active: The group is up to date

  • Applying Changes: Your organization has recently made changes to the access configuration of the group, and these are being applied to the users within that group

  • Pending Entra ID Changes: Your organization has made changes to the group's memberships in Entra ID, and these are currently being processed and updated into AskCody

This allows you to confirm that synchronization is working as expected.