Lakebase release notes

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.

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. For our SOC reports, please ask your Databricks account team or see Compliance.

To deliver Postgres version updates, security patches, and new features to your projects sooner, Lakebase Autoscaling 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 Autoscaling is now available in ap-northeast-1 (Asia Pacific - Tokyo). For all supported regions, see Region availability. To get started, see Get a Postgres database.

Lakebase Autoscaling 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.

Starting June 1, 2026, snapshot storage is billable for Lakebase Autoscaling. 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.

New Lakebase Autoscaling projects now have native Postgres password authentication disabled by default. Existing Autoscaling 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 (CMK) for Lakebase Autoscaling are now available in all Lakebase regions on AWS and Azure. CMK encrypts Lakebase Autoscaling project data at rest using a key your organization owns in its cloud KMS. CMK is available for new Lakebase Autoscaling projects. Lakebase Provisioned instances do not support CMK. See Customer-managed keys for Lakebase.

Lakebase Autoscaling 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.

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 Autoscaling 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 Autoscaling projects, see Compute defaults. This change does not affect existing projects.

Lakehouse Sync is now in Public Preview for Lakebase Autoscaling. 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.

Databricks is upgrading all Lakebase Provisioned instances to the Lakebase Autoscaling platform. Upgrades begin in June 2026 for customers who have requested them, with remaining instance upgrades continuing in the following weeks. Workspace admins will receive an email with upgrade dates before the upgrade begins.

The upgrade is automatic. Connections restart briefly during the transition, and existing connection strings, API calls, Declarative Automation Bundles, and Terraform configurations continue to work without modification.

After the upgrade, the following changes apply:

• Your instances will support autoscaling features and can be managed through both the new Autoscaling UI and the familiar Provisioned UI, which remains available until September 1, 2026.

• Each instance receives a new regional connection string that provides optimized ingress:

  • Existing connection strings: Provisioned connection strings (without a region) continue to work over the existing inbound Private Link and do not require Service Direct Private Link.
  • New regional connection string: If you use Private Link and connect to Lakebase from outside the Databricks workspace, you must configure inbound Private Link for performance-intensive services to use the new regional connection string.

• To use new autoscaling features such as scale-to-zero in your Declarative Automation Bundles and Terraform configurations, update them to use autoscaling semantics.

• Lakebase GA pricing applies. With elastic compute replacing fixed-size instances, most customers will see a reduction in compute costs.

• The Forward ETL and REST API Private Preview features on Lakebase Provisioned are disabled after the upgrade. Their replacements, Lakebase Change Data Feed and the Data API, are available on the Autoscaling platform.

Lakebase Autoscaling adds autoscaling and scale-to-zero, point-in-time restore and snapshots, maintenance window scheduling, database branching, and other enhancements. For details about what to expect, what changes, and what actions to take, see Upgrade to Autoscaling.

To request an expedited upgrade or if you have questions, contact your account team or Databricks Support.

You can now export Lakebase Postgres metrics and logs to any OTLP-compatible observability backend, including Grafana Cloud, New Relic, and Datadog. Configure the endpoint, authentication, and resource attributes from the Lakebase App. This feature is in Beta.

See OpenTelemetry export.

You can now manage encrypted Lakebase Autoscaling 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.

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

Lakebase Autoscaling 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.
• Lakehouse sync (Beta): Continuously replicate Lakebase Postgres tables to Unity Catalog Delta tables using CDC. See Lakebase Change Data Feed.

New Lakebase instances are now created as Lakebase Autoscaling projects by default. Lakebase Autoscaling is the latest version of Lakebase, with autoscaling compute, scale-to-zero, branching, and instant restore. This default behavior applies when you create new instances using the UI, Database instance API, Terraform, or SDKs. Existing Provisioned instances are unchanged and keep their current connection strings and behavior. To learn more, see Autoscaling by default.

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 Autoscaling 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 Autoscaling is now available in three additional regions:

• ca-central-1 (Canada Central)
• eu-west-2 (Europe – London)
• sa-east-1 (South America – São Paulo)

See Get started with Lakebase Autoscaling.

Lakebase is now generally available. Lakebase Autoscaling and Lakebase Provisioned are now unified in a single UI. GA includes autoscaling, scale-to-zero, instant branching, automated backups, point-in-time recovery, storage up to 8 TB, and expanded region availability.

See Get started with Lakebase Postgres.

Lakebase Provisioned instances are now accessible through the Lakebase App (via the apps switcher in the Databricks UI). The new unified interface consolidates Lakebase Provisioned and Lakebase Autoscaling management in one location, replacing the previous workflow of navigating to the Compute tab in the Lakehouse UI.

Lakebase Autoscaling (Public Preview) now includes a Metrics dashboard for monitoring system and database metrics. See Metrics.

Lakebase Autoscaling (Public Preview) now supports direct connections from the SQL editor with full read-write access. See Query from SQL editor in the workspace.

Lakebase Autoscaling (Public Preview) now supports Access Control Lists (ACLs). Grant CAN CREATE or CAN MANAGE permissions to control who can access and manage project resources. Manage permissions from project settings in the Lakebase App. See Manage project permissions.

You can now connect to Lakebase (Provisioned) readable secondaries and run read-only queries from the Databricks SQL editor. See Execute read-only queries from Databricks SQL Editor and Connect and query a database instance.

Lakebase (Autoscaling) is now in Public Preview on AWS. This new version of Lakebase introduces autoscaling compute, scale-to-zero, database branching, instant restore, and a redesigned project-based interface. To allow users to explore the new version, usage of Lakebase Autoscaling is free for a limited time. Billing for Lakebase Autoscaling usage begins in January 2026. See Get started with Lakebase Postgres (Autoscaling Preview).

Lakebase (Autoscaling Beta) is now available on AWS as a new app in the app switcher, separate from the existing Lakebase Public Preview. This new version introduces autoscaling, scale-to-zero, database branching, instant restore, and project-based organization with a redesigned UI.

See Get started with Lakebase Postgres (Autoscaling Beta).

The OLTP Database tab in the Compute section of the workspace is renamed to Lakebase Postgres. Use this tab to create and manage your Lakebase database instances.

See Create and manage a database instance.

You can now create synced tables in Snapshot sync mode from Iceberg tables or foreign tables.

See Supported source tables.

For newly created synced tables, TIMESTAMP types in source tables are now mapped to TIMESTAMP WITH TIMEZONE in synced tables. In existing synced tables, TIMESTAMP types continue to map to TIMESTAMP WITHOUT TIMEZONE.

See Data type mapping.

You can now tag a database instance and a synced table with a budget policy to attribute billing usage to specific policies. Additionally, custom tags can be added to a database instance for more granular attribution of compute usage to teams, projects, or cost centers.

See Update a serverless usage policy of a database instance, Create a synced table, and Custom tags.

You can now define Lakebase database catalogs, instances, and synced tables in a bundle. This means you can deploy a full database environment with one command instead of setting up resources separately.

When you deploy a bundle with a database instance, the instance starts running immediately.

See database_catalog, database_instance, and synced_database_table.

The Lakebase: Managed Postgres OLTP Database preview is now enabled by default. Users can start creating Lakebase database instances without needing workspace admins to enable this preview first. Admins can disable the preview if needed.

See Create and manage a database instance and Manage Databricks previews.

You can use the Databricks Terraform provider to create Lakebase resources such as database catalogs, database instances, and synced tables. This lets you set up and manage Lakebase resources with infrastructure as code.

See the Terraform documentation and changelog.

Synced tables are now automatically metered and billed. Synced tables use Spark Declarative Pipelines on Lakeflow to sync data from Unity Catalog tables into a Lakebase database instance. All usage is tracked and reported in system.billing.usage.

See Billable usage system table reference and Serve lakehouse data with synced tables (Lakebase Provisioned).

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.

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. For our SOC reports, please ask your Databricks account team or see Compliance.

To deliver Postgres version updates, security patches, and new features to your projects sooner, Lakebase Autoscaling 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 Autoscaling 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.

Starting June 1, 2026, snapshot storage is billable for Lakebase Autoscaling. 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.

New Lakebase Autoscaling projects now have native Postgres password authentication disabled by default. Existing Autoscaling 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 (CMK) for Lakebase Autoscaling are now available in all Lakebase regions on AWS and Azure. CMK encrypts Lakebase Autoscaling project data at rest using a key your organization owns in its cloud KMS. CMK is available for new Lakebase Autoscaling projects. Lakebase Provisioned instances do not support CMK. See Customer-managed keys for Lakebase.

Lakebase Autoscaling 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.

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 Autoscaling 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 Autoscaling projects, see Compute defaults. This change does not affect existing projects.

Lakehouse Sync is now in Public Preview for Lakebase Autoscaling. 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.

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.

Azure Databricks is upgrading all Lakebase Provisioned instances to the Lakebase Autoscaling platform. Upgrades begin in June 2026 for customers who have requested them, with remaining instance upgrades continuing in the following weeks. Workspace admins will receive an email with upgrade dates before the upgrade begins.

The upgrade is automatic. Connections restart briefly during the transition, and existing connection strings, API calls, Declarative Automation Bundles, and Terraform configurations continue to work without modification.

After the upgrade, the following changes apply:

• Your instances will support autoscaling features and can be managed through both the new Autoscaling UI and the familiar Provisioned UI, which remains available until September 1, 2026.

• Each instance receives a new regional connection string that provides optimized ingress:

  • Existing connection strings: Provisioned connection strings (without a region) continue to work over the existing inbound Private Link and do not require Service Direct Private Link.
  • New regional connection string: If you use Private Link and connect to Lakebase from outside the Azure Databricks workspace, you must configure inbound Private Link for performance-intensive services to use the new regional connection string.

• To use new autoscaling features such as scale-to-zero in your Declarative Automation Bundles and Terraform configurations, update them to use autoscaling semantics.

• Lakebase GA pricing applies. With elastic compute replacing fixed-size instances, most customers will see a reduction in compute costs.

• The Forward ETL and REST API Private Preview features on Lakebase Provisioned are disabled after the upgrade. Their replacements, Lakebase Change Data Feed and the Data API, are available on the Autoscaling platform.

Lakebase Autoscaling adds autoscaling and scale-to-zero, point-in-time restore and snapshots, maintenance window scheduling, database branching, and other enhancements. For details about what to expect, what changes, and what actions to take, see Upgrade to Autoscaling.

To request an expedited upgrade or if you have questions, contact your account team or Azure Databricks Support.

You can now manage encrypted Lakebase Autoscaling 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.

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

Lakebase Autoscaling 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 are now created as Lakebase Autoscaling projects by default. Lakebase Autoscaling is the latest version of Lakebase, with autoscaling compute, scale-to-zero, branching, and instant restore. This default behavior applies when you create new instances using the UI, Database instance API, Terraform, or SDKs. Existing Provisioned instances are unchanged and keep their current connection strings and behavior. To learn more, see Autoscaling by default.

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 Autoscaling 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. It is the latest version of Lakebase 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 Autoscaling.

Lakebase Autoscaling, the latest version of Lakebase Postgres, is now available on Azure in Beta. Access the new 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)

See Get started with Lakebase Autoscaling.

Lakebase Provisioned instances are now accessible through the Lakebase App (via the apps switcher in the Databricks UI). The new unified interface consolidates Lakebase Provisioned and Lakebase Autoscaling management in one location, replacing the previous workflow of navigating to the Compute tab in the Lakehouse UI.

You can now connect to Lakebase (Provisioned) readable secondaries and run read-only queries from the Azure Databricks SQL editor. See Execute read-only queries from Azure Databricks SQL Editor and Connect and query a database instance.

The OLTP Database tab in the Compute section of the workspace is renamed to Lakebase Postgres. Use this tab to create and manage your Lakebase database instances.

See Create and manage a database instance.

You can now create synced tables in Snapshot sync mode from Iceberg tables or foreign tables.

See Supported source tables.

For newly created synced tables, TIMESTAMP types in source tables are now mapped to TIMESTAMP WITH TIMEZONE in synced tables. In existing synced tables, TIMESTAMP types continue to map to TIMESTAMP WITHOUT TIMEZONE.

See Data type mapping.

You can now tag a database instance and a synced table with a budget policy to attribute billing usage to specific policies. Additionally, custom tags can be added to a database instance for more granular attribution of compute usage to teams, projects, or cost centers.

See Update a serverless usage policy of a database instance, Create a synced table, and Custom tags.

You can now define Lakebase database catalogs, instances, and synced tables in a bundle. This means you can deploy a full database environment with one command instead of setting up resources separately.

When you deploy a bundle with a database instance, the instance starts running immediately.

See database_catalog, database_instance, and synced_database_table.

The Lakebase: Managed Postgres OLTP Database preview is now enabled by default. Users can start creating Lakebase database instances without needing workspace admins to enable this preview first. Admins can disable the preview if needed.

See Create and manage a database instance and Manage Azure Databricks previews.

You can use the Databricks Terraform provider to create Lakebase resources such as database catalogs, database instances, and synced tables. This lets you set up and manage Lakebase resources with infrastructure as code.

See the Terraform documentation and changelog.

Synced tables are now automatically metered and billed. Synced tables use Spark Declarative Pipelines on Lakeflow to sync data from Unity Catalog tables into a Lakebase database instance. All usage is tracked and reported in system.billing.usage.

See Billable usage system table reference and Serve lakehouse data with synced tables (Lakebase Provisioned).