Releasesby GlyphZerobus Ingest is now enabled by default for workspaces with the compliance security profile
The Zerobus Ingest connector in Lakeflow Connect is now enabled by default for workspaces with the compliance security profile enabled. See Zerobus Ingest overview .
Also shipped Aug 6, 2026Databricks in August 2026 →
Automations in Snowflake CoWork (Public Preview)
Automations in Snowflake CoWork are now in Public Preview. An automation turns a one-time report into a recurring one: Snowflake CoWork re-runs your question with fresh data on the schedule you choose and emails you the results, including a summary and key metrics, along with a link that opens the full report so you can ask follow-up questions.
Looker Granular Dashboard Sizing is generally available
Dashboard editors can resize and lay out tiles with more granularity. Tiles appear rearranged the first time a dashboard is edited after enablement, and the new layout persists once saved.
Looker Dashboard Tile Limits is generally available
Admins can cap tiles per dashboard and per tab to optimize performance, configured on the Content Guardrails page in the Performance Center.
General availability: Pinecone Nexus
Pinecone Nexus, the knowledge engine for agents, is now generally available. Point Nexus at your sources, curate them into a context, and query that context to get grounded, cited answers. Get started in the Nexus quickstart.
Kimi K3 is now available in GitHub Copilot
Editor’s note (August 6, 2026): We have resumed rolling out Kimi K3 in GitHub Copilot. This model is billed at provider list pricing under usage-based billing. See GitHub Copilot’s pricing for models and requests for details. Editor’s note (August 6, 2026): We have temporarily paused the roll-out of Kimi K3 while we mitigate an incident with GitHub Actions.
Skill and plugin security scanning (beta) for Enterprise plans
Enterprise plans can turn on scanning that automatically checks third-party skills and plugins for malicious content when someone uploads or edits them.
More from LakeflowEvery Lakeflow release →
JAR tasks on serverless compute are now generally available
Package Scala or Java code as a JAR and run it as a task in a Lakeflow Job on serverless compute, without provisioning or managing clusters. See Create and run JARs on serverless compute .
Change data feed on materialized views (Beta)
You can now read a change data feed from a materialized view created in a Lakeflow pipeline or in Databricks SQL, using Databricks Runtime 18 LTS or above. Use this to replicate materialized view changes to destinations outside Databricks, or to keep a history of materialized view changes for auditing and reporting.
REPLACE USING flows for pipelines (Beta)
REPLACE USING flows are now available in Lakeflow pipelines 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.
SharePoint connector (GA)
Both SharePoint connectors in Lakeflow Connect are now generally available: the managed connector for fully managed ingestion pipelines, and the standard connector for custom pipelines built with Spark and SQL APIs.
PagerDuty connector (Beta)
The managed PagerDuty connector in Lakeflow Connect is now available in Beta. The connector ingests incident, on-call, service, and audit data from PagerDuty into Databricks. See PagerDuty connector .
NetSuite connector (GA)
The managed NetSuite connector in Lakeflow Connect is now generally available. The connector allows you to ingest ERP and financial data from Oracle NetSuite into Databricks. See NetSuite connector .
Google Drive connector (GA)
Both Google Drive connectors in Lakeflow Connect are now generally available: the managed connector for fully managed ingestion pipelines, and the standard connector for custom pipelines built with Spark and SQL APIs.
Environment variables for serverless jobs are in Beta
Environment variables for serverless Lakeflow Jobs tasks are in Beta . You can define named environment variable entries at the job level and select one for each task to pass deployment-specific configuration to your application code. A workspace admin must enable the preview from the workspace Previews page.