Databricks releases, every cloud
- The READ METADATA privilege will soon be available by default for workspaces with the compliance security profile enabled Coming soon
Grants read-only visibility into object metadata, including security-sensitive information.
- Secrets in Unity Catalog will soon be available by default for workspaces with the compliance security profile enabled Coming soon
Replaces manual enablement, uses catalog.schema.secret namespace.
- Role-based access control (RBAC) will soon be available by default for workspaces with the compliance security profile enabled Coming soon
Lets users assume a role with exclusive permissions, replacing accumulated permissions.
- Lakebase is enabled by default in compliance security profile workspaces
Replaces manual Lakebase enablement in HIPAA, C5, or TISAX workspaces.
- MANAGE no longer requires USE CATALOG or USE SCHEMA on the same object
No longer requires USE CATALOG or USE SCHEMA on the same object, but still needs them on parent containers.
- Data Classification is now available by default for additional compliance standards
Requires compliance security profile with C5, TISAX, or IRAP controls.
- Run the change, do not just read it. Hands-on labs in your own Databricks workspace, graded when you submit. Browse labs
- Request for Access will soon be enabled by default for all workspaces Coming soon
Routes requests to Unity Catalog object owners via email, replacing workspace-level settings.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Databricks SQL alerts are now available by default for workspaces with the compliance security profile enabled
Supports all compliance security profile standards, monitors data and KPIs via scheduled queries.
- Data Classification is now available by default for some workspaces with the compliance security profile enabled
Requires compliance security profile and specific controls like HIPAA or HITRUST.
- Postgres password authentication is now disabled by default for new Lakebase projects
Existing projects are unaffected, enable in project settings to allow.
- New Lakebase instances now scale to zero by default
New instances scale to zero after 24 hours of inactivity, reducing compute costs. Existing projects are unaffected.
- New Lakebase instances include autoscaling by default
Autoscaling is on by default for new instances, applies to UI, API, Terraform, and SDK creations.
- File events enabled by default on new external locations
Enabled on new locations, detects file changes for storage jobs and pipelines, can be disabled after creation.
Headlines, dates and product areas are Databricks' own, and every item links to the note it came from. The one-line summaries are ours.