Databricks and Google Cloud Enable Cross-Platform Data Access

Databricks and Google Cloud say customers can now access a single copy of data from both Unity Catalog and Google Cloud's borderless Lakehouse. The companies are also working toward shared catalog metadata that can move between platforms.
- Customers can access one copy of data across Unity Catalog and Google Cloud's Lakehouse.
- BigQuery can read Unity Catalog managed tables without copying the data.
- Iceberg tables from Google Cloud's catalog can be queried in Databricks.
- Shared catalog labels can preserve governance metadata across federated catalogs.
- Databricks and Google Cloud are pursuing open governance and bi-directional interoperability.
Bidirectional access without data duplication
The milestone, announced by Databricks on November 17, 2026, extends the companies' work on catalog interoperability. Customers can access the same copy of data from either BigQuery or Databricks without creating a duplicate.
Through Lakehouse Federation to Google Cloud, customers can mount Iceberg tables managed by Google Cloud's Lakehouse runtime catalog in Unity Catalog. Those tables can then be queried by Databricks Lakehouse, Databricks' serverless data warehouse, or analyzed with Genie, which answers data questions from natural language without code or SQL.
The connection also works in the opposite direction. Data managed in Databricks can be brought into Google Cloud's Lakehouse, allowing engines such as BigQuery to read Unity Catalog managed tables without copying the data.
Metadata is the next interoperability target
Databricks and Google Cloud are also pursuing open catalog metadata. Databricks says business and governance semantics should remain accessible rather than being tied to one vendor's system.
In the Iceberg community, the companies helped drive and land catalog labels, a proposal that allows catalogs to share metadata through key-value pairs. For example, a table tagged as domain=finance and status=certified, or a column tagged as pii=ssn, can retain those labels when the table is federated from one catalog to another.
According to Databricks, shared labels can support governance by helping flag sensitive data for masking and by giving agents context when they search for assets to answer data questions.
Why the partnership matters for data teams
The announcement points to a more open Lakehouse architecture, building on open table formats including Delta Lake and Iceberg and extending that approach to catalog federation. The companies say their goal is bi-directional interoperability that works seamlessly across Unity Catalog and Google Cloud's Lakehouse.
For customers, the immediate benefit described by Databricks is the ability to use data across the two environments without maintaining separate copies. The longer-term aim is for governance rules and business context to travel with data, so enterprises do not have to redefine them in every system as their data estates expand and AI agents become more embedded in workflows.
Databricks directs customers to its documentation for Catalog Federation between Unity Catalog and Google Cloud's borderless Lakehouse. It also invites customers to share interoperability needs with their Databricks account team.


