> 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/release7.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:
PrerequisiteDescription
Microsoft Entra AccessAccess to the Microsoft Entra admin center with permission to create application registrations.
Azure Portal AccessAccess to the Azure portal for application registration and credential management.
Administrative AccessPermission to grant Microsoft Graph API permissions and admin consent.
{% 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: 2. Navigate to **App Registrations**. ### Step 2: Create a New Application Registration 1. Click **New Registration**. 2. Enter a name for the application. 3. Click **Register**. ### 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. ## 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 | ### Create a Client Secret 1. Navigate to **Certificates & Secrets**. 2. Click **New Client Secret**. 3. Enter a **description**. 4. Select the required **expiration period**. 5. Click **Add**. ### Retrieve Client Secret 1. Copy the Value immediately after the **client secret** is created. {% 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**. 3. Select **Microsoft Graph**. 4. Select **Application Permissions**. 5. Search for **Sites.Read.All**. 6. Select the **Sites.Read.All** permission. 7. Click **Add Permissions**. ### Step 2: Grant Administrative Consent 1. Click **Grant Admin Consent**. 2. Click **Yes** to confirm. {% hint style="warning" %} Administrative consent must be granted before the SharePoint connector can access SharePoint metadata. {% endhint %} ## Credentials Required for Connector Configuration 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ovaledge.com/release7.2/connectors/connector-repositories/file-connectors/sharepoint/sharepoint-microsoft-entra-authentication.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.