Connection to SharePoint

To connect a Microsoft SharePoint site to the DQC Platform, you register an application in Microsoft Entra ID, grant it read access to the target site, and configure the connector with the resulting credentials. Once connected, every visible SharePoint list on the site becomes available as a table for data quality checks.

Add a SharePoint connector

To begin:

Go to the Connectors > Data sources screen
Click the SharePoint tile
Enter the connection parameters described below and choose an authentication method

Required connection information

Field	Example	Description
Name	`Marketing SharePoint`	A custom name to identify this connector inside DQC
Tenant ID	`contoso.onmicrosoft.com`	Your Microsoft Entra ID tenant — either the verified domain (e.g. `contoso.onmicrosoft.com`) or the directory (tenant) GUID
Site URL	`https://contoso.sharepoint.com/sites/team1`	Full URL of the SharePoint site whose lists you want to connect. Use the root site URL (e.g. `https://contoso.sharepoint.com`) to access the tenant's root site
Client ID	`00000000-0000-0000-0000-000000000000`	Application (client) ID of the Entra ID app registration used to authenticate
Authentication method	`Client Secret`	Either Client Secret (a generated secret string) or Client Certificate (PEM-encoded private key plus thumbprint)

The Tenant ID and Site URL are bound to the data cache and cannot be changed after the connector has been created. To point the connector at a different site or tenant, create a new connector.

Choose an authentication method

DQC authenticates against Microsoft Graph using the OAuth 2.0 client credentials flow (app-only, no user sign-in). You can supply credentials either as a client secret or as a client certificate.

Option A — Client Secret

Paste the secret value generated under Certificates & secrets in the app registration. Make sure to record the value when it is created — Entra ID will hide it afterwards.

Option B — Client Certificate

Recommended for production. Provide:

Certificate (PEM) — the PEM-encoded private key including the -----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY----- markers
Certificate Thumbprint — the SHA-1 thumbprint of the certificate uploaded to the app registration

Microsoft Entra ID setup

Perform these steps once per tenant. You need the Application Administrator or Global Administrator role in Entra ID.

In the Azure portal, open Microsoft Entra ID > App registrations and create a new registration (e.g. DQC SharePoint Reader)
Copy the Application (client) ID and the Directory (tenant) ID — these become the Client ID and Tenant ID in DQC
Under Certificates & secrets, create either a client secret or upload a certificate (depending on the authentication method you chose above)
Under API permissions, add the Microsoft Graph application permission Sites.Selected (recommended) or Sites.Read.All, then click Grant admin consent
If you chose Sites.Selected, grant the app read access to the specific site using PowerShell or the Graph Explorer (see Microsoft's Sites.Selected documentation)

Required Microsoft Graph permissions

Permission	Type	Used for
`Sites.Selected` (recommended)	Application	Read access scoped to the specific site granted to the app
`Sites.Read.All`	Application	Read access to all sites in the tenant — use only if `Sites.Selected` is not feasible

What gets imported

Once connected, DQC discovers and imports SharePoint lists from the configured site. Each list becomes a separate table.

Custom and built-in lists are included
Document libraries are not imported
Hidden and system lists are skipped
Lookup, person and choice fields are flattened to their display value (e.g. Display Name, Title, or Email) — multi-value fields are joined with ;
Internal metadata fields starting with @ or _ are dropped

List items are cached locally in DuckDB on a per-connector basis to keep subsequent reads fast. The cache is refreshed automatically when DQC pulls fresh data.

Connect and assign permissions

After saving the connector, DQC validates the credentials, fetches the available lists and lets you pick which ones to expose as tables. To control who can use the connector inside DQC, see Data source access permissions.

Troubleshooting

When DQC cannot connect to SharePoint or load its tables, it shows the reason with a short fix and links to this section. Look up the beginning of the message:

Message in DQC	Likely cause	Fix
`Failed to acquire Graph token for SharePoint: … AADSTS7000215 …`	Wrong client secret; often the secret ID instead of its value	Copy the secret value from the app registration
`Failed to acquire Graph token for SharePoint: … AADSTS7000222 …`	The client secret expired	Create a new secret and enter it
`Failed to acquire Graph token for SharePoint: … AADSTS700016 …`	Wrong client ID, or the app is not registered in this tenant	Check client ID and tenant ID
`Failed to acquire Graph token for SharePoint: … AADSTS700027 …`	The certificate is not registered or the thumbprint does not match	Upload the public certificate to the app registration and check the thumbprint
`Failed to resolve SharePoint site '…': 401 …` or `403 …`	The app lacks Microsoft Graph permissions	Grant `Sites.Read.All` as application permission with admin consent, or a site grant for `Sites.Selected` (see Required Microsoft Graph permissions)
`Failed to resolve SharePoint site '…': 404 …`	Wrong site URL	Enter the full site URL, for example `https://contoso.sharepoint.com/sites/finance`
`Invalid SharePoint site_url (missing host): …`	The site URL has no host	Enter the full site URL starting with `https://`
`List '…' not found on SharePoint site '…'`	The list was renamed or deleted	Restore the list name, then resync the connector
`Unable to connect to SharePoint site. Reason: …`	Wrong tenant ID or an invalid certificate	Check the tenant ID and the certificate
`Could not connect to the data source. Check the connection details …`	DQC could not classify the error of the connection test	Check every field of the form, the network access and the permissions described above

Synchronization failed: when a sync cannot connect, the connector shows Failed on the Data sources screen and the badge links to this section. Edit the connector and click Load tables or Save: DQC tests the connection again and shows the current reason.
Lists missing from the table list: DQC imports custom lists only; document libraries and hidden lists are not listed (see What gets imported).
Still stuck? Write to support@dqc.ai with the connector name, the time of the attempt and the full message.