Azure Databricks Unity Catalog connector - Metadata

Your understanding aligns well with my experience. Purview consistently discovers the Unity Catalog hierarchy (metastore, catalogs, schemas, tables/views, and columns), along with comments/descriptions, tags, and supported lineage. Table comments have also surfaced as asset descriptions in my experience, although Microsoft documents column comments more explicitly. I'd treat storage location as best-effort metadata rather than a guaranteed field, since its availability can vary by object type (especially managed vs. external tables) and connector behavior. Testing in your environment is still the best way to validate the exact metadata returned for your configuration.