> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/file-connectors/sharepoint/sharepoint-microsoft-entra-authentication.md).

# SharePoint - Microsoft Entra Authentication

This article outlines the process for creating and configuring a Microsoft Entra application registration to obtain the authentication credentials required for establishing a connection with the SharePoint connector. The generated Client ID, Tenant ID, and Client Secret are required to validate and configure the SharePoint connector within the OvalEdge application.

The SharePoint connector uses Microsoft Entra authentication and requires a properly configured application registration with the necessary API permissions and administrative consent.

## Prerequisites

Before proceeding with the application setup, ensure the following requirements are met:

<table><thead><tr><th width="200.33331298828125">Prerequisite</th><th>Description</th></tr></thead><tbody><tr><td>Microsoft Entra Access</td><td>Access to the Microsoft Entra admin center with permission to create application registrations.</td></tr><tr><td>Azure Portal Access</td><td>Access to the Azure portal for application registration and credential management.</td></tr><tr><td>Administrative Access</td><td>Permission to grant Microsoft Graph API permissions and admin consent.</td></tr></tbody></table>

{% hint style="warning" %}
Administrative approval is required to grant Microsoft Graph permissions and consent before the generated credentials can be used for connector authentication.
{% endhint %}

## Create an Application Registration

### Step 1: Access Microsoft Entra Admin Center

1. Sign in to the **Microsoft Entra admin center** using the following URL: <https://portal.azure.com/auth/login/>
2. Navigate to **App Registrations**.

   <img src="/files/xNaGiOyuMnHPjppOTw8D" alt="" height="345" width="624">

### Step 2: Create a New Application Registration

1. Click **New Registration**.

   <img src="/files/oO7xtWVd8ldSRgHhoo6E" alt="" height="325" width="624">
2. Enter a name for the application.
3. Click **Register**.

   <img src="/files/Ar1aJMakKV4mtcdqHpOG" alt="" height="359" width="624">

### Step 3: Open the App Registration

1. Navigate to **App Registrations**.
2. Click **All Applications**.
3. Search for the newly created application.
4. Open the application registration.

   <img src="/files/HdvehZuc3wERmYv9AU7q" alt="" height="329" width="624">

## Retrieve Authentication Credentials

### Retrieve Client ID and Tenant ID

1. Navigate to the **Overview** page of the application registration.
2. In the Essentials section, copy the following values:

| Credential | Azure Field             |
| ---------- | ----------------------- |
| Client ID  | Application (Client) ID |
| Tenant ID  | Directory (Tenant) ID   |

<img src="/files/lNGd3rjHAzMwN9WO5740" alt="" height="365" width="624">

### Create a Client Secret

1. Navigate to **Certificates & Secrets**.

   <img src="/files/JNSAJGxjlVzv78Y6Shg9" alt="" height="329" width="624">
2. Click **New Client Secret**.

   <img src="/files/WJIrYpy8K1kzwCFbc13v" alt="" height="331" width="624">
3. Enter a **description**.
4. Select the required **expiration period**.
5. Click **Add**.

   <img src="/files/XnhjFv1v85kpFQgKdiZJ" alt="" height="359" width="624">

### Retrieve Client Secret

1. Copy the Value immediately after the **client secret** is created.

   <img src="/files/jMfHoyYTFzsvYPq8xTeR" alt="" height="331" width="624">

{% hint style="warning" %}
The Client Secret value is displayed only once during creation. Ensure that the value is copied and stored securely before leaving the page.
{% endhint %}

## Configure API Permissions

### Step 1: Add Microsoft Graph Permissions

1. Navigate to **API Permissions**.
2. Click **Add a Permission**.

   <img src="/files/6uQk8VXJraILAz3LMpR5" alt="" height="340" width="624">
3. Select **Microsoft Graph**.

   <img src="/files/QYnl9HPoBviSbA2Lc1Lx" alt="" height="363" width="624">
4. Select **Application Permissions**.

   <img src="/files/Qh8fItmILo7Gi9TFbjUY" alt="" height="361" width="624">
5. Search for **Sites.Read.All**.
6. Select the **Sites.Read.All** permission.
7. Click **Add Permissions**.

   <img src="/files/VAZHxNesU3TgoQwNRr5d" alt="" height="349" width="624">

### Step 2: Grant Administrative Consent&#x20;

1. Click **Grant Admin Consent**.

   <img src="/files/viHRd5uinF91V8CdpaLt" alt="" height="359" width="624">
2. Click **Yes** to confirm.

   <img src="/files/8HpcecYhAADiP1efbqAM" alt="" height="357" width="624">

{% hint style="warning" %}
Administrative consent must be granted before the SharePoint connector can access SharePoint metadata.
{% endhint %}

## Credentials Required for Connector Configuration&#x20;

The following values are required when configuring the SharePoint connector in OvalEdge:

| Credential    | Description                                               |
| ------------- | --------------------------------------------------------- |
| Client ID     | Application (Client) ID from the application registration |
| Tenant ID     | Directory (Tenant) ID from the application registration   |
| Client Secret | Secret value generated for the application registration   |

{% hint style="info" %}
**Disclaimer**

This document is provided for reference purposes only and is subject to change in the future. For the latest information, contact the System Administrator of the system.
{% endhint %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/file-connectors/sharepoint/sharepoint-microsoft-entra-authentication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.