Databricks releases, every cloud
- Compute sizing for Databricks Apps is now generally available
Offers Medium (2 vCPUs, 6 GB) and Large (4 vCPUs, 12 GB) sizes.
- You can now use custom base environments for Python, Python Wheels, and notebook tasks in serverless jobs
Defined with YAML files, they support Python, Python wheel, and notebook tasks.
- New resource types for Databricks Apps
Adds MLflow experiments, vector search indexes, UDFs, and Unity Catalog connections as resources.
- Serverless compute is now available in Azure China North 3
Available for notebooks, jobs, pipelines, and SQL warehouses.
- Serverless workspaces are now available in new GCP regions
Available in most GCP regions, see documentation for list.
- Serverless compute is now available in new regions
Added to Australia Southeast, Canada Central, Mexico Central, Norway East, and South Africa North regions.
- Run the change, do not just read it. Hands-on labs in your own Databricks workspace, graded when you submit. Browse labs
- Configure compute size for Databricks Apps (Public Preview)
Controls CPU, memory, and cost based on workload requirements.
- List MCP servers in Azure Databricks Marketplace (Public Preview)
Allows distribution of AI tools and connection to external data sources, requires provider listing.
- List MCP servers in Databricks Marketplace (Public Preview)
Lets users install MCP servers to connect AI agents to external data sources.
- Serverless notebook tasks can now use jobs environment
Replaces inherited serverless environment with configurable job environment.
- Serverless compute has been updated to version 17.3
Updated from version 17.2, requires no configuration changes.
- The billable usage table now records the performance mode of serverless jobs and pipelines
Records performance mode in product_features.performance_target column with values PERFORMANCE_OPTIMIZED, STANDARD, or null.
- Admins can now manage a workspace's serverless base environments (Public Preview)
Defines custom environment specs for serverless notebooks, allows setting a default for new notebooks.
Headlines, dates and product areas are Databricks' own, and every item links to the note it came from. The one-line summaries are ours.