Skip to content
Data warehouse ⇄ Analytics

ClickHouse to Microsoft Power Bi integration — real-time data sync

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

Flow Microsoft Power Bi data into ClickHouse in real time — no exports, no schedulers, no custom scripts.

Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into ClickHouse, so ClickHouse always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.

Microsoft Power Bi is where teams explore, visualize, and report; ClickHouse is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.

Common use cases

  • 01 Read Users and workspace access for periodic access reviews reconciled against an HR or Microsoft Entra ID source of record.
  • 02 Mirror Workspaces, Reports, Dashboards, and Dataset metadata into a catalog database so teams discover Power BI content from a central index.
  • 03 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
  • 04 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.

Common sync patterns

Corrections propagate instead of reloading

When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.

One number both sides agree on

Metrics and aggregates stay aligned between the two systems, so a figure shown in Microsoft Power Bi matches the ClickHouse table it was built from instead of drifting between refreshes.

Where ClickHouse holds the source tables: live data in the reporting layer

Records maintained in ClickHouse flow into Microsoft Power Bi as they change, so dashboards and reports read current rows rather than an overnight extract.

What you can sync between ClickHouse and Microsoft Power Bi

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 Power Bi objects How this pairing syncs
Databases Namespaces that group tables and scope permissions for sync users. Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. Databases is specific to ClickHouse and Dataflows to Microsoft Power Bi — each maps to any object or custom field on the other side.
Views Saved queries used as curated, read-only sync sources. Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Views is specific to ClickHouse and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. Materialized views is specific to ClickHouse and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. Workspaces (Groups) Containers for content read via GET /groups (tenant-wide via GET /admin/groups); mirrored to reproduce the tenant's content hierarchy in a catalog. Distributed tables is specific to ClickHouse and Workspaces (Groups) to Microsoft Power Bi — 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. Activity Events (Audit Log) Admin audit log of user and content actions read via GET /admin/activityevents; loaded for security, access, and usage reporting across the tenant. Dictionaries is specific to ClickHouse and Activity Events (Audit Log) to Microsoft Power Bi — 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. Users and Access Workspace users and roles read via GET /groups/{id}/users or the admin scanner APIs; read for access reviews and identity reconciliation against an IdP. Tables (MergeTree family) is specific to ClickHouse and Users and Access to Microsoft Power Bi — each maps to any object or custom field on the other side.

How changes propagate between ClickHouse and Microsoft Power Bi

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 Power Bi 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.

DeliveryMicrosoft Power Bi does not accept inbound record writes, so this direction carries requests rather than records: Microsoft Power Bi's output flows back as field updates on the originating ClickHouse records.

Microsoft Power Bi ClickHouse Interval-based propagation

DetectionStacksync polls Microsoft Power Bi for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: no webhooks or change-data-capture.

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

Rate-limit considerations

  • Microsoft Power Bi: Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
What ships with ClickHouse ⇄ Microsoft Power Bi

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your ClickHouse ⇄ Microsoft Power Bi 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 Power Bi.

How the ClickHouse and Microsoft Power Bi 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 Power Bi

Integration surface
Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity.
Authentication
Microsoft Entra ID (Azure AD) OAuth 2.0 bearer tokens. Supports delegated user tokens and app-only service principals; service principals must be enabled under the tenant's Developer settings and granted workspace access. Tenant-wide admin reads require the Tenant.Read.All scope.
Change detection
Pull-based: no webhooks or change-data-capture. Content is polled via REST list endpoints, dataset changes are inferred from Refresh History and the admin Activity Events audit log, and the scanner API's GetModifiedWorkspaces reports workspaces changed since a given time.
Capabilities
read
Rate limits
Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
How it works

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

    Choose tables

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

ClickHouse and Microsoft Power Bi 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 472 integrations available for ClickHouse and Microsoft Power Bi.

Popular · 7 of 472
All ClickHouse integrations All Microsoft Power Bi 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