Skip to content
Database ⇄ Storage

Google Cloud Spanner to Sharepoint integration — real-time, two-way sync

Keep Google Cloud Spanner 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 Google Cloud Spanner and Sharepoint

Keep Google Cloud Spanner and Sharepoint in step: a row in Google Cloud Spanner 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 Google Cloud Spanner 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, Databases, Tables, Rows in Google Cloud Spanner with List items, Drive items (document libraries), Columns and content types, Permissions and sharing 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 Consolidate data from a globally distributed Spanner deployment into regional business systems.
  • 02 Push billing or entitlement changes from finance tools into Spanner tables the application reads at runtime.
  • 03 Stream list and library changes through delta query and change-notification webhooks into a warehouse for audit, access-review, and reporting.
  • 04 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.

Common sync patterns

Records that point at documents

Where a record in Google Cloud Spanner 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 Google Cloud Spanner as they land, so a database-driven process can pick them up without polling the storage system's API.

Continuous archival to file storage

Rows from Google Cloud Spanner are written out to Sharepoint as files on a schedule or as they change, giving a durable, low-cost copy for backup, compliance, or a data lake, without a custom export job to maintain.

What you can sync between Google Cloud Spanner 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.

Google Cloud Spanner objects Sharepoint objects How this pairing syncs
Databases Top-level containers that scope schema and sync configuration. 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. Databases is specific to Google Cloud Spanner and Sites to Sharepoint — each maps to any object or custom field on the other side.
Tables Relational tables mapped one-to-one to sync targets. 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. Tables is specific to Google Cloud Spanner and Lists to Sharepoint — each maps to any object or custom field on the other side.
Rows The unit of read and write in each sync cycle, keyed by primary key. 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. Rows is specific to Google Cloud Spanner and List items to Sharepoint — each maps to any object or custom field on the other side.
Interleaved tables Child rows physically co-located with parents; synced as related records. 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. Interleaved tables is specific to Google Cloud Spanner and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.
Secondary indexes Used to make incremental read queries efficient on non-key columns. 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. Secondary indexes is specific to Google Cloud Spanner and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.
Change streams Capture inserts, updates, and deletes for log-style change data capture. 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. Change streams is specific to Google Cloud Spanner and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner 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.

Google Cloud Spanner Sharepoint Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

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

Sharepoint Google Cloud Spanner 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 Google Cloud Spanner as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
  • 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 Google Cloud Spanner ⇄ Sharepoint

Connect Google Cloud Spanner and Sharepoint for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud Spanner 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 Google Cloud Spanner or Sharepoint record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Sharepoint.

How the Google Cloud Spanner and Sharepoint connectors work

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.

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 Google Cloud Spanner 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 Google Cloud Spanner 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
    Google Cloud Spanner connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Google Cloud Spanner 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 418 integrations available for Google Cloud Spanner and Sharepoint.

Popular · 7 of 418
All Google Cloud Spanner 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