---
title: "SharePoint Connector Graph Prerequisites"
slug: "sharepoint-connector-graph-prerequisites"
updated: 2025-04-10T21:17:45Z
published: 2025-04-10T21:18:43Z
canonical: "docs.revealdata.com/sharepoint-connector-graph-prerequisites"
---

> ## 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.

# SharePoint Connector Graph Prerequisites

## Graph API Connector Prerequisites for SharePoint

### Overview

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

### Information Required for Integration

The following details are required for configuring O365 Office connector in Reveal.

1. Service account username and password which has been assigned the following roles:

> [!NOTE]
> Note:
> 
> Disable Multi factor Authentication for the service account.
  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 o365 Office for integration with Reveal.

### Create a Service Account in Office 365

1. To create a new Office 365 user, go to Users >Active users in the [Office 365 admin center](https://admin.microsoft.com/Adminportal) and click on **Add a User**.
2. Enter the details of the new user and click **Finish Adding**. The user will now appear in the list of active users.
3. Navigate to [Permissions - Security & Compliance (office.com)](https://protection.office.com/permissions). Select **eDiscovery Manager** and click on **Edit**.
4. Search for the service account to be added under eDiscovery Manager. Choose the service.

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

Figure: Edit eDiscovery Manager

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

Figure: Add 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.](https://portal.azure.com/)
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.

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

Figure: Microsoft Azure Services
4. Under **Manage**, select **App registrations > New registration**.

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

Figure: New Registration
5. 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.

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

Figure: App Registration - Part 1

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

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

### 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.

![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/sharepoint-connector-graph-prerequisites-image-gmi2ui5s.jpg)

Figure: Redirect URI

#### Mobile and Desktop Applications

1. Select one of the suggested redirect URIs. For desktop applications using embedded browsers, [https://login.microsoftonline.com/common/oauth2/nativeclient](https://login.microsoftonline.com/common/oauth2/nativeclient) needs to be checked.
2. 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.

1. To add a Client Secret, first select the application from App registrations in the Azure portal. Then follow the steps given below.
2. Select **Certificates & secrets.**
3. Select **New client secret**Add a **Description** and an **Expiry** for your client secret.
4. Select **Add..**
5. Record the secret's value for use in the **client application code.**

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

![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/sharepoint-connector-graph-prerequisites-image-al5tryjg.jpg)

Figure: Certificates and Secrets

### 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**.

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

Figure: Add Permission - Microsoft Graph
3. Select **Delegated permissions**. Microsoft Graph exposes many permissions, with the most commonly used shown at the top of the list.

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

Figure: Delegated Permissions
4. 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** |
| --- | --- | --- | --- |
| User.Read.All | Application | Read all users' full profiles | Yes |
| Sites.Read.All | Application | Read Items in All Site Collections | Yes |
| EDiscovery.ReadWrite.All | Delegated | Read and Write All eDiscovery objects | Yes |
| EDiscovery.Read.All | Delegated | Read Case, Custodian Data | Yes |

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

Figure: Configured Permissions