One of your colleagues deployed a new virtual network (VNet) named corp-vnet that has the following properties:
* Address range: 172.16.0.0/16
* Front-end subnet: 172.16.2.0/24
* Mid-tier subnet: 172.16.3.0/24
* Back-end subnet: 172.16.4.0/24
To avoid a conflict with your on-premises IPv4 address space, you need to change the corp-vnet address space to 192.168.0.0/16 and redefine the subnet IDs immediately, before your colleague attempts to migrate virtual machines (VMs) to the new VNet.
What should you do?
You should remove and redeploy corp-vnet. Azure VNet address ranges cannot be modified. Furthermore, deleting an address range requires first removing any associated subnets. Therefore, in this case it makes the most sense simply to remove the entire VNet and redeploy it.
You should not add the 192.168.0.0/16 address space to corp-vnet. Azure VNets do indeed support more than one non-overlapping IPv4 address space. However, doing so does nothing to resolve the problem outlined in the scenario.
You should not delete the three subnet resources from corp-vnet. Performing this action is a necessary first step to delete the address range, but as previously discussed, it is most time-efficient simply to delete the entire VNet and redeploy it by using the Azure portal or another management tool.
You should not edit the corp-vnet address range to 192.168.0.0/16. This operation is not supported in Azure Resource Manager.