Databricks releases, every cloud
- Lakebase is enabled by default in compliance security profile workspaces
Replaces manual Lakebase enablement in HIPAA, C5, or TISAX workspaces.
- Dedicated group clusters will soon be available by default for workspaces with the compliance security profile enabled Coming soon
Enables shared compute for groups with compliance security profile, supporting Databricks Runtime for ML and RDD APIs.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Data Classification is now available by default for additional compliance standards
Requires compliance security profile with C5, TISAX, or IRAP controls.
- 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.
- Run the change, do not just read it. Hands-on labs in your own Databricks workspace, graded when you submit. Browse labs
- 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.
- Serverless compute is enabled by default
Eligible Google Cloud workspaces are affected, account admins no longer need to manually enable it.
Headlines, dates and product areas are Databricks' own, and every item links to the note it came from. The one-line summaries are ours.