Databricks Release Notes

The SendGrid connector is now available in Lakeflow Connect in Beta. Workspace admins can control access to this feature from the Previews page.

The connector ingests the SendGrid subuser directory and IP access-management activity for the parent account and each subuser into Databricks. Authentication uses a SendGrid parent-account API key, with support for both the global and EU data-residency endpoints.

See SendGrid connector.

You can now ingest data from a Gmail mailbox into Databricks using the managed Gmail connector in Lakeflow Connect. The connector ingests messages, labels, drafts, filters, and profile data using a Google service account, and syncs the messages and message_labels tables incrementally through the Gmail History API. This feature is in Beta.

See Gmail connector.

Identity attributes are in Beta. Databricks can store nine IdP-sourced attributes, such as title, department, and cost center, on account users, so they can be referenced in Unity Catalog ABAC column-masking policies. Account admins provision these attributes from their identity provider using automatic identity management or account SCIM 2.1, and use the Identity Attribute Control List to govern which attributes can be written.

See Identity attributes.

The Tags page in Governance Hub is now in Beta. The Tags page provides a centralized view of how tags are applied across your account. It summarizes governed tag usage, shows recent tag assignments and their sources, and surfaces recommendations to fix invalid tag values and add tags to important assets that are missing them.

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

OpenSharing support for tables backed by default storage is now generally available and is being enabled by default for accounts on a rolling basis. Providers can share these tables with any recipient, whether open or Databricks, including recipients that use classic compute. If the feature is not yet on by default for your account, an account admin can enable it in the account console.

For more details about the feature, see Limitations and Create shares for OpenSharing. For more details about enablement, see Sharing tables backed by default storage will be enabled by default for all accounts.

You can now control serverless network traffic between Databricks workspaces. Account admins use cross-workspace access to set which source workspaces can reach a workspace (ingress) and which destination workspaces a workspace's serverless workloads can send traffic to (egress). Traffic flows only when both the source workspace's egress rules and the destination workspace's ingress rules permit it. See Cross-workspace access.

You can now use Pages to give business terms, acronyms, and KPIs a single governed definition. Part of Unity Catalog semantics, Pages form the human-modeled layer of the Genie Ontology that Genie One draws on to ground its answers. See Pages.

You can now build custom trace views in the Databricks MLflow trace explorer. Describe the layout you want in plain language, and Genie generates a reusable view that surfaces the trace fields, metrics, and feedback controls most relevant to your review workflow. See Build a custom trace view.

The managed Google Search Console connector is now available in Beta in Databricks Lakeflow Connect. Use it to ingest search performance data, site metadata, and sitemap information from Google Search Console into Databricks.

The connector supports daily and hourly search analytics dimensions (date, country, device, page, query), as well as verified sites and submitted sitemaps. Incremental ingestion is supported for all search analytics tables.

You can now ingest data from Glean into Databricks using the managed Glean connector in Lakeflow Connect. The connector ingests company-wide usage insights for search, Assistant, and agents, along with the shortcuts (go links) defined in your Glean deployment, using a Glean Client API token. This feature is in Beta.

See Glean connector.

The Amplitude connector in Lakeflow Connect is now in Beta. Ingest product analytics event data along with event, cohort, and annotation metadata from Amplitude. See Amplitude connector.

Attribute-based access control (ABAC) GRANT policies dynamically grant Unity Catalog privileges to securables whose governed tags match a condition. They now support model services, model provider services, Model Context Protocol (MCP) services, and agent services, which are the resource types Unity Gateway governs. This lets you grant access to gateway resources by tag instead of one at a time. All supported types are in Beta.

See ABAC GRANT policies.

REPLACE USING flows are now available for standalone streaming tables in Beta.

Use a REPLACE USING flow when your source is a series of partial snapshots keyed by column. On each update, the flow replaces all rows that match the specified key columns and leaves all other rows unchanged. A SEQUENCE BY column orders the updates, so the highest sequence for a key always wins, even when updates arrive out of order. REPLACE USING doesn't require a change data capture feed with explicit insert, update, and delete operations, and it doesn't require a primary key.

See Apply partial snapshot replacement with REPLACE USING flows.

ABAC GRANT policies dynamically grant Unity Catalog privileges to securables whose governed tags match a condition. These policies were previously only available for models, but now also support model services, model provider services, Model Context Protocol (MCP) services, and agent services. All supported types are in Beta.

For more information, see ABAC GRANT policies.

Lakebase is now PCI-DSS and HITRUST compliant for workspaces with the compliance security profile enabled. On AWS, this support is limited to the us-east-1 region. On Azure, all regions where Lakebase is available are supported. See Data protection.

DeepSeek V4 Flash (0731) is now available on Unity Gateway for fast, cost-efficient reasoning, coding, and agentic tool use. Access it through the same governed API as other models, with centralized permissions, guardrails, spend controls, and observability, and switch models without changing application code.

Customers are responsible for ensuring their compliance with applicable terms.

To query the model and see supported regions, see Use foundation models.