Skip to content
Data warehouse ⇄ Storage

Dremio to Sharepoint integration — real-time, two-way sync

Keep Dremio and Sharepoint in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dremio and Sharepoint

Bridge query-ready tables and stored files: Dremio and Sharepoint keep the same records in step, in real time, in both directions.

Dremio keeps the tables and query results a business reports on; Sharepoint keeps the raw files, documents, and objects that the same business produces and shares. The two overlap wherever a dataset lives as both — a file dropped in Sharepoint that has to become rows in Dremio, or a result in Dremio that people downstream need back as a file in Sharepoint. When that overlap is bridged by manual export and import or an overnight job, one side spends the day working from a stale copy.

Stacksync syncs Jobs, Sources, Physical datasets, Virtual datasets (views) in Dremio with Site pages, Sites, Lists, List items in Sharepoint field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.
  • 02 Sync curated Dremio views into an operational Postgres so applications get low-latency access to lakehouse data.
  • 03 Two-way sync SharePoint List items with a database table so internal apps read and write structured records in SQL without calling the SharePoint API directly.
  • 04 Mirror document-library drive items and their metadata into a store to index files for search and governance, and push generated documents back into the right library.

Common sync patterns

Where Sharepoint holds the file inventory: make it queryable

The catalog of documents, owners, and folders in Sharepoint appears as Jobs, Sources, Physical datasets, Virtual datasets (views) in Dremio, so file metadata can be joined against the rest of your data and reported on.

Where Dremio computes the labels: push them onto the files

Classifications, scores, or status derived in Dremio are written back onto the matching Site pages, Sites, Lists, List items in Sharepoint as metadata or tags, so the file store reflects what analytics decided.

Where Sharepoint receives the raw files: land them as query-ready rows

Files and exports that arrive in Sharepoint are parsed into Jobs, Sources, Physical datasets, Virtual datasets (views) in Dremio as they land, so analysts query current data instead of waiting on the next scheduled load.

What you can sync between Dremio and Sharepoint

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Dremio objects Sharepoint objects How this pairing syncs
Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. Permissions and sharing Role assignments and sharing links on sites, list items, and drive items; read and written to manage access, requiring Sites.Manage.All or Sites.FullControl.All scopes. Apache Iceberg tables is specific to Dremio and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.
Spaces and folders Namespaces that organize virtual datasets and govern access. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Spaces and folders is specific to Dremio and Site pages to Sharepoint — each maps to any object or custom field on the other side.
Reflections Materialized accelerations that make repeated extraction queries cheaper. Sites SharePoint site collections and subsites via /sites; read site properties and discover the document libraries (drives) and lists each site contains, addressed by hostname and site path or site ID. Reflections is specific to Dremio and Sites to Sharepoint — each maps to any object or custom field on the other side.
Jobs Query execution records useful for monitoring sync workloads. Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. Jobs is specific to Dremio and Lists to Sharepoint — each maps to any object or custom field on the other side.
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. Sources is specific to Dremio and List items to Sharepoint — each maps to any object or custom field on the other side.
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. Drive items (document libraries) Files and folders in a library's drive via /drives and /drive/root; upload, download, move, delete, and read per-item metadata, synced two-way with a store. Physical datasets is specific to Dremio and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between Dremio and Sharepoint

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Dremio Sharepoint Interval-based propagation

DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.

DeliveryEach detected change is written to Sharepoint through its API, with automatic retries and rate-limit backoff.

Sharepoint Dremio Sub-second propagation

DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.

DeliveryEach detected change is applied to Dremio as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Dremio: Bounded by engine capacity and workload management rather than API rate limits.
  • Sharepoint: SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
What ships with Dremio ⇄ Sharepoint

Connect Dremio and Sharepoint for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dremio–Sharepoint connection.

Real-time

Two-way sync

Changes in Dremio or Sharepoint instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dremio or Sharepoint data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Dremio or Sharepoint record.

Observability

Monitoring

Track your Dremio ⇄ Sharepoint sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dremio and Sharepoint.

How the Dremio and Sharepoint connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits

Sharepoint

Integration surface
Microsoft Graph REST API (graph.microsoft.com/v1.0 and beta) covering SharePoint sites, lists, list items, columns, content types, and document-library drives and drive items; plus the classic SharePoint REST API (_api/web) and CSOM. Supports Graph JSON $batch (up to 20 requests per call).
Authentication
OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Sites.Read.All, Sites.ReadWrite.All, Sites.Selected, Sites.Manage.All, or Sites.FullControl.All, plus Files.ReadWrite.All for drive content; application permissions require tenant admin consent.
Change detection
Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last deltaLink; change-notification subscriptions (push webhooks) POST near-real-time notifications for list and drive/root changes to a notification URL and must be renewed before they expire. Classic SharePoint list webhooks are also available.
Capabilities
read · write · webhooks
Rate limits
SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
How it works

How to connect Dremio to Sharepoint — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Dremio and Sharepoint with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dremio connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dremio and Sharepoint objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dremio ⇄ Sharepoint
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dremio Sharepoint
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dremio and Sharepoint integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 425 integrations available for Dremio and Sharepoint.

Popular · 7 of 425
All Dremio integrations All Sharepoint integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own