BYOC in Five Checkpoints: Name, Split, Land, Govern, Operate
A five-checkpoint walkthrough of BYOC: name the control you need, split control and data planes, build the landing zone, govern data in place, then operate inside your own tenant.
ClickhouseAnnouncement
ClickHouse announced a significant expansion of its strategic collaboration with Microsoft at The European Microsoft Fabric + SQL Community Conference, including the public preview of a native ClickHouse workload for Microsoft Fabric that brings sub-second analytical query latency to OneLake. The company also made generally available the ability to read Apache Iceberg tables from OneLake using OneLake Table APIs, and introduced a public preview of writing Iceberg tables back to OneLake. These capabilities eliminate data duplication and ingestion steps, allowing teams to keep OneLake as the governed single source of truth while leveraging ClickHouse’s speed. ClickHouse Bring Your Own Cloud (BYOC) is now available in the Microsoft Marketplace, enabling customers to run ClickHouse Cloud inside their own Azure tenant with full control over IAM, networking, and encryption. The integrations aim to serve real-time agentic workloads, interactive dashboards, and observability without separate cluster provisioning or ETL pipelines.
The post is an announcement from ClickHouse, Inc. detailing a major expansion of its strategic collaboration with Microsoft at The European Microsoft Fabric + SQL Community Conference in Barcelona on September 29, 2026. It builds on ClickHouse’s existing presence in the Microsoft ecosystem, where customers use ClickHouse Cloud on Azure for real-time observability, BI, AI/ML pipelines, and analytical applications. The announcement reflects a shared commitment between ClickHouse and Microsoft to give data teams fast, flexible, and open infrastructure for analytics and AI without trading off between platforms.
Four integrations: a native ClickHouse workload for Microsoft Fabric (public preview) that accelerates OneLake queries to sub-second latency; GA of OneLake read for Apache Iceberg tables via OneLake Table APIs; public preview of OneLake write that writes Iceberg tables back to OneLake; and ClickHouse BYOC in the Microsoft Marketplace for running ClickHouse Cloud inside the customer’s Azure tenant.
The ClickHouse workload for Microsoft Fabric is in public preview and provides sub-second query latency on OneLake without needing a separate cluster or ETL pipeline.
ClickHouse support for reading Apache Iceberg tables from OneLake is now GA, letting customers query OneLake-managed data directly with no data duplication.
ClickHouse BYOC in the Microsoft Marketplace lets organizations run a fully managed ClickHouse Cloud inside their own Azure tenant while retaining ownership of data, IAM, and network controls.
Yes. ClickHouse now supports reading Apache Iceberg tables from OneLake using OneLake Table APIs, which is generally available. This allows customers to query Iceberg tables managed in OneLake directly from ClickHouse without data duplication or an ingestion step, keeping OneLake as the single source of truth.
ClickHouse BYOC lets organizations run ClickHouse Cloud inside their own Azure tenant. Data never leaves the customer's environment; IAM policies, network controls, and encryption remain under customer control, while ClickHouse handles provisioning, upgrades, monitoring, and scaling. It is available through the Microsoft Marketplace and counts toward Microsoft Azure Consumption Commitments (MACC).
Summaries are generated from the original by a language model. Check the original before relying on it.
See the idea
A five-checkpoint walkthrough of BYOC: name the control you need, split control and data planes, build the landing zone, govern data in place, then operate inside your own tenant.
Keep 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.
One useful email. Unsubscribe anytime.