Databricks Networking

[Thabang]

Currently our workspace has almost reached its maximum IP capacity, and we would like to create additional compute resources to handle memory intensive tasks. In doing some research we have been running into some conflicting answers, so I wanted to ask directly if it is possible to do either of the following to a Databricks workspace on Azure:

1) Is it at all possible to detach a Databricks workspace from its existing subnet and move it to a larger Subnet?
2) Is it possible to increase the size/s of a subnet of an existing azure Databricks workspace?

[-werners-]

Hi,
we had the same issue a few years ago, and we had to create a new workspace linked to a larger subnet because at the time it was not possible to move to another subnet (or change the existing subnet).

This was about 2 or 3 years ago. I think this is possible in the mean time by using vnet injection:
learn.microsoft.com/en-us/azure/databricks/security/network/classic/update-workspaces

[Thabang]

Thank you for the response!

The issue with this is that our Databricks workspace was created within a Vnet and not the managed Vnet that you would typically get and so I do not think Vnet injection is possible in this instance. We may be forced into creating a new workspace and linking it to a larger subnet.

[Louis_Frolio · Accepted solution]

Greeting @Thabang , I did some digging and there are potential mitigation paths, but they’re fairly involved and not something you’d want to tackle solo. The guidance consistently points to engaging Support—you’ll definitely need their help to do this safely and correctly.

To give you a sense of the level of effort, here are a few high-level indicators:

Short answers

1. Moving a workspace to larger subnets

   Detaching a workspace from its current subnets in order to move to larger ones is now supported for VNet-injected Azure Databricks workspaces via the new “Update workspace network configuration” flow (Public Preview). You can either replace the existing subnets in place with larger ones or move the workspace to an entirely new VNet with larger subnets.

This operation requires a maintenance window and must be performed through the Azure portal using a defined sequence of steps. Terraform does not support this flow yet.

If the workspace uses back-end Private Link, you’ll need to recreate the Private Link configuration and associated DNS records after the move.

2. Expanding an existing subnet

   Increasing the size of an existing subnet is possible for VNet-injected workspaces, but only if the VNet has sufficient contiguous free address space. In that case, Azure can expand the subnet, and Databricks must update the workspace’s network metadata so the newly available IPs are recognized.

This is not a self-service operation today. It requires coordination with your Azure Databricks account team or support and involves downtime.

Hope this gives you a bit more insight.

Cheers, Louis