Databricks August 2026 product notes say sharing managed Iceberg tables is generally available as of August 14, covering Databricks-to-Databricks sharing, open sharing, and access for external Iceberg clients.

A day earlier, August 13 entries mark OpenSharing SecureConnect as generally available. Providers can share data from cloud storage behind a firewall or private endpoint without allowlisting each recipient’s network. Recipients keep their existing OpenSharing setup while Databricks routes storage access through a managed proxy. Related GA items in the same notes include sharing tables backed by default storage and sharing Delta tables with Iceberg reads enabled.

Why networking mattered

SecureConnect is designed for one-time provider setup: allow Databricks network endpoints on storage, enable SecureConnect on a metastore, then onboard recipients without per-customer firewall edits. Databricks said SecureConnect is rolling out by default for provider accounts, with expanded networking billing that can include recipient charges.

The Iceberg GA closes a gap for lakehouse teams that want open-table interoperability without rebuilding share pipelines for every external engine. Docs point providers to add managed Iceberg tables to a share and let recipients read them with Iceberg clients as well as Databricks consumers.

Decoded Take

Databricks is turning open table formats into a distribution channel, not only a storage format. SecureConnect removes a classic blocker for regulated data providers that refuse to punch holes for every partner. Watch how networking bills land on recipients, and whether Iceberg-native consumers outside Databricks become a meaningful share of share traffic versus Databricks-to-Databricks paths.