Skip to content
Data warehouse ⇄ Developer tools

BigQuery to Microsoft Graph integration — real-time, two-way sync

Keep BigQuery and Microsoft Graph 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 BigQuery and Microsoft Graph

Close the gap between analytics and operations: BigQuery holds the record while Microsoft Graph runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

BigQuery is the central store where teams keep Tables, Partitioned tables, Clustered tables, Datasets for reporting and analysis; Microsoft Graph runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Drive items (OneDrive & SharePoint), Teams messages and chats, Planner tasks, Users produced in Microsoft Graph are exactly what analysts want to measure in BigQuery, and the curated rows in BigQuery are what should drive the next action in Microsoft Graph. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Tables, Partitioned tables, Clustered tables, Datasets in BigQuery with Drive items (OneDrive & SharePoint), Teams messages and chats, Planner tasks, Users in Microsoft Graph field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Feed ML feature tables in BigQuery from operational systems on a continuous schedule
  • 02 Land CRM and ERP records in BigQuery continuously so dashboards reflect business systems without nightly batch jobs
  • 03 Mirror OneDrive and SharePoint drive items into a data store to index documents and their metadata for search and governance.
  • 04 Read Teams channel messages and chats into a warehouse for conversation analytics and compliance archiving, and post messages back for alerts.

Common sync patterns

Operational data lands in BigQuery for analytics

Records created in Microsoft Graph — issues, events, messages, metrics, or user changes — replicate into BigQuery tables as they happen, so reporting runs on current data instead of last night's export.

Warehouse signals reach Microsoft Graph

A row scored, flagged, or enriched in BigQuery creates or updates the matching record in Microsoft Graph, so the operational tool acts on the same data the analysts already see.

Backfill history, then stay live

Load the existing set of Drive items (OneDrive & SharePoint), Teams messages and chats, Planner tasks, Users into BigQuery once, then keep it current with every change — you get full history plus real-time updates without a separate pipeline.

What you can sync between BigQuery and Microsoft Graph

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.

BigQuery objects Microsoft Graph objects How this pairing syncs
Tables The syncable unit: only tables can be synced per the Stacksync docs. Users Entra ID user accounts read and written via /users; create, update profile attributes, and enable or disable accounts with User.ReadWrite.All. Tables is specific to BigQuery and Users to Microsoft Graph — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. Groups and memberships Microsoft 365 and security groups via /groups; read and write name, owners, and add/remove members, with membership deltas surfaced by delta query. Partitioned tables is specific to BigQuery and Groups and memberships to Microsoft Graph — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Mail messages (Outlook) Messages via /users/{id}/messages; read and create drafts, update, and send with the sendMail action, so this surface is fully read-write. Clustered tables is specific to BigQuery and Mail messages (Outlook) to Microsoft Graph — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. Calendar events Outlook events via /users/{id}/events; read and write meetings, attendees, and recurrence, and accept or decline invitations. Datasets is specific to BigQuery and Calendar events to Microsoft Graph — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Contacts Personal Outlook contacts via /users/{id}/contacts; full create, read, update, delete, synced two-way with CRM person records. Projects is specific to BigQuery and Contacts to Microsoft Graph — each maps to any object or custom field on the other side.

How changes propagate between BigQuery and Microsoft Graph

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.

BigQuery Microsoft Graph Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

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

Microsoft Graph BigQuery Sub-second propagation

DetectionMicrosoft Graph notifies Stacksync of record changes through webhook events. Delta query (change tracking) returns created, updated, and deleted items since the last deltaLink for users, groups, mail, events, contacts, and.

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

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
  • Microsoft Graph: Throttled per app and per tenant, returning HTTP 429 with a Retry-After header; limits vary by service — the Outlook mail service allows about 10,000 requests per 10 minutes per app per mailbox with up to 4 concurrent requests, and delta and subscription tokens expire and must be renewed.
What ships with BigQuery ⇄ Microsoft Graph

Connect BigQuery and Microsoft Graph for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Microsoft Graph connection.

Real-time

Two-way sync

Changes in BigQuery or Microsoft Graph instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever BigQuery or Microsoft Graph 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 BigQuery or Microsoft Graph record.

Observability

Monitoring

Track your BigQuery ⇄ Microsoft Graph sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BigQuery and Microsoft Graph.

How the BigQuery and Microsoft Graph connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

Microsoft Graph

Integration surface
Microsoft Graph unified REST API (v1.0 and beta) at graph.microsoft.com, spanning Microsoft 365 services — Entra ID, Outlook mail and calendar, OneDrive and SharePoint, Teams, and Planner; supports 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 Mail.ReadWrite, Calendars.ReadWrite, Files.ReadWrite.All, User.ReadWrite.All, and Group.ReadWrite.All; application permissions require tenant admin consent.
Change detection
Delta query (change tracking) returns created, updated, and deleted items since the last deltaLink for users, groups, mail, events, contacts, and driveItems; change-notification subscriptions (webhooks) POST near-real-time notifications to a notification URL and must be renewed before they expire.
Capabilities
read · write · webhooks
Rate limits
Throttled per app and per tenant, returning HTTP 429 with a Retry-After header; limits vary by service — the Outlook mail service allows about 10,000 requests per 10 minutes per app per mailbox with up to 4 concurrent requests, and delta and subscription tokens expire and must be renewed.
How it works

How to connect BigQuery to Microsoft Graph — 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 BigQuery and Microsoft Graph 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
    BigQuery connected
    Microsoft Graph connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

BigQuery and Microsoft Graph 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 354 integrations available for BigQuery and Microsoft Graph.

Popular · 5 of 354
All BigQuery integrations All Microsoft Graph 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