Skip to content
Database ⇄ Storage

Azure SQL Database to Sharepoint integration — real-time, two-way sync

Keep Azure SQL Database 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 Azure SQL Database and Sharepoint

Keep Azure SQL Database and Sharepoint in step: a row in Azure SQL Database for every file in Sharepoint, with names, paths, metadata, and status staying consistent in real time, in both directions.

A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in Azure SQL Database says a file exists and carries its name, location, and status, while Sharepoint holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.

Stacksync syncs Views, Schemas, Rows and columns, Stored procedures in Azure SQL Database with Permissions and sharing, Site pages, Sites, Lists in Sharepoint bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.

Common use cases

  • 01 Replicate Azure SQL tables to a warehouse without building custom CDC pipelines.
  • 02 Consolidate data from several line-of-business apps into one Azure SQL database as an integration hub.
  • 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

File metadata kept in step

Tags, custom properties, owner, or status columns edited on a row in Azure SQL Database write back to the matching file's metadata in Sharepoint, and metadata changed in Sharepoint updates the row, so the two never disagree about a file.

Records that point at documents

Where a record in Azure SQL Database references a file in Sharepoint, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.

A landing zone for incoming files

Files that arrive in a folder or bucket in Sharepoint become rows in Azure SQL Database as they land, so a database-driven process can pick them up without polling the storage system's API.

What you can sync between Azure SQL Database 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.

Azure SQL Database objects Sharepoint objects How this pairing syncs
Change tracking / CDC tables System-maintained change records used to drive incremental sync. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Change tracking / CDC tables is specific to Azure SQL Database and Site pages to Sharepoint — each maps to any object or custom field on the other side.
Tables The primary sync target; rows map one-to-one to records in the paired system. 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 is specific to Azure SQL Database and Sites to Sharepoint — each maps to any object or custom field on the other side.
Views Read-only projections used when the sync should expose a curated shape rather than raw tables. 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. Views is specific to Azure SQL Database and Lists to Sharepoint — each maps to any object or custom field on the other side.
Schemas Namespaces that organize tables and control which objects a sync user can reach. 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. Schemas is specific to Azure SQL Database and List items to Sharepoint — each maps to any object or custom field on the other side.
Rows and columns Standard relational records with typed columns; primary keys anchor upserts. 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. Rows and columns is specific to Azure SQL Database and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.
Stored procedures Existing business logic that some teams invoke on write instead of direct table inserts. 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. Stored procedures is specific to Azure SQL Database and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between Azure SQL Database 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.

Azure SQL Database Sharepoint Sub-second propagation

DetectionChanges in Azure SQL Database are captured at the source via change data capture — no polling loop against its API. Change data capture or change tracking, both supported on Azure SQL Database.

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

Sharepoint Azure SQL Database 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 Azure SQL Database as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • 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 Azure SQL Database ⇄ Sharepoint

Connect Azure SQL Database and Sharepoint for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure SQL Database 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 Azure SQL Database or Sharepoint record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure SQL Database and Sharepoint.

How the Azure SQL Database and Sharepoint connectors work

Azure SQL Database

Integration surface
SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers
Authentication
SQL authentication (database credentials) or Microsoft Entra ID authentication
Change detection
Change data capture or change tracking, both supported on Azure SQL Database; polling as a fallback
Capabilities
read · write · CDC

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 Azure SQL Database 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 Azure SQL Database 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
    Azure SQL Database connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure SQL Database 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 · Azure SQL Database ⇄ 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
    Azure SQL Database Sharepoint
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure SQL Database 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 434 integrations available for Azure SQL Database and Sharepoint.

Popular · 7 of 434
All Azure SQL Database 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