Allow custom/CIDR ranges for deploying Databrick in VNET
Current ARM template and implementation of Databricks being deployed in VNET only allows /16 CIDR before deployment and does not allow manipulation to shrink /16 CIDR after deployment. This is a huge problem in larger enterprises where a /16 takes up 64k IPs and VNET technology only allows 8192 MAX Private IPs in a VNET. This presents a challenge for enterprises carving huge swaths of /16 space especially when WAN routing comes into place for the organization. The ability to define and deploy your own VNET with a /22 or other /CIDR range should be allowed.
Murtaza Kanchwala commented
It would also be nice if I could specify which range to use in stead of just using 10.139.0.0/16. I can't use the peering option anymore if for example some other iaas service already has a range in 10.139.0.0/16
Agreed. No reason for any single application to take an entire /16