Per-workspace URLs

In April 2020, Azure Databricks added a new unique per-workspace URL for each workspace. This per-workspace URL has the format


The per-workspace URL replaces the deprecated regional URL (<region> to access workspaces.


Avoid using legacy regional URLs. They may not work for new workspaces, are less reliable, and exhibit lower performance than per-workspace URLs.

Launch a workspace using the per-workspace URL

In the Azure portal, go to the Azure Databricks service resource page for your workspace and either click Launch Workspace or copy the per-workspace URL as displayed on the resource page and paste it into your browser address bar.

resource page

Get a per-workspace URL using the Azure API

Use the Azure API Workspaces - Get endpoint to get workspace details, including per-workspace URL. The per-workspace URL is returned in the properties.workspaceUrl field in the response object.

Migrate your scripts to use per-workspace URLs

Azure Databricks users typically write scripting or other automation that references workspaces in one of two ways:

  • You create all workspaces in the same region and hardcode the legacy regional URL in the script.

    Because you need an API token for each workspace, you also have a list of tokens either stored in the script itself or in some other database. If this is the case, we recommend that you store a list of <per-workspace-url, api-token> pairs and remove any hardcoded regional URLs.

  • You create workspaces in one or more regions and have a list of <regional-url, api-token> pairs either stored in the script itself or in a database. If this is the case, we recommend that you store the per-workspace URL instead of the regional URL in the list.


Because both regional URLs and per-workspace URLs are supported, any existing automation that uses regional URLs to reference workspaces that were created before the introduction of per-workspace URLs will continue to work. Although Databricks recommends that you update any automation to use per-workspace URLs, doing so is not required in this case.

Find the legacy regional URL for a workspace

If you need to find the legacy regional URL for a workspace, run nslookup on the per-workspace URL.

$ nslookup adb-<workspace-id>.<random-number>

Non-authoritative answer:
adb-<workspace-id>.<random-number> canonical name =