Synchronize outbound metadata to Databricks Unity Catalog
Synchronizing outbound metadata via the Databricks Unity Catalog integration is the process of propagating attribute and property values from Collibra Platform to Databricks Unity Catalog. Once you have set up a mapping, outbound synchronization runs automatically every 5 minutes if there are outbound events to process.
You can configure the following mappings for outbound synchronization:
- Collibra attribute to Databricks tag: applies an attribute value as a tag value on the matching Databricks object
- Collibra property to Databricks property: applies the Description attribute to the Databricks description field
- Collibra asset status to Databricks tag (in preview)
- Collibra articulation score to Databricks tag (in preview)
- Collibra average rating to Databricks tag (in preview)
- Collibra tags to Databricks tag (in preview)
- Collibra responsibility to Databricks tag (in preview)
- Collibra data classification to Databricks tag, for Column assets only (in preview)
The outbound flow is supported for Database, Schema, Table, Database View, and Column assets. For tag mappings, if you leave the tag name or value blank, the next synchronization removes the tag from the asset in Databricks Unity Catalog. Average rating mapping is the exception. Removing the rating writes 0 instead of removing the tag because 0 is a valid rating.
Note Outbound synchronization is only supported for assets ingested through the Databricks Unity Catalog integration, and not for assets ingested through a JDBC data source using the scalable ingestion flow.
About Databricks tags
The integration supports mapping the following two types of tags to Databricks Unity Catalog:- Custom tags: Custom tags accept any user-defined key-value pair. These are suitable for asset attributes such as description or any other custom attributes where the possible values are not predefined.
- Governed tags: Governed tags are a subset of custom tags. These are linked to tag policies in Databricks Unity Catalog that define allowed values. In contrast to custom tags, governed tags are ideal for attributes such as status, where all possible values are known in advance. Note that governed tags only accept predefined allowed values and reject any others. If you assign a tag value that is not allowed, it will not be propagated to the governed tag in Databricks Unity Catalog. In this case, the new value will appear in the asset attribute but the associated governed tag will remain unchanged. For attributes with multiple values, the combined, semicolon-separated value must itself match an allowed value, so use a custom tag or policy that allows the combined values. For more information on governed tags, go to the Databricks Unity Catalog documentation.
Prerequisites
In your Collibra environment:
- To configure outbound synchronization using the Databricks Unity Catalog integration, you need:
- Collibra Platform 2026.03 or newer.
- Edge 2026.3.21 or newer.
- You have integrated metadata from Databricks Unity Catalog to Collibra Platform.
- When you created the Databricks Unity Catalog connection, you granted the necessary permissions in Databricks Unity Catalog for outbound synchronization.
- If you're using an Edge site older than version 2025.10.126, you must rerun the inbound metadata synchronization for tag mappings to be applied to database and schema assets in Databricks Unity Catalog.
Steps
To configure an outbound mapping for Databricks Unity Catalog:
-
On the main toolbar, click
→
Catalog.
The Catalog homepage opens. - Click Integrations.
The Integrations page opens. - Click the Integration configuration tab.
- In the Integration column, click the link for your Databricks Unity Catalog integration.
The integration settings page opens. - Select the Metadata outbound tab and then click Add configuration.
- Complete the fields as needed.
- In the Collibra attribute to Databricks tag mappings section, click Add tag mapping to add a new tag mapping.
- In the Asset field, select the supported asset type to which you want to apply the tag mapping. If you do not specify an asset type, the tag mapping will apply to all applicable asset types by default.
- In the Attribute field, select the attribute whose value you want to send to Databricks Unity Catalog. Attributes with multiple values are also supported. Their selected values are combined into a single Databricks tag value joined with a semicolon (
;). For example,Finance;HR;Legal. - In the Tag key field, specify the value to be mapped in Databricks Unity Catalog for the selected attribute.
- In the Collibra property to Databricks property mappings section, click Add Collibra property to Databricks property mapping to add a new property mapping.
- In the Asset field, select the supported asset type to which you want to apply the mapping. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
- In the Collibra property field, select the attribute whose value you want to send to Databricks Unity Catalog. Currently, only Description is available.
- In the Databricks property field, select the native Databricks object property to receive the value. Currently, only description is available.
- In the Collibra asset status to Databricks tag mappings section, click Add status mapping.
- In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
- In the Tag key field, specify the value to be mapped in Databricks Unity Catalog for the selected attribute.
- In the Collibra asset articulation score to Databricks tag mappings section, click Add articulation score mapping.
- In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
- In the Tag key field, specify the value to be mapped in Databricks Unity Catalog for the selected attribute.
- In the Collibra asset average rating to Databricks tag mappings section, click Add average rating mapping.
- In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
- In the Tag key field, specify the value to be mapped in Databricks Unity Catalog for the selected attribute.
- In the Collibra tag to Databricks tag mappings section, click Add tag mapping.
- In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
- In the Tag key field, specify the value to be mapped in Databricks Unity Catalog for the selected attribute.
- In the Collibra responsibility to Databricks tag mappings section, click Add responsibility mapping.
- In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
- In Role, select the resource role.
- In the Tag key field, specify the value to be mapped in Databricks Unity Catalog for the selected attribute.
- In the Collibra data classification to Databricks tag mappings section, click Add data classification mapping.
- In Asset, Column is selected by default. Data classification mapping applies to Column assets only.
- In Data classification, select the data classification.
- In the Tag key field, specify the value to be mapped in Databricks Unity Catalog for the selected attribute.
- Click Save.
Outbound synchronization runs automatically every 5 minutes if there are outbound events to process.
| Field | Action |
|---|---|
| Collibra attribute to Databricks tag mappings | Configure a tag mapping to send a Collibra attribute value to a Databricks Unity Catalog tag. To add an outbound tag mapping: For example, you map a Note Attributes with a maximum cardinality greater than 1 are not supported for outbound tag mapping. Each value is stored as a separate attribute instance and propagated as a separate update, so only the most recently changed value is sent. |
| Collibra property to Databricks property mappings | Configure a property mapping to send a Collibra property value to a native Databricks object property. Only Description mapping to the Databricks description property is currently supported. To add an outbound property mapping: For example, your team maintains certified descriptions for finance tables in Collibra. You map the Description attribute on Databricks Unity Catalog Table assets to the corresponding Databricks Unity Catalog description property. When you update a Databricks table's description in Collibra, the next outbound synchronization updates the description value on the table in Databricks Unity Catalog. |
| Collibra asset status to Databricks tag mappings (In preview) | Configure a status mapping to send an asset's current status name to a Databricks tag. On each status change, the new status name is written. When you remove the status, the integration removes the tag. |
| Collibra asset articulation score to Databricks tag mappings (In preview) | Configure an articulation score mapping to send an asset's articulation score, a decimal from 0.0 to 100.0 (for example, 87.5), to a Databricks tag. The integration removes the tag when the score is removed. |
| Collibra asset average rating to Databricks tag mappings (In preview) | Configure an average rating mapping to send an asset's average rating to a Databricks tag. The average rating can be one of the following values: 0, 0.2, 0.4, 0.6, 0.8, or 1. If you remove the average rating in Collibra, the integration writes 0 to the tag. It does not remove the tag because 0 is a valid average rating. |
| Collibra tag to Databricks tag mappings (In preview) | Configure a tag mapping to send all Collibra tags on an asset to a Databricks tag as a single value, joined with semicolons (for example, |
| Collibra responsibility to Databricks tag mappings (In preview) | Configure a responsibility mapping to send the owner of a responsibility to a Databricks tag as |
| Collibra data classification to Databricks tag mappings (In preview) | Configure a data classification mapping to send the label of an accepted data classification match (for example, |
The synchronization job synchronizes the Databricks Unity Catalog data.
After the outbound synchronization:
- You can view a summary of the results in the Activities tab.
- You can view the propagated attribute values in Databricks Unity Catalog.