- Introduction
- Setting up your account
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields
- Labels (predictions, confidence levels, label hierarchy, and label sentiment)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Annotated and unannotated messages
- Extraction Fields
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Access control and administration
- Manage sources and datasets
- Understanding the data structure and permissions
- Creating or deleting a data source in the GUI
- Preparing data for .CSV upload
- Uploading a CSV file into a source
- Creating a dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amending dataset settings
- Deleting a message
- Deleting a dataset
- Exporting a dataset
- Using Exchange integrations
- Model training and maintenance
- Understanding labels, general fields, and metadata
- Label hierarchy and best practices
- Comparing analytics and automation use cases
- Turning your objectives into labels
- Overview of the model training process
- Generative Annotation
- Dastaset status
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Understanding data requirements
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and Recall
- How validation works
- Understanding and improving model performance
- Reasons for label low average precision
- Training using Check label and Missed label
- Training using Teach label (Refine)
- Training using Search (Refine)
- Understanding and increasing coverage
- Improving Balance and using Rebalance
- When to stop training your model
- Using general fields
- Generative extraction
- Using analytics and monitoring
- Automations and Communications Mining™
- Developer
- Uploading data
- Downloading data
- Exchange Integration with Azure service user
- Exchange Integration with Azure Application Authentication
- Exchange Integration with Azure Application Authentication and Graph
- Migration Guide: Exchange Web Services (EWS) to Microsoft Graph API
- Fetching data for Tableau with Python
- Elasticsearch integration
- General field extraction
- Self-hosted Exchange integration
- UiPath® Automation Framework
- UiPath® official activities
- How machines learn to understand words: a guide to embeddings in NLP
- Prompt-based learning with Transformers
- Efficient Transformers II: knowledge distillation & fine-tuning
- Efficient Transformers I: attention mechanisms
- Deep hierarchical unsupervised intent modelling: getting value without training data
- Fixing annotating bias with Communications Mining™
- Active learning: better ML models in less time
- It's all in the numbers - assessing model performance with metrics
- Why model validation is important
- Comparing Communications Mining™ and Google AutoML for conversational data intelligence
- Licensing
- FAQs and more

Communications Mining user guide
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
- Log into Communications Mining through IXP in Automation Cloud.
- Navigate to Settings, then to the Integrations tab.
- 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
-
Sign into your Azure portal.
-
Navigate to App Registrations and select New Registration.

-
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).
- Name: Use a descriptive name, for example,
-
Select Register.
-
Note down the following values from the application overview page:
- Application (client) ID
- Directory (tenant) ID
2.2 Create a client secret
-
In your application, select Certificates & secrets from the left menu.
-
Under Client secrets, select New client secret.

-
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.
- Description: Enter a meaningful description, for example,
-
Select Add.
-
Immediately copy the secret Value and store it securely.

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
-
Select API permissions from the left menu.
-
Select Add a permission.

-
Select Microsoft Graph under the Microsoft APIs tab.

-
Select Application permissions.

-
Expand Mail and select Mail.Read.

-
Select Add permissions.
-
Select Add a permission again, then select Microsoft Graph → Application permissions.
-
Expand MailboxSettings and select MailboxFolder.Read.All.

-
Select Add permissions.
-
Returning to the API permissions menu, select Grant admin consent for [Your Organization].
-
Select Yes in the confirmation dialog.

Your configured permissions should show:
Mail.Read(Application) — green checkmark under Status.MailboxFolder.Read.All(Application) — green checkmark under Status.
2.4 Restrict mailbox access (recommended)
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.
Step 3: Test your Graph API credentials (recommended)
Before updating your production integrations, test the new Graph API credentials in a separate test integration first.
- Go to Communications Mining in IXP in Automation Cloud.
- Navigate to Settings → Integrations tab.
- Select New integration.
- Configure the test integration:
- Select a test project.
- Enter a clear test name, for example,
Exchange Graph Testor[Production Name] - Test.
- 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.
- OAuth Authority:
- Select Validate and save credentials.
- Add the mailboxes used in your production integration. Use a recent start timestamp to limit the amount of data synced initially.
- Select Create Integration.
- 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
If you need to revert, edit the integration and switch the credentials back to your EWS details.
-
Go to Communications Mining in IXP in Automation Cloud.
-
Navigate to Settings, then to the Integrations tab.
-
Locate the production integration you want to migrate and open its settings.
-
Select the Credentials tab, then select Change Credentials.
-
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.
- OAuth Authority:
-
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.
-
Select Save or Continue to apply the updated configuration.
-
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.
- Overview
- Prerequisites
- Migration process
- Step 1: Identify your current EWS integrations
- Step 2: Register an Azure application
- Step 3: Test your Graph API credentials (recommended)
- Step 4: Back up your current EWS configuration
- Step 5: Update your production integration
- Step 6: Update remaining integrations