Databricks Unity Catalog and Microsoft Purview: Are Tags Synchronized Automatically?

Unity Catalog tags are partially imported, not fully synchronized as Purview tags.

Supported metadata from Azure Databricks Unity Catalog scans in Microsoft Purview includes:

• Metastore
• Catalogs
• Schemas
• Tables, including columns
• Views, including columns
• Technical metadata
• Lineage between tables, views, and columns during notebook runs

For tags specifically:

• Microsoft Purview supports scanning tags from Unity Catalog.
• These tags are brought into Purview as properties.
• Unity Catalog tags are not fully synchronized as native Purview schema tags.
• Tags are not supported for scans done using a Kubernetes SHIR option.

Related metadata behavior:

• Table descriptions and column comments are supported and appear in Purview as asset description and column description.
• External table metadata is supported, but lineage for external assets is not supported.

References:

• Connect to and manage Azure Databricks Unity Catalog in Microsoft Purview
• Set up data quality for Azure Databricks Unity Catalog
• Clarification on Specific Metadata Sync Between Databricks Unity Catalog and Microsoft Purview (Column Comments & Tags, Table Descriptions) - Microsoft Q&A