Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This page includes subnet sizing information for admins deploying new workspaces. The size of your workspace's subnets determines the maximum number of Azure Databricks compute nodes that can run in the workspace at the same time.
Subnet requirements
If you deploy your workspace in your own Azure virtual network (VNet injection), the VNet needs two subnets dedicated to the workspace: a container subnet and a host subnet. For the full list of VNet and subnet requirements, see VNet configuration.
Use a CIDR block between /16 and /24 for the VNet and a CIDR block up to /26 for the two subnets. You can create a CIDR block up to /28 for your subnets, however, Azure Databricks does not recommend a subnet smaller than /26.
Each cluster node uses one IP address in each subnet: one for the host in the host subnet and one for the container in the container subnet. Azure reserves five IPs in each subnet, so the maximum number of nodes in a workspace is the number of IP addresses in a subnet minus five.
Subnet sizes are expressed in CIDR notation. For more guidance on planning your address space, see Address space guidance.
Quick sizing guideline
Use the following table to estimate the maximum number of Azure Databricks cluster nodes your workspace can support based on the VNet and subnet size.
| VNet size (CIDR) | Maximum subnet size (CIDR) | Maximum Azure Databricks cluster nodes |
|---|---|---|
/16 |
/17 |
32,763 |
/20 |
/21 |
2,043 |
/24 |
/25 |
123 |