Session

Unity Catalog External Locations: Extending Governance to OneLake and Beyond

Overview

ExperienceIn Person
TrackGovernance & Security
IndustryEnterprise Technology
TechnologiesUnity Catalog
Skill LevelBeginner

Unity Catalog External Locations are how Databricks connects to storage. Users define a path to the storage, attach a credential, and UC governs everything built on top: managed tables, views and other assets. Currently, it supports S3, ADLS, GCS and Cloudflare R2.  We are expanding this functionality to include support for Microsoft OneLake.

In this session, we'll show how External Locations provide a consistent, extensible pattern for connecting Databricks to any storage platform — and walk through what it takes to create External Location for Microsoft OneLake. You'll see the architecture, the setup end-to-end, and a demo reading and writing UC-governed assets directly into OneLake storage without needing to setup any ETL pipelines.

We will close the session with what’s next: extending the same model to on-premise storage, so Unity Catalog becomes a single governance layer across your data estate.

Session Speakers

Ljubica Vujovic Boskovic

/Senior Product Manager
Databricks

Full Summary

Centralized governance for data that lives everywhere: external locations in Unity Catalog

Enterprise data now spans multiple clouds, regions, and on‑premises systems. Fragmentation is no longer just a data problem, it is a governance problem that blocks reliable access, auditing, and lineage. External locations in Unity Catalog provide a single control plane over distributed storage so teams can analyze data in place without replicating it, aligning access and oversight with where data actually lives.

FAQ


An external location is a securable abstraction that maps a storage URL to a storage credential in Unity Catalog. Administrators grant permissions on it and create Unity Catalog objects on top of data that stays in its original storage.

Users query with Databricks SQL or Spark. Unity Catalog checks permissions, including file access on the storage system, then issues a short‑lived credential to the driver to read the data, so users never manage cloud identities or storage paths.

External locations connect to Azure Data Lake Storage Gen2, Amazon S3, Google Cloud Storage, and Cloudflare R2. Microsoft Fabric OneLake support is in public beta, using the same creation semantics as other locations.

Databricks storage items in Fabric do not yet enforce OneLake data access rules. Any workspace principal with contributor, viewer, or admin roles can access the data, so the recommendation is to keep those Fabric workspaces limited to a small, trusted set of principals during beta.

Not yet. External locations currently require the Databricks workspace and the target storage to be in the same cloud, and true cross‑cloud access is a forward‑looking roadmap item.