MySQL integrated CDC pipeline is now in Beta
The integrated CDC pipeline for MySQL is now in Beta . An integrated CDC pipeline ingests change data from MySQL into Databricks using a single pipeline, combining extraction and application into one pipeline update. Unlike the standard gateway-based architecture, an integrated CDC pipeline requires no separate ingestion gateway.
Also shipped Jul 1, 2026Databricks in July 2026 →
Fivetran Context Layer is in public preview
Context Layer builds a context layer from documentation sources, systems of record and analytical sources, then connects it to an organization's AI coding and chat tools.
Fivetran sunsets the AVEVA PI and Delighted connectors
New AVEVA PI and Delighted connections are blocked from July 1, 2026. Existing AVEVA PI connections stop syncing July 23, 2026, and Delighted connections are paused after the Delighted API deprecation.
Fivetran Move a Connection REST API endpoint enters beta
A new beta endpoint moves connections from one destination group to another.
Workload identity federation for Snowflake workloads that access external services (General availability)
Snowflake can now act as the OpenID Connect (OIDC) provider when Snowflake workloads authenticate to external services. To use this capability, create a secret of type WORKLOAD_IDENTITY_FEDERATION and share its issuer URL and subject identifier with the external service to establish trust.
Provisioned Throughput: Multiple pending new orders GA
The ability to submit multiple pending orders is generally available. you can submit up to seven Google model orders for the same model and region. See Multiple pending orders .
Looker (Google Cloud core) release channels enter preview
Instances can choose Rapid, Regular or No channel to control update cadence. Rapid gives early access but is excluded from the SLA, while Regular offers optional Accelerated Security Patching.
More from LakeflowEvery Lakeflow release →
Veeva Vault connector (Beta)
The Veeva Vault connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector uses Veeva's Direct Data API to ingest all standard objects, custom objects, system tables, and audit trail tables from your Vault instance into Databricks.
Lakeflow Connect row filtering is now generally available
Row filtering in Lakeflow Connect is now generally available. Row filtering allows you to ingest only the rows you need by applying conditions similar to a SQL WHERE clause, improving performance and minimizing data duplication.
Run a subset of job tasks with their dependencies
When you run a subset of a job's tasks, you can now expand your selection to include each task's dependencies. Add the + modifier to a task key to also run its upstream tasks ( +my_task ), its downstream tasks ( my_task+ ), or both ( +my_task+ ). Start a partial run from the UI, the REST API, the Databricks CLI, the SDKs, or Declarative Automation Bundles.
SQL alert task in Lakeflow Jobs is now generally available
The SQL alert task in Lakeflow Jobs is now generally available. Use the task to evaluate a Databricks SQL alert as part of a Lakeflow Job. The task returns its evaluation state as a task output value, so downstream tasks can branch on the result. See SQL alert task for jobs .
Standard performance mode is now supported for materialized view or streaming table refreshes in jobs
Materialized view and streaming table refreshes that are orchestrated through a SQL task in a Lakeflow job now respect the job's Performance optimized setting. When the setting is turned off, the refresh uses standard performance mode, which consumes fewer DBUs.
Microsoft Dynamics 365 connector (GA)
The managed Microsoft Dynamics 365 connector in Lakeflow Connect is now generally available. The connector allows you to ingest CRM and ERP data from Dynamics 365 into Databricks using Azure Synapse Link. See Microsoft Dynamics 365 connector .
REPLACE WHERE flows are now generally available
REPLACE WHERE flows for pipelines and standalone streaming tables are now generally available. Use them to replace only rows matching a predicate on each refresh, without reprocessing the full table history. See Batch processing with REPLACE WHERE flows .
Excel file format support is now available by default
Excel file format support is now available by default for all workspaces. You can ingest, parse, and query .xls , .xlsx , and .xlsm files directly using built-in support, without external libraries or manual conversions. See Read and stream Excel files .