Skip to content
Data warehouse ⇄ Developer tools

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

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

Close the gap between analytics and operations: ClickHouse 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.

ClickHouse is the central store where teams keep Materialized views, Distributed tables, Dictionaries, Tables (MergeTree family) 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 Mail messages (Outlook), Calendar events, Contacts, Drive items (OneDrive & SharePoint) produced in Microsoft Graph are exactly what analysts want to measure in ClickHouse, and the curated rows in ClickHouse 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 Materialized views, Distributed tables, Dictionaries, Tables (MergeTree family) in ClickHouse with Mail messages (Outlook), Calendar events, Contacts, Drive items (OneDrive & SharePoint) 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 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • 02 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
  • 03 Send Outlook mail through the sendMail action when a database or CRM record changes, then read replies back onto the same record.
  • 04 Mirror OneDrive and SharePoint drive items into a data store to index documents and their metadata for search and governance.

Common sync patterns

Keep user and access records aligned

Where Microsoft Graph manages users, directory, or access data, those records stay current in ClickHouse — and can be provisioned back from it — so ownership and permissions match across both.

Operational data lands in ClickHouse for analytics

Records created in Microsoft Graph — issues, events, messages, metrics, or user changes — replicate into ClickHouse 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 ClickHouse creates or updates the matching record in Microsoft Graph, so the operational tool acts on the same data the analysts already see.

What you can sync between ClickHouse 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.

ClickHouse objects Microsoft Graph objects How this pairing syncs
Views Saved queries used as curated, read-only sync sources. Users Entra ID user accounts read and written via /users; create, update profile attributes, and enable or disable accounts with User.ReadWrite.All. Views is specific to ClickHouse and Users to Microsoft Graph — each maps to any object or custom field on the other side.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. 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. Materialized views is specific to ClickHouse and Groups and memberships to Microsoft Graph — each maps to any object or custom field on the other side.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. 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. Distributed tables is specific to ClickHouse and Mail messages (Outlook) to Microsoft Graph — each maps to any object or custom field on the other side.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. Calendar events Outlook events via /users/{id}/events; read and write meetings, attendees, and recurrence, and accept or decline invitations. Dictionaries is specific to ClickHouse and Calendar events to Microsoft Graph — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Contacts Personal Outlook contacts via /users/{id}/contacts; full create, read, update, delete, synced two-way with CRM person records. Tables (MergeTree family) is specific to ClickHouse and Contacts to Microsoft Graph — each maps to any object or custom field on the other side.
Databases Namespaces that group tables and scope permissions for sync users. Drive items (OneDrive & SharePoint) Files and folders via /drives and /me/drive; read and write items, upload and download content, and read per-item metadata. Databases is specific to ClickHouse and Drive items (OneDrive & SharePoint) to Microsoft Graph — each maps to any object or custom field on the other side.

How changes propagate between ClickHouse 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.

ClickHouse Microsoft Graph Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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

Microsoft Graph ClickHouse 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 ClickHouse as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • 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 ClickHouse ⇄ Microsoft Graph

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your ClickHouse ⇄ 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 ClickHouse and Microsoft Graph.

How the ClickHouse and Microsoft Graph connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

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 ClickHouse 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 ClickHouse 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
    ClickHouse connected
    Microsoft Graph connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

ClickHouse 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 352 integrations available for ClickHouse and Microsoft Graph.

Popular · 5 of 352
All ClickHouse 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