ixp
latest
false
UiPath logo, featuring letters U and I in white

Communications Mining user guide

Last updated Mar 13, 2026

Migration Guide: Exchange Web Services (EWS) to Microsoft Graph API

Overview

Microsoft is deprecating the Exchange Web Services (EWS) API, with full disablement scheduled for October 2026.

You must migrate all Exchange integrations that currently use EWS to the Microsoft Graph API to make sure that these continue to function.

Prerequisites

Before you start the migration, make sure you meet the following requirements:

  • Azure Portal access: Administrative access to the Azure portal of your organization.
  • Permissions: The ability to register applications and grant admin consent in Azure AD.
  • Integration access: Administrative access to your Communications Mining integrations.
  • Mailbox information: List of all mailboxes currently connected via EWS integrations.

Migration process

Step 1: Identify your current EWS integrations

  1. Log into Communications Mining through IXP in Automation Cloud.
  2. Navigate to Settings, then to the Integrations tab.
  3. Document all existing Exchange integrations, including:
    • Integration names
    • Connected mailboxes
    • Associated projects

Step 2: Register an Azure application

If you have not already created an Azure application for Graph API access, apply the following steps:

2.1 Create the application registration
  1. Sign into your Azure portal.

  2. Navigate to App Registrations and select New Registration.

    App registrations

  3. Configure the application as follows:

    • Name: Use a descriptive name, for example, uipath-exchange-graph-integration.
    • Supported account types: Select Accounts in this organizational directory only (Single tenant).
  4. Select Register.

  5. Note down the following values from the application overview page:

    • Application (client) ID
    • Directory (tenant) ID
2.2 Create a client secret
  1. In your application, select Certificates & secrets from the left menu.

  2. Under Client secrets, select New client secret.

    new client secret

  3. This opens the Add a client secret sidepanel. Configure the secret:

    • Description: Enter a meaningful description, for example, Exchange Graph Integration Secret.
    • Expires: Select an expiration period. The recommended option is 12 or 24 months.
  4. Select Add.

  5. Immediately copy the secret Value and store it securely.

    client secrets

Note:

Azure displays the secret value only once. If you lose it, you must create a new secret.

2.3 Set API permissions for Microsoft Graph
  1. Select API permissions from the left menu.

  2. Select Add a permission.

    add a permission

  3. Select Microsoft Graph under the Microsoft APIs tab.

    The image shows the options under the Microsoft APIs tab, with a highlight on the Microsoft Graph.

  4. Select Application permissions.

    The image shows the permission options of Microsoft Graph highlighting the Application permissions option.

  5. Expand Mail and select Mail.Read.

    The image shows the page for selecting a permission, highlighting the Mail.Read permission.

  6. Select Add permissions.

  7. Select Add a permission again, then select Microsoft GraphApplication permissions.

  8. Expand MailboxSettings and select MailboxFolder.Read.All.

The image shows the page for selecting a permisson, highlighting the MailboxFolder.Read.All permission.

  1. Select Add permissions.

  2. Returning to the API permissions menu, select Grant admin consent for [Your Organization].

  3. Select Yes in the confirmation dialog.

    admin consent

Your configured permissions should show:

  • Mail.Read (Application) — green checkmark under Status.
  • MailboxFolder.Read.All (Application) — green checkmark under Status.

For enhanced security, limit the application to access only the required mailboxes. Make sure you follow the Microsoft guide: Limiting application permissions to specific Exchange Online mailboxes.

Before updating your production integrations, test the new Graph API credentials in a separate test integration first.

  1. Go to Communications Mining in IXP in Automation Cloud.
  2. Navigate to SettingsIntegrations tab.
  3. Select New integration.
  4. Configure the test integration:
    • Select a test project.
    • Enter a clear test name, for example, Exchange Graph Test or [Production Name] - Test.
  5. Fill in the credentials from Step 2:
    • OAuth Authority: https://login.microsoftonline.com/{tenant_id}
    • OAuth Client ID: Your Application (client) ID.
    • Client Secret: Your client secret value.
    • Authentication Method: Select With application access.
    • API Version: Select Microsoft Graph.
  6. Select Validate and save credentials.
  7. Add the mailboxes used in your production integration. Use a recent start timestamp to limit the amount of data synced initially.
  8. Select Create Integration.
  9. Wait 15–30 minutes for the first sync to complete, then verify that emails are syncing successfully and that no error messages appear on the integration status page.

Once confirmed, proceed to update your production integrations.

Step 4: Back up your current EWS configuration

Before modifying your production integration, record your current EWS credentials and connection details. This allows you to revert if needed, as credential changes cannot be undone within the platform.

Step 5: Update your production integration

Info:

If you need to revert, edit the integration and switch the credentials back to your EWS details.

  1. Go to Communications Mining in IXP in Automation Cloud.

  2. Navigate to Settings, then to the Integrations tab.

  3. Locate the production integration you want to migrate and open its settings.

  4. Select the Credentials tab, then select Change Credentials.

  5. Update the following fields:

    • OAuth Authority: https://login.microsoftonline.com/{tenant_id} — replace {tenant_id} with your Azure Directory (tenant) ID.
    • OAuth Client ID: Your Application (client) ID.
    • Client Secret: Your client secret value.
    • Authentication Method: Select With application access.
    • API Version: Select Microsoft Graph.
  6. Select Validate and save credentials to verify your configuration.

    Note:

    If validation fails, double-check your tenant ID, client ID, and client secret. Ensure admin consent was granted for the API permissions.

  7. Select Save or Continue to apply the updated configuration.

  8. Monitor the integration for at least one hour to confirm stable operation and successful email sync.

Step 6: Update remaining integrations

Repeat Steps 3–5 for each remaining EWS integration in your organization.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated