Lakebase release notes

This page lists new features, improvements, and behavior changes for Lakebase, the fully managed Postgres database on Azure Databricks.

For an overview of Lakebase, see Lakebase Postgres.

Note

Releases are staged. Your Azure Databricks account might not be updated until a week or more after the initial release date.

Postgres minor version updates

August 24, 2026

Lakebase updated its supported Postgres versions to 16.15, 17.11, and 18.6. These minor releases bring you the latest upstream Postgres fixes and security patches. When a new minor version is available, Lakebase applies it the next time your compute restarts. See Manage updates.

Lakebase available in four new Azure regions

August 18, 2026

Lakebase is now available in four additional Azure regions: North Central US (northcentralus), France Central (francecentral), Germany West Central (germanywestcentral), and East Asia (eastasia). For the full list of supported regions, see Region availability.

Lakebase Postgres APIs are now generally available

August 14, 2026

Programmatic management of Lakebase Postgres is now generally available through the REST API, Databricks CLI, and Databricks SDKs (Python, Java, Go). These interfaces support operations for projects, branches, endpoints, databases, roles, credentials, synced tables, and catalogs. See Lakebase Autoscaling API guide.

Lakebase support for compliance security profile standards

August 5, 2026

Lakebase is now available by default for workspaces with the compliance security profile enabled and either HIPAA, C5, or TISAX controls selected, and for workspaces with the compliance security profile enabled without a compliance standard. See Data protection.

Diagnose and fix Lakebase issues with Genie, using telemetry in Unity Catalog (Beta)

July 24, 2026

Lakebase adds AI-assisted troubleshooting: database issues and early warnings are surfaced to you with Insights, and you can then investigate and fix them conversationally with Genie. Both draw on database telemetry captured to Unity Catalog. See Observability.

Lakebase is now SOC 2 Type 2 compliant

July 14, 2026

Lakebase is now SOC 2 Type 2 compliant. For our SOC reports, please ask your Databricks account team or see Compliance.

Lakebase update notifications now post 3 days in advance

July 10, 2026

To deliver Postgres version updates, security patches, and new features to your projects sooner, Lakebase has shortened the planned update notification window. Planned updates are now posted at least 3 days in advance, rather than 7. You can check your project's settings for upcoming updates.

See Manage updates.

Lakebase now supports Postgres 18

June 18, 2026

Lakebase now supports Postgres 18. Postgres 17 remains the default version. To use Postgres 18, select it when creating a new project. For a full list of supported versions, see Postgres compatibility.

Lakebase snapshot storage is now billed

June 1, 2026

Starting June 1, 2026, snapshot storage is billable for Lakebase. Snapshot storage size is shown on the Backup & Restore page. For pricing details, see the Lakebase pricing page. To learn about managing snapshots, see Snapshots.

Postgres password authentication is now disabled by default for new Lakebase projects

May 21, 2026

New Lakebase projects now have native Postgres password authentication disabled by default. Existing projects are unaffected. To allow native Postgres roles to connect with static passwords, enable password connections in project settings. See Manage password connections.

Customer-managed keys for Lakebase available in all AWS and Azure regions

May 20, 2026

Customer-managed keys (CMK) for Lakebase are now available in all Lakebase regions on AWS and Azure. CMK encrypts Lakebase project data at rest using a key your organization owns in its cloud KMS. CMK is available for new Lakebase projects. See Customer-managed keys for Lakebase.

Lakebase now supports compute sizes up to 64 CU (128 GB)

May 20, 2026

Lakebase now supports compute sizes up to 64 CU (128 GB RAM), up from the previous maximum of 32 CU (64 GB RAM). Larger workloads can now use dynamic scaling. See Autoscaling.

Recover a deleted Lakebase project within 7 days

May 15, 2026

When you delete a Lakebase project, it now enters a soft-deleted state for 7 days before permanent deletion. You can recover the project during that window, restoring all branches, databases, endpoints, and project settings. See Recover a deleted project.

New Lakebase instances now scale to zero by default

May 13, 2026

New Lakebase instances now scale to zero by default after 24 hours of inactivity, reducing compute costs for idle projects. To learn more about scale to zero, see Scale to zero. To configure scale to zero, see Configure scale to zero. To change the scale to zero default for new Lakebase projects, see Compute defaults. This change does not affect existing projects.

Lakebase: Lakehouse Sync is now in Public Preview

May 12, 2026

Lakehouse Sync is now in Public Preview for Lakebase. Lakehouse Sync enables continuous, low-latency replication of your Lakebase Postgres tables into Unity Catalog managed Delta tables using Change Data Capture (CDC). See Lakebase Change Data Feed.

Lakehouse Sync is now available on Azure (Beta)

May 6, 2026

You can now continuously replicate Lakebase Postgres tables into Unity Catalog managed Delta tables using CDC. Lakehouse Sync captures row-level changes and writes them as SCD Type 2 history. No external compute, pipelines, or jobs are required. See Lakebase Change Data Feed.

Lakebase: Customer-managed keys

April 14, 2026

You can now manage encrypted Lakebase project data using a customer-managed key (CMK) from your own cloud KMS. This gives your organization full control over encryption and helps meet regulatory and compliance requirements. See Customer-managed keys for Lakebase.

Lakebase databases as Databricks Apps resources

March 16, 2026

You can now add Lakebase databases as resources for your Databricks app. See Add a Lakebase resource to a Databricks app.

Lakebase updates: OAuth role management and budget policies and tags

March 12, 2026

Lakebase now includes the following features:

OAuth roles: Create OAuth roles using the Lakebase UI or REST API, in addition to SQL. See Create Postgres roles.
Budget policies and tags: Associate a serverless budget policy and add custom tags to your project for cost attribution and tracking. See Manage projects.

New Lakebase instances include autoscaling by default

March 12, 2026

New Lakebase instances are now created with autoscaling compute, scale-to-zero, branching, and instant restore by default. This applies when you create instances using the UI, Database instance API, Terraform, or SDKs. See Autoscaling.

Lakebase is now generally available with compliance security profile

March 4, 2026

Lakebase is now generally available for workspaces with the compliance security profile when the compliance standard is set to HIPAA, C5, TISAX, or None.

See Lakebase compliance.

Lakebase now includes high availability

March 2, 2026

Lakebase now includes high availability. High availability provides automatic failover from your primary compute instance to secondary compute instances distributed across availability zones, with no connection string changes required.

See High availability.

Lakebase is now generally available on Azure

March 2, 2026

Lakebase is now generally available on Azure, with autoscaling compute, scale-to-zero, branching, and instant restore. The GA release extends region support to 11 new Azure regions in addition to the existing eastus2, westeurope, and westus regions.

New regions:

australiaeast (Australia East)
brazilsouth (Brazil South)
canadacentral (Canada Central)
centralindia (Central India)
southcentralus (South Central US)
southeastasia (Southeast Asia)
eastus (East US)
centralus (Central US)
northeurope (North Europe)
uksouth (UK South)
westus2 (West US 2)

See Get started with Lakebase.

Lakebase now available on Azure (Beta)

February 4, 2026

Lakebase Postgres is now available on Azure in Beta. Access the Lakebase app from the app switcher to use autoscaling compute, scale-to-zero, database branching, and instant restore.

Supported Azure regions:

eastus2 (East US 2)
westeurope (West Europe)
westus (West US)