---
title: "Microsoft Teams Connector Setup Guide"
slug: "ms-teams-connector-setup-guide"
tags: ["MS Teams", "Office 365", "Connector"]
updated: 2025-07-18T11:33:04Z
published: 2025-07-18T11:33:04Z
canonical: "docs.revealdata.com/ms-teams-connector-setup-guide"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Teams Connector Setup Guide

## Overview

Reveal Hold supports integration with MS Teams for in-place preservation and data collection. This document describes the prerequisites for integrating Reveal Hold with MS Teams.

> [!NOTE]
> **Note**
> 
> All recent changes announced by Microsoft to the Purview eDiscovery experience—specifically, the unification of eDiscovery (Standard) and eDiscovery (Premium) under a single interface—do not impact the preservation capabilities of Reveal Hold. Reveal Hold operates independently of the Microsoft Purview user interface. Regardless of any change in interface announced by the Microsoft to the Purview eDiscovery experience, our preservation workflows remain fully functional and enforceable. Clients can continue to rely on Reveal Hold for issuing legal holds, tracking custodial compliance, and ensuring defensible preservation across Microsoft 365 and other supported data sources.
> 
> 
> 
> For further information or support, please contact your account representative or visit our support portal.

## Information Required for Integration

The following details are required from the client for configuring MS Teams connector in Reveal Hold.

1. Service account username and password which has been assigned the following roles:
  1. eDiscovery Manager
2. Client ID and Tenant ID of the registered application in Azure.
3. Client secret generated for the application.

The below sections describe the steps to be carried out in MS Teams for integration with Reveal Hold.

### Create a Service Account in Office 365

1. To create a new Office 365 user, go to Users >Active users in the[](https://admin.microsoft.com/Adminportal)Office 365 admin center and click on **Add a User**.

![Graphical user interface, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-rfyz94uo.png)

Figure: Add a user

1. Click on **Next.** In Product license select ‘Create user without product license’

![Graphical user interface, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-zcuzs1hl.png)

Figure: Product licenses

1. Click on **Next.** In Optional settings select ‘User (No admin center access)

![Graphical user interface, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-818e0r40.jpg)

Figure: Optional Settings

1. Enter the details of the new user and click **Finish Adding**. The user will now appear in the list of active users.

![Graphical user interface, text, application, email Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-rmd5q70z.png)

Figure: Review and Finish

5. Navigate to https://compliance.microsoft.com/permissions. Select **Roles** under **‘Microsoft purview solutions’** and Click on ‘ediscovery manager’.

![Graphical user interface, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-i13if3tw.png)

Figure: Edit eDiscovery Manager

1. Click on ‘Edit’ of eDiscovery Manager.

![Graphical user interface, text, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-devirscm.png)

Figure: Edit eDiscovery Manager

1. Search for the service account to be added under eDiscovery Manager.

![Graphical user interface, text, application, email Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-yeuzp2tu.png)

Figure: Edit eDiscovery Manager

1. Choose the service account to add from the list and click **Add** to save.

![Graphical user interface, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-h5x1v2dl.png)

Figure: Add Service account

1. Service account added in eDiscovery Manager as below screenshot.

![Graphical user interface, text, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-6ndzz3bk.png)

Figure: Added Service Accounts to eDiscovery Manager

### Register Application in Azure

Registering an application establishes a trust relationship between the app and the Microsoft identity platform. The trust is unidirectional: the app trusts the Microsoft identity platform, and not the other way around.

Follow the steps given below to create the app registration:

1. Sign in to the Azure portal.
2. If access to multiple tenants is available, from the top menu, use the **Directory +** subscription filter to select the tenant in which the application is to be registered.
3. Search for and select Azure Active Directory.

![Graphical user interface, application Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-cf8g7dzc.png)

Figure: Microsoft Azure Services

1. Under **Manage**, select **App registrations > New registration**.

![Graphical user interface, text, application, email Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-qfkztisd.png)

Figure: New Registration

1. Enter a **Display Name** for the application. Users of the application might see the display name when they use the app, for example during sign-in. The display name can be changed at any time and multiple app registrations can share the same name. The app registration's automatically generated Application (client) ID, not its display name, uniquely identifies the app within the identity platform.

![Graphical user interface, text, application, email Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-ncguyr2z.png)

Figure: App Registration - Part 1

1. Specify **Accounts in this organizational directory only** can use the application. In some cases, it is known as Sign-in audience.
2. Do not enter **Redirect URI** (optional). The following section describes how to configure a redirect URI.
3. Select **Register** to complete the initial app registration.

![Graphical user interface, text, application, email Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-rborel00.png)

Figure: App Registration - Part 2

### Add a Redirect URI

A redirect URI is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication. In a production web application, for example, the redirect URI is often a public endpoint where the app is running.

![Graphical user interface, application, Teams Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-yoyjl2oa.png)

Figure: Redirect URI

### Mobile and Desktop Applications

1. Select one of the suggested redirects URIs. For desktop applications using embedded browsers, https://login.microsoftonline.com/common/oauth2/nativeclient needs to be checked.

![Graphical user interface, application, Teams Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-ebtqwoin.png)

1. Select **Configure** to complete the platform configuration.

### Add a Client Secret

The client secret is also known as an application password. It is a string value the app can use in place of a certificate to identify itself. The client secret is the easier of the two credential types to use.

To add a Client Secret, first select the application from App registrations in the Azure portal. Then follow the steps given below.

1. Select **Certificates & secrets**
2. Select **New client secret**
3. Add a **Description** and an **Expiry** for your client secret
4. Select **Add**

![Graphical user interface, text, application, Teams Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-wr5uhigt.png)

Figure: Certificates and Secrets

1. Record the secret's value for use in the **client application code**

This secret value is never displayed again after leaving this page.

### Add Permissions to Access Microsoft Graph

Configure delegated permission to Microsoft Graph to enable the client application to perform operations on behalf of the logged-in user such as reading their email or modifying their profile. By default, users of the client app are asked when they sign in, to consent to the delegated permissions configured for it.

To configure permissions,

1. Choose **API permissions** to view the options.
2. Select **Add a permission >** **Microsoft Graph**.

![Graphical user interface, application, email Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-cdyjj8n0.png)

Figure: Add Permission - Microsoft Graph

1. Select **Delegated permissions**. Microsoft Graph exposes many permissions, with the most commonly used shown at the top of the list.

![Graphical user interface, text, application, email Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-49eig7yo.png)

Figure: Delegated Permissions

1. Under **Select permissions**, select the following permissions and navigate to Application Permissions adjacent to Delegated permissions to Select Application permissions listed in below table.

| **API / Permissions name** | **Type** | **Description** | **Admin consent required** |
| --- | --- | --- | --- |
| Group.Read.All | Application | Read all groups | Yes |
| User.Read.All | Application | Read all users' full profiles | Yes |
| User.Read | Delegated | Sign in and read user profile | No |
| Sites.Read.All | Application | Read Items in All Site Collections | Yes |
| EDiscovery.ReadWrite.All | Delegated | Read and Write All eDiscovery objects | Yes |
| Directory.Read.All | Application | Read Directory Data | Yes |
| EDiscovery.Read.All | Delegated | Read Case, Custodian Data | Yes |

1. Click on ‘Grant admin Consent for domain’

![Graphical user interface, application, Teams Description automatically generated](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/ms-teams-connector-setup-guide-image-rrpoj8lc.png)

![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/image(24).png)

Figure: Configured Permissions