Customer-managed keys for encryption
Note
This feature requires the Premium Plan.
For some types of data, Azure Databricks supports adding a customer-managed key to help protect and control access to encrypted data. Azure Databricks has three customer-managed key features for different types of data:
- Customer-managed keys for managed disks
- Enable customer-managed keys for managed services
- Configure customer-managed keys for DBFS root
The following table lists which customer-managed key features are used for which types of data.
| Type of data | Location | Customer-managed key feature |
|---|---|---|
| Notebook source and metadata | Control plane | Managed services |
| Personal access tokens (PAT) or other credentials used for Git integration with Databricks Repos | Control plane | Managed services |
| Secrets stored by the secret manager APIs | Control plane | Managed services |
| Databricks SQL queries and query history | Control plane | Managed services |
| Customer-accessible DBFS root data | Your workspace’s DBFS root in your workspace DBFS root storage in your Azure subscription. This also includes workspace libraries and the FileStore area. | DBFS root |
| Job results | Workspace root DBFS storage instance in your Azure subscription | DBFS root |
| Databricks SQL results | Workspace root DBFS storage instance in your Azure subscription | DBFS root |
| MLflow Models | Workspace root DBFS storage instance in your Azure subscription | DBFS root |
| Delta Live Table | If you use a DBFS path in your DBFS root, this is stored in your workspace root DBFS storage instance in your Azure subscription. This does not apply to DBFS paths that represent mount points to other data sources. | DBFS root |
| Interactive notebook results | By default, when you run a notebook interactively (rather than as a job) results are stored in the control plane for performance with some large results stored in your workspace root DBFS storage in your Azure subscription. You can choose to configure Azure Databricks to store all interactive notebook results in your Azure subscription. | For partial results in the control plane, use a customer-managed key for managed services. For results in the root DBFS storage, which you can configure for all result storage, use a customer-managed key for DBFS root. |
| Other workspace system data in the root DBFS storage that is inaccessible through DBFS, such as notebook revisions. | Workspace root DBFS storage in your Azure subscription | DBFS root |
| Managed disks | Temporary disk storage of VMs in compute resources such as clusters. Applies only to compute resources in the Classic data plane in your Azure subscription. See Serverless compute and customer-managed keys. | Managed disks |
For additional security for your workspace’s root DBFS storage instance in your Azure subscription, you can enable double encryption for the DBFS root.
Serverless compute and customer-managed keys
Databricks SQL Serverless supports customer-managed keys for managed services and root DBFS storage.
Customer-managed keys for managed disk storage do not apply to serverless compute resources. Disks for serverless compute resources are short-lived and tied to the lifecycle of the serverless workload. When compute resources are stopped or scaled down, the VMs and their storage are destroyed.
Feedback
Submit and view feedback for