Two-way sync
Changes in Azure Synapse Analytics or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics 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.
Azure Synapse Analytics 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 Azure Synapse Analytics, or a result in Azure Synapse Analytics 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 Schemas, Materialized views, SQL pools, Tables (dedicated SQL pool) in Azure Synapse Analytics with Columns and content types, Permissions and sharing, Site pages, Sites 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.
Where the same dataset lives as a file in Sharepoint and a table in Azure Synapse Analytics, a change on either side propagates to the other, ending the drift between the file people read and the table people query.
The catalog of documents, owners, and folders in Sharepoint appears as Schemas, Materialized views, SQL pools, Tables (dedicated SQL pool) in Azure Synapse Analytics, so file metadata can be joined against the rest of your data and reported on.
Classifications, scores, or status derived in Azure Synapse Analytics are written back onto the matching Columns and content types, Permissions and sharing, Site pages, Sites in Sharepoint as metadata or tags, so the file store reflects what analytics decided.
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.
| Azure Synapse Analytics objects | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces that separate staging, integration, and presentation layers. | Columns and content types Field definitions and content types on a site or list; read the schema and create columns so database fields map cleanly onto SharePoint list fields. | Schemas is specific to Azure Synapse Analytics and Columns and content types to Sharepoint — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | 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. | Materialized views is specific to Azure Synapse Analytics and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side. | |
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | SQL pools is specific to Azure Synapse Analytics and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | 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. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | 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. | External tables is specific to Azure Synapse Analytics and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | 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. | Views is specific to Azure Synapse Analytics and List items to Sharepoint — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
DeliveryEach detected change is written to Sharepoint through its API, with automatic retries and rate-limit backoff.
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 Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Sharepoint connection.
Changes in Azure Synapse Analytics or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or Sharepoint data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or Sharepoint record.
Track your Azure Synapse Analytics ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Sharepoint.
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.
Authenticate Azure Synapse Analytics 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.
Pick the Azure Synapse Analytics 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 532 integrations available for Azure Synapse Analytics and Sharepoint.