Databricks Release Notes

Transactions that write to Unity Catalog managed Delta tables are now generally available. Group multiple SQL statements across one or more tables into a single atomic transaction using BEGIN ATOMIC ... END; or BEGIN TRANSACTION; ... COMMIT; syntax. All changes succeed together or roll back together, ensuring data consistency across your operations. Transactions require catalog commits enabled on participating tables. Transactions that write to Unity Catalog managed Iceberg tables remain in Private Preview.

See Transactions.

Databricks now automatically sends an email notification when a service principal token is set to expire within seven days. Because service principals don't have their own mailboxes, Databricks sends these notifications to workspace admins. Notifications are sent only for service principal tokens that have a lifetime longer than seven days and have been used at least once. No configuration is required.

See Service principal token expiration notifications.

The sample datasets /databricks-datasets mounted to DBFS are now also available in the samples catalog as samples.databricks.datasets, made available through OpenSharing. The datasets volume hosts a collection of Databricks-provided datasets that you can use to build and test data pipelines.

The samples catalog is available in Unity Catalog-enabled workspaces. For more information about the sample datasets available in the samples catalog, see Sample datasets.

You can now override a standalone streaming table's defined REPLACE WHERE predicate for a single refresh by adding a WHERE clause to the REFRESH STREAMING TABLE command. The override applies only to that refresh and doesn't change the table definition, which is useful for one-time backfills and corrections. This is supported only on standalone streaming tables created with a FLOW REPLACE WHERE clause. See REFRESH (MATERIALIZED VIEW or STREAMING TABLE).

Role-based access control (RBAC) is now in Public Preview. RBAC lets users assume a role in Databricks using only that role's permissions for the duration of the session instead of their own accumulated permissions. This enables exclusive access. Users must actively assume a role to reach sensitive data, which prevents them from accessing it as their own identity and from mixing data across use cases, clinical trials, projects, or clients.

To enable RBAC, an account admin turns on the preview at the account level. Workspace admins then enable it in each workspace.

See Role-based access control (RBAC).

Lakeflow Designer now supports all compliance security profile standards supported by Databricks and is available by default for workspaces with the compliance security profile enabled.

For a full list of supported compliance standards, see Compliance security profile.

See Lakeflow Designer.

Governance Hub is in Beta. Governance Hub is a centralized, account-level UI in the account console for monitoring governance across your Databricks account. It provides a unified view of data health and coverage, AI usage and spend, and cost drivers, with prioritized insights and recommendations. All views respect existing permissions.

Account admins can enable Governance Hub from the account console Previews page. See Governance Hub.

Priority pay-per-token, also referred to as priority mode, for Foundation Model APIs pay-per-token is generally available for partner models and in preview for open source models.

Priority mode is for latency-sensitive, real-time applications that need more consistent availability under load.

See Priority pay-per-token for Foundation Model APIs for model availability.

You can now create an S3 external location using automated setup, the recommended method for connecting an S3 bucket to Databricks. Automated setup uses AWS IAM temporary delegation to configure your external location and provision all required resources, including the IAM role, storage credential, and external location. It also provides built-in approval workflows for users who need AWS admin authorization. See Create an external location with automated setup.

You can now set a statement timeout on a single SQL warehouse so that different warehouses can apply different timeouts to their queries. Set the timeout with the statement_timeout field in the Create or Update warehouse APIs. This feature is in Beta and is API-only. See Warehouse-level timeout.

The managed Reddit Ads connector in Lakeflow Connect is now available in Beta. You can use the connector to ingest advertising campaign data and performance metrics from Reddit Ads into Databricks. See Reddit Ads connector.

Model Serving now supports Google Gemini 3.6 Flash as a Databricks-hosted model. You can access this model using Foundation Model APIs.

Customers are responsible for ensuring their compliance with applicable terms.

Model Serving now supports Google Gemini 3.5 Flash Lite as a Databricks-hosted model. You can access this model using Foundation Model APIs.

Customers are responsible for ensuring their compliance with applicable terms.

Context-based ingress control for workspaces public access is now generally available. Control who can reach your workspace endpoints using allow and deny rules that allow you to combine identities, network sources, and request types. See Context-based ingress control.

You can now mention Genie Code in a notebook comment to get AI help without leaving the comment thread. Type @ in a comment, select Genie Code, and enter your request. Genie Code replies inline in the thread. See Code comments.

The Databricks Genie app in Microsoft Teams is now in Public Preview. The app brings Genie into Microsoft Teams so users can ask data questions and get answers without leaving Microsoft Teams. See Databricks Genie app in Microsoft Teams.

The Anthropic connector in Lakeflow Connect is now available in Beta. The connector allows you to ingest Compliance API data — audit activity, organizations, users, roles, groups, settings, and Claude chats and messages — from Anthropic into Databricks. See Anthropic connector.