- 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
Exchange Integration with Azure Application Authentication
Introduction
This step-by-step guide will show you a popular method for creating a Microsoft Exchange application for Communications Mining™ in your Azure Cloud Platform. You will learn how to create an Application (client) with an ID and Client Secret, and find your existing Directory (tenant) ID. This will allow users to access Exchange mailbox integrations in Communications Mining.
Microsoft will retire Exchange Web Services (EWS) on October 1, 2026. It is recommended to follow the Exchange integration with Azure Application Authentication and Graph guide instead.
Why is a successful integration important?
Failure to create an Exchange-Communications Mining™ application in Azure can lead to permissions errors that prevent users from accessing their mailbox integrations. To gain the full benefits of Communications Mining, follow these steps and complete the process in its entirety.
The step-by-step integration process
-
Sign in with Azure.
Sign into your Azure Cloud Portal.
-
Register a new application for Communications Mining.
Access the App Registrations menu and select the New Registration option.
Register a new application:
- Enter an application name—for example
reinfer-exchange-integration. - Under Supported account types, select the single tenant option.
- Hit Register to complete the registration.
Azure will give you an Application (client) ID and a Directory (tenant)ID.
- Enter an application name—for example
-
Create a Client Secret for your Communications Mining application.
To keep your application secure, you must create a Client Secret to log into your application. First, select Certificates & Secrets under the Manage sidebar, then continue with the following steps:
- Select the Client secrets option if it's not already selected.
- Select New client secret.
- In the sidebar, add an easily recognizable description and select an expiry date—we recommend 12 months.
- Hit Add.
You've now created a Secret Value for your Communications Mining™ application.
Note:Azure will only display this Secret Value to you once, so make sure to copy it. If you ever lose your secret value, simply complete Step 3 again to create a new one.
-
Set API permissions
- Navigate to API permissions under the Manage sidebar.
- Select Add a permission
- Select APIs my organization uses.
- Search for and select "Office 365 Exchange Online".
- Select "Application Permissions".
- Select the option "full_access_as_app".
- Hit Add permissions.
- Back in the API permissions menu, hit Grant admin consent for Communications Mining.
- In the Grant admin consent confirmation pop-up, select Yes.
-
Restrict access to the mailbox with a conditional access policy.
At this point, you will likely want to limit the applications permissions so that it can only access certain mailboxes within your organisation. To learn how to do this, read Microsoft's article Limiting application permissions to specific Exchange Online mailboxes.
-
Sign into Communications Mining.
Sign into Communications Mining through UiPath® Automation Cloud as usual.
-
Create a new integration in Communications Mining.
- Navigate to the Integrations page using the gear icon.
- Select New Integration.
- Select an existing project and enter a name for your integration, and add a title if desired.
- Select Continue.
- Populate your oauth authority using the tenant ID generated in Step 2, in the following format:
https://login.microsoftonline.com/{tenant_id}. - Populate your client ID generated in Step 2.
- Populate your Client Secret generated in Step 3.
- Select the option With application access.
- Select Validate & Save Credentials to check that your credentials are valid.
- Select Continue.
- Select Add Mailbox to open the mailbox form.
- Enter the email address for which you wish to copy emails into Communications Mining.
- Select Add Mailbox again to save the mailbox.
- Select Create Integration.
Final steps
You have now successfully created an integration between Communications Mining™ and Microsoft Exchange through Azure. You can disable the integration using the toggle, as shown in the following image. To delete it, select the trash can icon.
You can also enable attachment syncing at mailbox level on an Exchange integration. The streams API then makes the attachments retrievable via an attachment reference. Check more about syncing attachments in the Attachments and Using Exchange Integrations pages.
If you have any questions or need assistance with the integration process, contact UiPath® support.