Loading post…
ClickhouseAnnouncement
ClickHouse Workload for Microsoft Fabric: sub-second analytics on OneLake, now in public preview
Summary
The ClickHouse workload for Microsoft Fabric brings ClickHouse as a native acceleration layer for OneLake, now in public preview. It provisions dedicated ClickHouse Cloud services on Azure via the Fabric Extensibility Toolkit, using a ClickHouse item in the workspace. Users sync OneLake tables through ClickPipes as point-in-time snapshots with no ingestion charges. The embedded SQL console and external tools (Power BI, Copilot Studio, GitHub Copilot) can then query billions of rows with sub-second response times at high concurrency. Planned future features include write-back to OneLake, continuous sync, permission sync, and deeper Power BI integration.
Context
Data teams on Microsoft Fabric face a challenge when AI agents, real-time dashboards, or customer-facing applications require millisecond query responses at high concurrency. Existing workarounds include pre-aggregation pipelines, custom caching layers, or external databases with hand-rolled ETL — each adding infrastructure to build, secure, and maintain outside the platform. The ClickHouse workload for Microsoft Fabric aims to address this by providing an acceleration layer that keeps OneLake as the source of truth.
Approach / What changed
The ClickHouse workload for Microsoft Fabric is a native Fabric workload that provisions dedicated ClickHouse Cloud services on Azure via the Fabric Extensibility Toolkit. Users create a ClickHouse item in their workspace, sync OneLake tables through ClickPipes (point-in-time snapshots in public preview), and query data with an embedded SQL console or external tools. Access is governed through Microsoft Entra token exchange, with workspace roles mapped to ClickHouse roles. The workload supports read-only agent endpoints for Copilot Studio and GitHub Copilot, Power BI via the certified connector, and standard ClickHouse clients.
Takeaways
The workload provisions a dedicated ClickHouse Cloud service on Azure for each Fabric workspace, with users mapped from Microsoft Entra and roles inherited from Fabric workspace roles.
Syncing from OneLake uses ClickPipes for point-in-time snapshots; data flows within Azure with no egress costs and no ingestion charges during the public preview.
The service can serve as a governed, read-only endpoint for AI agents in Microsoft Copilot Studio and GitHub Copilot, as well as Power BI, Fabric notebooks, and standard ClickHouse clients.
FAQ
How can I query accelerated data within Fabric?
In the embedded SQL console, you can run standard SQL queries with ClickHouse's full analytical capabilities. Full-table aggregations over billions of rows return results in milliseconds, even with many concurrent clients. Queries can be saved for later use, but in public preview, saved queries are personal to each user.
How does the OneLake sync work technically?
The workload uses ClickPipes, the same managed ingestion that powers S3 and Azure Blob Storage pipes. The ClickPipe reads the table directly from OneLake using your authorized credentials, maps the types, and streams data into your dedicated ClickHouse Cloud service. Data flows between OneLake and your service within Azure with no egress costs.
Is the OneLake sync continuous or manual in preview?
Syncing from OneLake currently provides point-in-time snapshots, not continuous sync. The post states that continuous sync (richer replication) is planned for the future. For now, syncs are triggered manually and there are no ingestion charges during the public preview.
Source and freshness
- Source
- clickhouse.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.