Source connector

SharePoint connector

SharePoint integration for databases, warehouses and BI tools

Document libraries and team site content. Datrise captures Microsoft SharePoint entities such as sites, lists, list items, documents, libraries and permissions, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Microsoft Graph API v1.0 (SharePoint sites, lists, and drives) authenticates with OAuth 2.0, incremental runs key on @odata.deltaLink from the driveItem/listItem/site delta endpoint, and SharePoint caps calls at No fixed requests-per-second figure; SharePoint Online throttles per app-per-tenant using resource units (1 RU for a single-item query or delta-with-token, 2 RU for multi-item queries/writes, 5 RU for permission expansions), with base caps of 1,250 RU/minute and 1,200,000 RU/24h for tenants under 1,000 licenses, scaling to 6,250 RU/minute and 6,000,000 RU/24h at 50,000+ licenses; exceeded limits return HTTP 429 with a Retry-After header.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `microsoft_sharepoint_sites`) with a schema derived from the SharePoint API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the SharePoint pipeline page, and join the waitlist to get the SharePoint connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Microsoft SharePoint data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
sites	microsoft_sharepoint_sites	Upsert by primary key, incremental on updated-at
lists	microsoft_sharepoint_lists	Upsert by primary key, incremental on updated-at
list items	microsoft_sharepoint_list_items	Upsert by primary key, incremental on updated-at
documents	microsoft_sharepoint_documents	Upsert by primary key, incremental on updated-at
libraries	microsoft_sharepoint_libraries	Upsert by primary key, incremental on updated-at
permissions	microsoft_sharepoint_permissions	Upsert by primary key, incremental on updated-at

Microsoft SharePoint API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Microsoft Graph API v1.0 (SharePoint sites, lists, and drives)
Authentication	OAuth 2.0 — Microsoft identity platform OAuth2 with either delegated permissions (on behalf of a signed-in user) or application permissions for app-only/daemon access, e.g. Sites.Read.All.
Pagination	token — `@odata.nextLink` (embeds an opaque `$skiptoken`) pages a collection; delta queries keep following `@odata.nextLink` until a final `@odata.deltaLink` is returned.
Rate limit	No fixed requests-per-second figure; SharePoint Online throttles per app-per-tenant using resource units (1 RU for a single-item query or delta-with-token, 2 RU for multi-item queries/writes, 5 RU for permission expansions), with base caps of 1,250 RU/minute and 1,200,000 RU/24h for tenants under 1,000 licenses, scaling to 6,250 RU/minute and 6,000,000 RU/24h at 50,000+ licenses; exceeded limits return HTTP 429 with a Retry-After header.
Incremental cursor	@odata.deltaLink from the driveItem/listItem/site delta endpoint — Delta tokens for directory-adjacent objects expire after 7 days; an expired or invalid token returns an HTTP 410 Gone requiring a full resync.
Webhooks	Yes — Change notifications (Microsoft Graph webhooks/subscriptions)
Bulk export	Yes — Microsoft Graph Data Connect
Deletes detectable	Yes — Deleted driveItems appear in delta responses with the `deleted` facet; listItem delta uses an `@removed` annotation with reason `changed` or `deleted`.

Official API reference

What bites when replicating Microsoft SharePoint

driveItem/listItem delta responses page via `@odata.nextLink` (with a `$skiptoken`) until the final page returns `@odata.deltaLink`; treating an intermediate page as final silently drops data.
SharePoint Online throttles per-app-per-tenant traffic starting at 1,250 resource units/minute and 1,200,000 resource units/24h for tenants under 1,000 licenses, scaling up to 6,250/minute and 6,000,000/24h for 50,000+ licenses.
A delta-with-token request costs only 1 resource unit versus 2 for a delta request without a token, so always resume from the stored `@odata.deltaLink`/`@odata.nextLink` rather than re-querying from scratch.
A stale delta token returns HTTP 410 Gone with a `resyncChangesApplyDifferences` or `resyncChangesUploadDifferences` error code, forcing a full resync of the target library.

Compare this against every other documented API

Popular destinations for Microsoft SharePoint

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Microsoft SharePoint connector FAQ

What SharePoint data does the connector extract?: 6 objects: sites, lists, list items, documents, libraries and permissions. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the SharePoint integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load SharePoint data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each SharePoint → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Microsoft SharePoint pipeline with guided onboarding

Join the waitlist to get priority access for Microsoft SharePoint integrations with guided setup, schema-aware mapping, and production-grade incremental sync.