Data and AI releases

2,002 this month · 180 companies

Table update triggers on OpenSharing objects and system tables are now generally available

Generally availableNot yet verified

Lakeflow Jobs table update triggers can monitor OpenSharing objects and system tables. See Add a trigger to OpenSharing and system tables .

Observability

Read on docs.databricks.com

Also shipped Sep 30, 2026Databricks in September 2026 →

The new Astro experience is now live for all Organizations

The new Astro experience is now turned on for all Organizations and is out of Preview. It replaces the previous Astro experience, so there is no longer an opt-in or an option to switch back. The change doesn't affect your pipelines or configuration. Astro's navigation gives you a single view across your entire Organization instead of a single Workspace.

Preview
Source ↗

The Astro IDE is generally available

The Astro IDE is now generally available and is no longer a Preview feature. The Astro IDE is a browser-based workspace for Apache Airflow where you write Dag code, validate and test changes, and deploy or push your work without setting up a local development environment.

GA
Source ↗

More from LakeflowEvery Lakeflow release →

GitLab connector is available in Beta

The managed GitLab connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. Use the connector to ingest repository, project, group, CI/CD, and security data from GitLab into Databricks.

Beta
Source ↗

Workday Activity Logging connector (Beta)

The Workday Activity Logging connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector incrementally ingests Workday user activity log events into Databricks. Authentication uses an OAuth refresh token. See Workday Activity Logging connector .

Beta
Source ↗

Okta System Logs connector is available in Beta

The managed Okta System Logs connector is now available in Beta in Databricks Lakeflow Connect. Use the connector to incrementally ingest audit and security events from the Okta System Log into Databricks. The connector uses SSWS API token authentication and supports Declarative Automation Bundles and API-based pipeline authoring.

Beta
Source ↗

Microsoft 365 Unified Audit Logs connector is available in Beta

The managed Microsoft 365 Unified Audit Logs connector is now available in Beta in Databricks Lakeflow Connect. Use the connector to ingest unified audit events from Microsoft Entra ID, Exchange, SharePoint, and other Microsoft 365 workloads into Databricks. The connector uses OAuth machine-to-machine authentication and supports incremental ingestion.

Beta
Source ↗

CrowdStrike Falcon Event Stream connector (Beta)

The CrowdStrike Falcon Event Stream connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector ingests Falcon Event Stream events from CrowdStrike Falcon into Databricks.

Beta
Source ↗

Akamai WAF connector (Beta)

The Akamai WAF connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector ingests web application firewall (WAF) security events from Akamai into Databricks. Authentication uses Akamai EdgeGrid API client credentials. See Akamai WAF connector .

Beta
Source ↗

1Password Event Logs connector (Beta)

The 1Password Event Logs connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector uses the 1Password Events API to ingest audit events, item usages, and sign-in attempts into Databricks. Authentication uses an Events Reporting bearer token.

Beta
Source ↗

Run Lakeflow pipelines as a group

You can now set a pipeline's run-as identity to an account group, in addition to a user or a service principal. Pipeline updates run with the group's permissions, so a team can own an automated pipeline without tying it to one person's account. See Set the run-as identity to a group .

Update
Source ↗