Allow Static Public IP's on Virtual Network Gateways
Static Public IP's cannot be used with Virtual Network Gateways. This can potentially be very problematic if a Virtual Network Gateway ever needs to be re-created or re-provisioned.
Example: what if we have 30 separate tunnels to a Virtual Network Gateway and it needs to be re-created or re-provisioned? This would result in a new Public IP being provisioned (takes about 30-40 minutes - of downtime!) which would require 30 remote VPN Administrators to be engaged to rebuild their side of the tunnel. This could be easily resolved by allowing Static Public IP's to be associated with Virtual Network Gateways.
Furthermore, if this feature is implemented, it should be done in such a way that allows existing VNG's to set their Public IP to static WITHOUT requiring the IP to change. Example: If we have 20 VNG's in 4 separate regions when you implement the feature, it would not even be feasible for us to use the feature if we will lose our existing IP when setting it to static.
Eric Scheffler commented
FWIW I've done some basic testing on this and simply manually assigning a static IP to the virtual VPN NIC/TAP adapter on the VPN client seems to work fine. In my case I'm using the OpenVPN client to connect to the Azure VPN gateway; the IP address you assigned even shows up as "In Use" on the portal, so this might be an acceptable workaround until this is implemented.
Microsoft is SUCKS, this is happening with me and i need to delete the VNGW for some sort of unknown reason (stuck in failed status).
they should allow static IPs for VNGW !
AWS is long better that AZURE !!!!