# SharePoint

This article outlines the integration with the SharePoint connector, enabling streamlined metadata management through features such as crawling, data preview, and manual lineage building. It also ensures secure authentication via Credential Manager.

<figure><img src="/files/7T7hBj3jfL5MnpzUi4Q8" alt=""><figcaption></figcaption></figure>

## **Overview**

### **Connector Details**

<table data-header-hidden><thead><tr><th width="421.5"></th><th></th></tr></thead><tbody><tr><td>Connector Category</td><td>File Connectors</td></tr><tr><td>OvalEdge Release Supported</td><td>Release6.x and later</td></tr><tr><td><p>Connectivity</p><p>[How the connection is established with SharePoint]</p></td><td>REST APIs</td></tr><tr><td>Verified SharePoint Version</td><td>SharePoint 2013</td></tr></tbody></table>

{% hint style="info" %}
The SharePoint connector has been validated with the mentioned "Verified SharePoint Versions" and is expected to be compatible with other supported SharePoint versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

### **Connector Features**

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Profiling                                    |       ❌      |
| Sample Profiling                             |       ✅      |
| Query Sheet                                  |      NA      |
| Data Preview                                 |       ✅      |
| Auto Lineage                                 |      NA      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ✅      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

{% hint style="info" %}
NA' indicates that the respective feature is 'Not Applicable.'
{% endhint %}

### Metadata Mapping

The following objects are crawled from SharePoint and mapped to the corresponding UI assets.

<table><thead><tr><th width="177.75">SharePoint Object</th><th width="187">SharePoint Property</th><th width="178">OvalEdge Attribute</th><th width="170.5">OvalEdge Type</th><th width="176.75">OvalEdge Category</th></tr></thead><tbody><tr><td>Folder</td><td>Folder</td><td>Folder</td><td>Folder</td><td>Folder</td></tr><tr><td>File</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>XLSX</td><td>File</td><td>File</td><td>XLSX</td><td>File</td></tr><tr><td>XLS</td><td>File</td><td>File</td><td>XLS</td><td>File</td></tr><tr><td>CSV</td><td>File</td><td>File</td><td>CSV</td><td>File</td></tr><tr><td>TXT</td><td>File</td><td>File</td><td>TXT</td><td>File</td></tr><tr><td>PARQUET</td><td>File</td><td>File</td><td>PARQUET</td><td>File</td></tr><tr><td>ORC</td><td>File</td><td>File</td><td>ORC</td><td>File</td></tr><tr><td>JSON</td><td>File</td><td>File</td><td>JSON</td><td>File</td></tr><tr><td>YAML</td><td>File</td><td>File</td><td>YAML</td><td>File</td></tr><tr><td>PIP</td><td>File</td><td>File</td><td>PIP</td><td>File</td></tr></tbody></table>

### Set up a Connection

#### Prerequisites

The following are the prerequisites to establish a connection.

Ensure that the CSV files follow the required formatting standards for proper data processing and visibility. Refer to [CSV Format Requirements](https://docs.ovaledge.com/connectors/additional-requirements/csv-format-requirements-for-file-connectors)**.**

**Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
👨‍💻Who can provide these permissions? These permissions are typically granted by the SharePoint administrator, as users may not have the required access to assign them independently.
{% endhint %}

| Objects              | Permission Level        | Access Permission |
| -------------------- | ----------------------- | ----------------- |
| Connector Validation | Application Permissions | Site.Read.All     |
| Sites                | Application Permissions | Site.Read.All     |
| Lineage (Manual)     | Application Permissions | Site.Read.All     |
| Buckets              | Application Permissions | Site.Read.All     |
| Folder               | Application Permissions | Site.Read.All     |
| Files                | Application Permissions | Site.Read.All     |

### Connection Configuration Steps

{% hint style="warning" %}
Users are required to have the Connector Creator role in order to configure a new connection.
{% endhint %}

1. Log into **OvalEdge**, go to **Administration > Connectors**, click **+ (New Connector)**, search for **SharePoint**, and complete the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="220.25">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "SharePoint" is displayed as the selected connector type.</td></tr><tr><td>Authentication*</td><td><p>The following authentication are supported for SharePoint:</p><ul><li>Online</li><li>On-Premise-Basic</li><li>On-Premise-Kerberos</li></ul></td></tr></tbody></table>

{% tabs %}
{% tab title="Online" %}

<table><thead><tr><th width="191.5">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Version*</td><td><p>Select version from the drop down menu.</p><ul><li>SharePoint</li><li>Graph</li></ul></td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selected option.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul></td></tr><tr><td>License Add Ons</td><td>Select the checkbox for Data Quality Add-On to identify data quality issues using data anomaly detection.</td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the SharePoint connection              </p><p>(Example: "SharePointdb").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.</td></tr><tr><td>Connector Description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Share point Url*</td><td>Enter the URL or address of the SharePoint site.</td></tr><tr><td>Site*</td><td>Enter the site (URL path) within the SharePoint tenant.</td></tr><tr><td>Client Id*</td><td>Enter the Client ID assigned to the application.</td></tr><tr><td>Client Secret*</td><td>Enter the Client Secret associated with the Client ID for authentication.</td></tr><tr><td>Tenant Id*</td><td>Enter the unique tenant identifier for the SharePoint.<br><strong>Note</strong>: This field is available only when the version is selected as "Graph".</td></tr><tr><td>Sharepoint Path</td><td>Enter the URL path or address to the SharePoint site.<br><strong>Note</strong>: This field is available only when the version is selected as "Graph".</td></tr><tr><td>Title</td><td>Enter the title name for the connector.<br><strong>Note</strong>: This field is available only when the version is selected as "SharePoint".</td></tr><tr><td>App Domain</td><td>Enter the domain name where the client application is hosted.<br><strong>Note</strong>: This field is available only when the version is selected as "SharePoint".</td></tr><tr><td>Redirect URI</td><td>Enter the redirect URI configured in the App registration for authentication.<br><strong>Note</strong>: This field is available only when the version is selected as "SharePoint".</td></tr><tr><td>Proxy Enabled*</td><td>Select <strong>Yes</strong> to route API calls through a proxy server. Select <strong>No</strong> to bypass the proxy and connect directly.</td></tr></tbody></table>
{% endtab %}

{% tab title="On-Premise-Basic" %}

<table><thead><tr><th width="191.5">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selected option.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul></td></tr><tr><td>License Add Ons</td><td>Select the checkbox for Data Quality Add-On to identify data quality issues using data anomaly detection.</td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the SharePoint connection              </p><p>(Example: "SharePointdb").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.</td></tr><tr><td>Connector Description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Share point Url*</td><td>Enter the URL or address of the SharePoint site.</td></tr><tr><td>Site*</td><td>Enter the URL path or address of the SharePoint site.</td></tr><tr><td>Username*</td><td>Enter the username authorized to access the SharePoint site.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified username for authentication.</td></tr></tbody></table>
{% endtab %}

{% tab title="On-Premise-Kerberos" %}

<table><thead><tr><th width="191.5">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selected option.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul></td></tr><tr><td>License Add Ons</td><td>Select the checkbox for Data Quality Add-On to identify data quality issues using data anomaly detection.</td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the SharePoint connection              </p><p>(Example: "SharePointdb").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.</td></tr><tr><td>Connector Description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Share point Url*</td><td>Enter the URL or address of the SharePoint site.</td></tr><tr><td>Site*</td><td>Enter the URL path or address of the SharePoint site.</td></tr><tr><td>Username*</td><td>Enter the username authorized to access the SharePoint site.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified username for authentication.</td></tr><tr><td>Domain</td><td>Enter the domain name associated with the Sharepoint site.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td><p>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured</p><p>in the security settings are available for selection.</p></td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl

{% hint style="warning" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

1. Navigate to the **Connectors** page and click **Crawl/Profile.**
2. This action initiates the metadata collection process from the data source and loads the retrieved metadata into the **File Manager > File Explorer.**
3. In the File Manager, click the connector name, select the specific **folder(s) or file(s)**, then click **Catalog /** **Catalog and Profile** from the **Nine Dots** menu. For more details, click [here](https://docs.ovaledge.com/file-manager/file-explorer).
4. The selected files or folders will be added to the **Data Catalog > Files/File Columns** tab.

{% hint style="info" %}
Only file columns are fetched into the system after file profiling is performed.
{% endhint %}

#### Other Operations

The **Connectors** page provides a centralized view of all configured connectors, along with their health status.

**Managing connectors includes:**

* **Connectors Health:** Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including databases, tables, columns, and codes.

**Nine Dots Menu Options:**

To view, edit, validate, configure, or delete connectors, click on the **Nine Dots** menu.

* **Edit Connector:** Update and revalidate the data source.
* **Validate Connector**: Check the connection's integrity.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings:** Manage term associations at the connector level.
* **Delete Connector:** Remove a connector with confirmation.

## Limitations

<table><thead><tr><th width="91.2728271484375">Sl. No.</th><th>Description</th></tr></thead><tbody><tr><td>1.</td><td>Full profiling is not supported for the SharePoint connector. Profiling operations performed on files support sample-based profiling only.</td></tr></tbody></table>

## Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table><thead><tr><th width="100.81817626953125">S. No.</th><th width="213.90911865234375">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Error while validating connection: Graph API validation failed / Site ID or Drive ID lookup failed</td><td><p><strong>Error Description:</strong> Validation fails due to incorrect site path, invalid hostname format, or insufficient permissions.</p><p><strong>Resolution:</strong></p><ul><li>Ensure hostname does not include protocol or trailing slashes.</li><li>Verify site path format (e.g., <code>/sites/{siteName}</code> or root).</li><li>Confirm <strong>Site.Read.All</strong> permissions with admin consent.</li><li>Validate site accessibility with the provided credentials.</li></ul></td></tr><tr><td>2</td><td>Error while validating connection: Authentication failed / Unable to acquire access token</td><td><p><strong>Error Description:</strong> Authentication failure due to invalid credentials, incorrect tenant details, or missing permissions.</p><p><strong>Resolution:</strong></p><ul><li>Verify Client ID, Client Secret, and Tenant ID.</li><li>Ensure required API permissions are granted.</li><li>Confirm admin consent is provided.</li><li>Check for expired or inactive credentials.</li></ul></td></tr><tr><td>3</td><td>Could not discover SharePoint tenant/resource information</td><td><p><strong>Error Description:</strong> Tenant discovery fails due to incorrect URL, network issues, or missing authentication response.</p><p><strong>Resolution:</strong></p><ul><li>Verify SharePoint URL and site path.</li><li>Ensure network connectivity to the SharePoint server.- Validate endpoint accessibility.</li><li>Review logs for request failures.</li></ul></td></tr><tr><td>4</td><td>Validation failed for ACS / On-Premise connection</td><td><p><strong>Error Description:</strong> Failure due to incorrect credentials, token issues, or misconfigured site path.</p><p><strong>Resolution:</strong></p><ul><li>Verify username and password are correct and active.</li><li>Validate site URL and structure.</li><li>Ensure token generation is successful (if applicable).</li><li>Check authentication configuration.</li></ul></td></tr><tr><td>5</td><td>File or folder access fails due to invalid path</td><td><p><strong>Error Description:</strong> Path-related issues caused by incorrect formatting or improper encoding.</p><p><strong>Resolution:</strong></p><ul><li>Ensure paths are properly formatted and encoded.</li><li>Remove unnecessary leading or trailing slashes.- Verify the file or folder exists.</li><li>Validate the path structure.</li></ul></td></tr><tr><td>6</td><td>File upload operation fails</td><td><p><strong>Error Description:</strong> Upload failures due to permission issues, invalid path, or file constraints.</p><p><strong>Resolution:</strong></p><ul><li>Verify write permissions on the target location.- Ensure the folder path exists.</li><li>Check file size and constraints.</li><li>Review system logs for failure details.</li></ul></td></tr><tr><td>7</td><td>Issues with special characters in file or folder names</td><td><p><strong>Error Description:</strong> Improper handling of special characters leads to path resolution failures.</p><p><strong>Resolution:</strong></p><ul><li>Use UTF-8 encoding for path values.</li><li>Ensure proper handling of special characters.</li><li>Validate encoded paths before execution.</li></ul></td></tr><tr><td>8</td><td>Kerberos authentication not working (On-Premise)</td><td><p><strong>Error Description:</strong> Authentication failure due to incomplete or incorrect Kerberos configuration.</p><p><strong>Resolution:</strong></p><ul><li>Configure SPNEGO/JAAS correctly.</li><li>Verify domain and network connectivity.</li><li>Ensure SPN is properly registered.</li><li>Synchronize system clocks.</li></ul></td></tr><tr><td>9</td><td>SSL certificate validation failure (On-Premise)</td><td><p><strong>Error Description:</strong> Connection fails due to invalid, expired, or untrusted SSL certificates.</p><p><strong>Resolution:</strong></p><ul><li>Import the certificate into the truststore.</li><li>Verify certificate validity and hostname match.</li><li>Ensure proper SSL configuration.</li></ul></td></tr><tr><td>10</td><td>Access denied or insufficient permissions</td><td><p><strong>Error Description:</strong> User or application lacks required permissions to access resources.</p><p><strong>Resolution:</strong></p><ul><li>Grant required permissions.</li><li>Ensure admin consent is provided.</li><li>Verify access to relevant sites and files.</li><li>Revalidate after permission updates.</li></ul></td></tr><tr><td>11</td><td>Authentication fails during long-running operations</td><td><p><strong>Error Description:</strong> Failures occur due to token expiration or stale authentication sessions. <strong>Resolution:</strong></p><ul><li>Implement token refresh handling.</li><li>Validate token expiry before execution.</li><li>Re-authenticate when required.</li><li>Clear cached tokens if invalid.</li></ul></td></tr></tbody></table>

## FAQs

<details>

<summary>What is the difference between Graph API and ACS API?</summary>

Graph API is the modern Microsoft API designed for SharePoint Online with improved performance and scalability. ACS API is a legacy SharePoint REST API that supports both Online and On-Premise environments with different authentication mechanisms.

</details>

<details>

<summary>When should Graph API be used over ACS API?</summary>

Use Graph API for SharePoint Online environments with modern authentication. Use the ACS API for On-Premise SharePoint or when the Graph API is not supported.

</details>

<details>

<summary>Why is profiling not executed for the SharePoint connector?</summary>

The SharePoint connector supports only limited (sample-based) profiling. Full profiling is not supported due to connector limitations.

</details>

<details>

<summary>Does enabling DuckDB allow full profiling for SharePoint?</summary>

No. DuckDB functionality is not applicable to the SharePoint connector. Enabling **key: `enable.duckdb`** does not enable full profiling.

</details>

<details>

<summary>What permissions are required for the SharePoint connector?</summary>

The connector requires appropriate API permissions such as **Site.Read.All** along with admin consent. Access to the relevant sites, folders, and files must also be ensured.

</details>

<details>

<summary>Why is access denied even after granting permissions?</summary>

This may occur if admin consent is not provided, permissions are not yet propagated, or incorrect tenant/application details are used.

</details>

<details>

<summary>How to verify if Graph API permissions are configured correctly?</summary>

Verify the application registration in the Azure Portal, ensure required permissions are added, and confirm that admin consent is granted.

</details>

<details>

<summary>What causes authentication failures in the SharePoint connector?</summary>

Common causes include invalid credentials, incorrect tenant or client details, expired secrets, or misconfigured authentication settings.

</details>

<details>

<summary>Why are files or folders not accessible during operations?</summary>

This can occur due to incorrect path format, missing permissions, or invalid encoding of special characters in file or folder names.

</details>

<details>

<summary>Does the SharePoint connector support full profiling for all file types?</summary>

No. The connector does not support full profiling for files; only limited profiling capabilities are available.

</details>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions: 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:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/file-connectors/sharepoint.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.