Lakebase in an enterprise setup

Lode — Thu, 09 Apr 2026 08:08:51 GMT

Hi,

Has anyone managed to get the new Lakebase autoscaling fully working in an enterprise Azure setup?

We are currently facing issues when setting up Lakebase autoscaling in a Databricks environment without a public IP, where all traffic is routed privately. We followed the Databricks documentation and configured private endpoints for service direct.

Our Databricks compute can successfully connect to Lakebase using a connection string, and the same applies from machines on our office network. So overall, connectivity is working. However, the problem appears specifically in the Lakebase UI.

When opening the tables view or using the SQL editor in the Lakebase view within the Databricks workspace, the traffic seems to be routed through a non-private endpoint.

What is working:

Accessing Lakebase from notebooks on shared clusters
Accessing Lakebase from serverless notebooks
Accessing Lakebase from our office network
UI features such as branching, creating credentials, and spinning up new Lakebase projects

What is not working:

Tables view and SQL editor in the Lakebase UI

From browser inspection, we see a 403 error on a POST request to:
https://api.database.westeurope.azuredatabricks.net/sql

I have attached:

The error message from the Databricks workspace (tables view)
Network requests from Chrome DevTools showing the failing call

Any ideas what could be missing or misconfigured?

topic Lakebase in an enterprise setup in Administration & Architecture

Lakebase in an enterprise setup