Skip to content
Database ⇄ Business productivity

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

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

Mirror Microsoft 365's data into Google Cloud Spanner so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Microsoft 365 through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Google Cloud Spanner.

Stacksync mirrors Users, Groups, Mail Messages, Calendar Events from Microsoft 365 into Views, Databases, Tables, Rows in Google Cloud Spanner and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Microsoft 365, so the tool and the database never disagree.

Common use cases

  • 01 Sync employee records from an HR system into Entra ID users and group memberships.
  • 02 Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
  • 03 Consolidate data from a globally distributed Spanner deployment into regional business systems.
  • 04 Push billing or entitlement changes from finance tools into Spanner tables the application reads at runtime.

Common sync patterns

One integration pattern for the whole stack

Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.

Read Microsoft 365 with a query

Records from Microsoft 365 are ordinary rows in Google Cloud Spanner; join them, index them, and use them in application logic without touching the vendor API.

Automate Microsoft 365 from your codebase

Write to the synced tables in Google Cloud Spanner and Stacksync propagates the change into Microsoft 365, replacing custom integration code.

What you can sync between Google Cloud Spanner and Microsoft 365

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 Microsoft 365 objects How this pairing syncs
Views Read-only projections useful for shaping data before it leaves Spanner. Teams Team and membership data provisioned from upstream systems. Views is specific to Google Cloud Spanner and Teams to Microsoft 365 — each maps to any object or custom field on the other side.
Databases Top-level containers that scope schema and sync configuration. Planner & To Do Tasks Task items synced with project and work-management tools. Databases is specific to Google Cloud Spanner and Planner & To Do Tasks to Microsoft 365 — each maps to any object or custom field on the other side.
Tables Relational tables mapped one-to-one to sync targets. Users Entra ID user accounts synced with HR and identity systems. Tables is specific to Google Cloud Spanner and Users to Microsoft 365 — 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. Groups Microsoft 365 and security groups kept aligned with org structure and access rules. Rows is specific to Google Cloud Spanner and Groups to Microsoft 365 — 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. Mail Messages Exchange Online messages read for logging, archiving, or activity capture. Interleaved tables is specific to Google Cloud Spanner and Mail Messages to Microsoft 365 — 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. Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. Secondary indexes is specific to Google Cloud Spanner and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and Microsoft 365

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 Microsoft 365 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 Microsoft 365 through its API, with automatic retries and rate-limit backoff.

Microsoft 365 Google Cloud Spanner Sub-second propagation

DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.

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.
What ships with Google Cloud Spanner ⇄ Microsoft 365

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

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

Real-time

Two-way sync

Changes in Google Cloud Spanner or Microsoft 365 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 Microsoft 365 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 Microsoft 365 record.

Observability

Monitoring

Track your Google Cloud Spanner ⇄ Microsoft 365 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 Microsoft 365.

How the Google Cloud Spanner and Microsoft 365 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.

Microsoft 365

Integration surface
REST API (Microsoft Graph)
Authentication
OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
Change detection
Graph change notifications (webhooks) plus delta queries for incremental sync
Capabilities
read · write · webhooks
How it works

How to connect Google Cloud Spanner to Microsoft 365 — 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 Microsoft 365 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
    Microsoft 365 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Google Cloud Spanner and Microsoft 365 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 378 integrations available for Google Cloud Spanner and Microsoft 365.

Popular · 5 of 378
All Google Cloud Spanner integrations All Microsoft 365 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