CSA LoomCSA Loom
Home
Ctrl K
Sign in
HomeWorkspacesBrowse
Lakehouse catalogSearchMarketplaceData productsConnectionsGovernance
Real-Time IntelligenceData ScienceOrchestration (Warp)Estate builderAgent MeshDeveloper
DeploymentWorkload hubScheduler
LineageAssetsMonitorReportsCopilot
  1. Home
  2. Unified catalog

One catalog across your Loom workspaces, Microsoft Purview, and Databricks Unity Catalog — search, govern, and grant access without leaving Loom. (Fabric OneLake is opt-in.)
SearchFederated search across Purview, Unity Catalog, and OneLake.BrowseTree view: source → workspace → schema/domain → asset.PermissionsLoom roles that fan out to Purview RBAC, UC GRANTs, and Fabric roles.Unity CatalogFull Unity Catalog: objects, grants, storage, sharing — Databricks (Commercial) or OSS (Gov).MetastoresRegistered Databricks metastores, Purview accounts, OneLake regions.LineageFederated lineage graph rolling up Purview + UC + Fabric edges.

Metastores & accounts

Manage the catalog back-ends Loom federates over. Register a Databricks workspace, attach it to a Unity Catalog metastore, and optionally catalog it in Microsoft Purview by registering it as a source and running a scan — all persisted across Console reloads, no bicep redeploy. Unity Catalog and Purview are the Azure-native defaults; Fabric OneLake appears as an optional, read-only mirror that gates nothing. Where an action needs a Databricks account admin or a missing env var, an honest warning names the exact role or setting to grant.