Azure VPN Gateway - enabling/disabling Gateway Private IPs issue

Question

Hi, during some tests I have tried to enable Gateway Private IPs only to see that taking almost a full hour without completing so I have cancelled that deployment. Now when I try to disable Gateway Private IPs that fails every single time. Since this is a future production Azure VPN Gateway I want to have Gateway Private IPs disabled and, in general, to have everything clear here. Currently I can not say if Gateway Private IPs are truly enabled or disabled since first deployment (to enable them) was cancelled and all subsequent deployments (to disable them) failed - I simply do not believe Azure Portal.

I really do not understand why initial change (to enable Gateway Private IPs) took so long (even longer than Azure VPN GW creation in the first place - it was very suspicious to me hence I have cancelled that (having been waiting for almost full hour)). If I need to create everything from scratch (including removing all VPN connections first) that is something I'd never do.

What can be done here? Thank you in advance.

Answer 1

The cancelled operation can leave the portal uncertain, but the resource-provider value—not the toggle—is authoritative. Query the gateway with az network vnet-gateway show for enablePrivateIpAddress and provisioningState. If state is Succeeded and the private-IP value is false, no rebuild is needed.

If state is Updating, avoid more changes and let the long-running update finish; Microsoft’s CLI can wait until provisioningState is Succeeded. If it is Failed, review Activity log and the deployment operation for the exact Network resource-provider error and correlation ID. Then issue one explicit az network vnet-gateway update with enable-private-ip false, and wait for completion before changing anything else.

Deleting connections or recreating the gateway is not a normal prerequisite. If the update repeatedly fails or never leaves Updating, open an Azure networking support request with the correlation ID because Microsoft must clear a stuck control-plane operation.