REPLACE WHERE flows are now generally available

GAJul 7, 2026VerifiedAdded Sep 22, 2026

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 .

Streaming Data integration

Read Databricks's release notes

https://docs.databricks.com/aws/en/release-notes/product/2026/july#replace-where-flows-are-now-generally-available

Summaries of vendors' own notes. Product names and logos belong to their owners; logos via logo.dev.

More Lakeflow releases

LakeflowJul 7, 2026

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 .

UpdateSQLStreamingData integrationSource

LakeflowJul 8, 2026

Behavior changes for continuous jobs and pipelines

In early August 2026, continuous Lakeflow pipelines and jobs will receive updates to simplify configuration. You will be able to configure a continuous schedule directly from the pipeline page, including job-level settings such as performance mode . Configuring a continuous schedule this way wraps the pipeline in a continuous job.

UpdateData integrationPerformanceSource

LakeflowJul 6, 2026

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.

UpdateSQLStreamingPerformanceSource

LakeflowJul 9, 2026

Change to default pipeline editor for workspaces with the compliance security profile enabled

The Lakeflow Pipelines Editor has been generally available since May 2026. In August, it will become the default editor for developing and debugging pipelines in workspaces with the compliance security profile enabled. At that time the legacy editor will be removed.

GAGovernanceSecurityData integrationSource

LakeflowJul 9, 2026

Strac connector (Beta)

The Strac connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector ingests data-security audit events from your Strac instance into Databricks. Authentication uses a Strac API key. See Strac connector .

BetaSecurityData integrationDeveloper toolsSource

LakeflowJul 2, 2026

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.

GASQLData integrationPerformanceSource

LakeflowJul 1, 2026

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.

BetaSecurityData integrationDeveloper toolsSource

LakeflowJul 1, 2026

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.

BetaStreamingData integrationSource

Also shipped on Jul 7, 2026

Snowflake SnowflakeJul 7, 2026

Deep Research in Snowflake CoWork (General availability)

Deep Research in Snowflake CoWork is now generally available. Deep Research is an investigation mode for complex, open-ended questions that require multi-step reasoning across your data.

GASource

Microsoft Azure databases and analyticsJul 7, 2026

[Launched] Generally Available: Network Security Perimeter support for Azure Event Hubs

Azure Event Hubs now supports Network Security Perimeter (NSP), enabling organizations to define a logical network isolation boundary for PaaS resources and control public network access through perimeter-based access rules.With Network Security Perimeter

GAStreamingSecuritySource

Microsoft Azure databases and analyticsJul 7, 2026

[Launched] Generally Available: Confidential Computing support for Azure Event Hubs Dedicated

Azure Event Hubs Dedicated now supports Confidential Computing, enabling organizations to protect streaming data while it is being processed in memory. By leveraging hardware-based trusted execution environments (TEEs), customers can help safeguard sensit

GAStreamingSource

GitHub GitHub CopilotJul 7, 2026

Per-user budgets for cost centers in the billing UI

Enterprise admins can now create cost center user-level budgets directly in the billing UI where you manage cost centers and budgets. This feature is available for GitHub Enterprise Cloud. This gives you the same per-user AI credit budget controls that were previously only available through the REST API.

PricingPricingObservabilityDeveloper toolsSource

GitHub GitHub Advanced SecurityJul 7, 2026

Secret scanning extended metadata and multipart validation

To help you understand ownership and impact of a leaked secret, GitHub secret scanning surfaces enriched metadata for supported secret types. Extended metadata checks are now generally available, including support for multipart validators with supplementary metadata. What’s new?

GASecurityDeveloper toolsPerformanceSource

GitHub GitHub platformJul 7, 2026

Restrict who can dismiss reviews in rulesets

You can now restrict who can dismiss pull request reviews directly in GitHub repository rulesets. This capability is generally available and gives you precise control over who can clear an approval before changes merge. The setting lives alongside the other review options in the Require a pull request before merging rule.

GAObservabilityDeveloper toolsSource