Custom classifiers
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page describes how to create and manage custom classifiers for Databricks Data Classification in Unity Catalog. Custom classifiers extend the built-in classification system so you can detect sensitive data that is specific to your organization, such as internal employee IDs, proprietary product codes, vendor identifiers, or partner account numbers.
To create a custom classifier, you select a governed tag and provide example columns that contain representative values for the class. Data Classification then detects this class during its regular scans.
Using custom classifiers, you can:
- Tag organization-specific data: Detect and configure auto-tagging for data types that are unique to your organization, such as employee IDs, partner codes, or internal account numbers.
- Extend governance controls: Apply ABAC column-level masks to sensitive data.
Custom classifier configuration and the detection metadata that Databricks generates from your example columns are encrypted at rest. You can use a customer-managed key (CMK) on your system catalog to manage the encryption key. Configuring a CMK on the system catalog encrypts all data in the system catalog, not just custom classifier data.

Requirements
- Data Classification must be enabled on at least one catalog in the metastore. See Use data classification.
- Your workspace must have serverless compute available (enabled by default in workspaces with Unity Catalog).
- To create, edit, or delete a custom classifier, you must be a metastore admin.
- To create or edit a custom classifier, you must have
ASSIGNprivileges on the governed tag the classifier uses. See Manage permissions on governed tags. - To select a column for the classifier, you must have
SELECTon the table that contains it.
Create a custom classifier
-
From the Data Classification results page, click Manage custom classifiers.

-
In the Manage custom classifiers side panel, click Create custom classifier.
-
Select a tag. Choose an existing governed tag, or click Create new tag to define one inline. If the tag has allowed values, choose the specific value you want to detect.

-
Select example columns. Browse the catalog tree and select columns that contain representative values for the class. Choose columns whose values are typical of what you want detected — broader and more varied examples produce more accurate detection rules.

-
Click Create.
Detections from the custom classifier typically appear on the results page within a few hours.
A custom classifier applies to all catalogs in the metastore that have Data Classification enabled. Per-catalog or per-schema scoping is not supported.
Manage custom classifiers
The Manage custom classifiers side panel lists all custom classifiers configured for the metastore. From this panel, you can search by tag name, edit the example columns of an existing classifier, or delete a classifier.

Edit a custom classifier
To update the example columns for an existing custom classifier:
- In the Manage custom classifiers side panel, select the custom classifier you want to edit.
- Click Edit next to the example columns list.
- Add or remove columns. The example column limit still applies.
- Click Save.
Updates take effect within a few hours. Existing detections from the previous configuration remain in place.
The governed tag and tag value cannot be changed after a custom classifier is created. To switch to a different tag, delete the custom classifier and create a new one.
Delete a custom classifier
- In the Manage custom classifiers side panel, select the custom classifier you want to delete.
- Click Delete.
- Confirm the deletion.
- Confirm that the classifier is removed from the Manage custom classifiers side panel.
When you delete a custom classifier:
- No new detections are produced for that classifier.
- Existing detections are removed from the Data Classification results page.
- Tags that were already auto-applied to columns are not removed automatically.
Suspended custom classifiers
If rule generation or validation fails, Databricks suspends the custom classifier and shows a warning on the Data Classification results page. A suspended custom classifier produces no new detections.

To resolve a suspension, edit the custom classifier and replace example columns that are inaccessible or not representative enough. If the governed tag or tag value is no longer valid, delete the custom classifier and create a new one with a valid tag.
View custom classifier detections
To view custom classifier detections, follow the same steps as for built-in classifications. See View classification results.
Limitations
- You can create a maximum of 50 custom classifiers per metastore.
- Each custom classifier must reference between 1 and 10 example columns to provide sufficient data for classification.
- Governed tag naming is subject to Tag Policy rules.
- Custom classifiers apply to all Data Classification-enabled catalogs in the metastore. Per-catalog or per-schema scoping is not supported.
- The governed tag used by a custom classifier cannot be changed after creation. To use a different tag, delete and recreate the custom classifier.
- New and updated custom classifiers apply only to subsequent Data Classification scans. Existing scan results are not automatically reclassified, so detections for previously scanned data appear after the next scan completes.
- All Data Classification limitations apply to custom classifiers as well, including supported table types. See Limitations.
Troubleshooting
The following topics help you troubleshoot common issues with custom classifiers.
A custom classifier is suspended
Common causes include:
- One or more example columns reference tables that have been deleted or renamed since the classifier was created.
- The example columns are not representative enough for the system to learn a stable detection.
- The governed tag is no longer a governed tag, or the tag value is no longer valid.
To resolve, edit the custom classifier with a different set of example columns and wait for the next scan. If the suspension is caused by an invalid governed tag or tag value, delete the custom classifier and create a new one with a valid tag.
Permission denied when creating or listing custom classifiers
You must be a metastore admin. Creating or editing a custom classifier additionally requires ASSIGN privileges on the governed tag. See Requirements.
Cannot select an example column
You must have SELECT on the table that contains the column. If you do not have SELECT on the table, ask the table owner to grant it, or choose a different example column.