Skip to content
Security and identity ⇄ Data warehouse

Azure Active Directory to ClickHouse integration — real-time, two-way sync

Keep Azure Active Directory and ClickHouse 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 Active Directory and ClickHouse

Land the users, groups, and access events from Azure Active Directory in ClickHouse continuously for security analytics, and write computed results back — without building or maintaining a pipeline.

Azure Active Directory is the record of who exists and what they can reach; ClickHouse is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Azure Active Directory governs are what security, compliance, and analytics teams want to query in ClickHouse. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Service principals, Directory roles, Devices, Users from Azure Active Directory into tables in ClickHouse in real time, and the connection works in both directions: values computed in ClickHouse, such as risk scores or access-review decisions, can be written back to attributes in Azure Active Directory where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.

Common use cases

  • 01 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
  • 02 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
  • 03 Sync manager, department, and jobTitle from an HRIS back onto Entra ID User attributes to keep dynamic groups and Conditional Access accurate.
  • 04 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.

Common sync patterns

Access governance on joined data

Join Azure Active Directory's users and group memberships with HR, product, and usage data already in ClickHouse to surface who holds access they no longer need.

Queryable history for audit and compliance

A continuously synced copy in ClickHouse gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.

Risk and review results back on the account

Risk scores, anomaly flags, or access-review outcomes computed in ClickHouse write back to attributes on the matching user in Azure Active Directory, where the identity team can act on them.

What you can sync between Azure Active Directory and ClickHouse

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 Active Directory objects ClickHouse objects How this pairing syncs
Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. Views Saved queries used as curated, read-only sync sources. Devices is specific to Azure Active Directory and Views to ClickHouse — each maps to any object or custom field on the other side.
Users /users in Microsoft Graph; synced two-way — profile attributes, accountEnabled, and assignedLicenses are read out while provisioning writes (create, update, disable, delete) are pushed back. Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Users is specific to Azure Active Directory and Materialized views to ClickHouse — each maps to any object or custom field on the other side.
Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. Distributed tables Query-routing tables over cluster shards in self-managed deployments. Groups is specific to Azure Active Directory and Distributed tables to ClickHouse — each maps to any object or custom field on the other side.
Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. Group memberships is specific to Azure Active Directory and Dictionaries to ClickHouse — each maps to any object or custom field on the other side.
Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Applications is specific to Azure Active Directory and Tables (MergeTree family) to ClickHouse — each maps to any object or custom field on the other side.
Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. Databases Namespaces that group tables and scope permissions for sync users. Service principals is specific to Azure Active Directory and Databases to ClickHouse — each maps to any object or custom field on the other side.

How changes propagate between Azure Active Directory and ClickHouse

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 Active Directory ClickHouse Sub-second propagation

DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.

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

ClickHouse Azure Active Directory 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 Azure Active Directory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Azure Active Directory: Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header.
What ships with Azure Active Directory ⇄ ClickHouse

Connect Azure Active Directory and ClickHouse for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–ClickHouse connection.

Real-time

Two-way sync

Changes in Azure Active Directory or ClickHouse instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Active Directory or ClickHouse 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 Active Directory or ClickHouse record.

Observability

Monitoring

Track your Azure Active Directory ⇄ ClickHouse sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Active Directory and ClickHouse.

How the Azure Active Directory and ClickHouse connectors work

Azure Active Directory

Integration surface
Microsoft Graph REST API (v1.0)
Authentication
OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent
Change detection
Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push
Capabilities
read · write · webhooks
Rate limits
Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header

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
How it works

How to connect Azure Active Directory to ClickHouse — 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 Active Directory and ClickHouse 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 Active Directory connected
    ClickHouse connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Active Directory and ClickHouse 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 Active Directory ⇄ ClickHouse
    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 Active Directory ClickHouse
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Active Directory and ClickHouse 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 538 integrations available for Azure Active Directory and ClickHouse.

Popular · 8 of 538
All Azure Active Directory integrations All ClickHouse 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