I have successfully established a site-to-site VPN connection to my Azure subscription and it is operational. I am trying to expand access to additional networks on the "Local" (premise) side of things and when I attempt to edit the "Local Network" for my virtual network I keep getting the same error “Cannot delete or modify virtual network while in use ‘name of the virtual network’”
The VPN gateway for the local (premise) network is 176.169.50.57 I would like to add subnets 176.169.49.0/24 and 176.169.128.0/25. I have found documentation that states that the network address space for the virtual network can only be the non-routable networks (192.168.0.0, 10.0.0.0, and 172.16.0.0), but nothing that state that this same restriction is in place for the local (premise) network. I have successfully added subnets to the local network from all three of the non-routable networks listed above, but fail when we try to add addresses from any other subnets.
Thoughts? We are evaluating Azure for use in our environment and the networks we are trying to add are for our workstations so that they can access resources we are planning to place in Azure.
UPDATE - deletion and recreation of virtual network appears to be the only way that this can be done. Created a test virtual network with valid but bogus IP address information. Was able to fully edit "Local Network" settings before gateway was created, but once done, the portal only allowed me to add networks in RFC1918 definition. Did not test if those additions were actually valid from a routing perspective. Executed procedure on real environment and was able to make necessary updates.
Strongly recommend that the interface be modified to allow dynamic editing of these values without being forced to delete the entire virtual network. We had several virtual machines defined which ad to be deleted to release their hold on the virtual network so it could be deleted. Network environments are somewhat dynamic and I can't imagine having to do this in a production environment.