To learn how to migrate to the Az PowerShell module, see Migrate Azure PowerShell from AzureRM to Az.
To get started with the Az PowerShell module, see Install Azure PowerShell. This article uses the Azure Az PowerShell module, which is the recommended PowerShell module for interacting with Azure. PowerShell Resource Manager deployment model Resetting the gateway will cause a gap in VPN connectivity, and may limit future root cause analysis of the issue. Once the command is issued, the current active instance of the Azure VPN gateway is rebooted immediately. On the page for the virtual network gateway, select Reset. In the portal, navigate to the virtual network gateway that you want to reset.
If you want to reset a classic gateway, see the PowerShell steps for the Classic deployment model. You can reset a Resource Manager VPN gateway using the Azure portal. If you apply specific IPsec/IKE configuration, such as encryption, hashing algorithms, and PFS (Perfect Forward Secrecy), ensure both the Azure and on-premises VPN gateways have the same configurations.The pre-shared key must be the same on both Azure and on-premises VPN gateways.The Internet IP addresses (VIPs) for both the Azure VPN gateway and the on-premises VPN gateway are configured correctly in both the Azure and the on-premises VPN policies.Verify the following items before resetting your gateway: Verifying and correcting the configurations for your on-premises and Azure VPN gateways saves you from unnecessary reboots and disruptions for the other working connections on the gateways. Any mismatch in the items will result in the disconnect of S2S VPN tunnels. On the Reset page, click Reset to reset the connection.īefore you reset your gateway, verify the key items listed below for each IPsec Site-to-Site (S2S) VPN tunnel. On the Connection page, select Reset from the left menu. You can find the connection resource either by locating it in All resources, or by navigating to the 'Gateway Name' -> Connections -> 'Connection Name' Navigate to the Connection that you want to reset. You can reset a connection easily using the Azure portal. Only the selected connection is reset and restored. When you select to reset a connection, the gateway does not reboot. This will cause a longer gap on the VPN connectivity, up to 30 to 45 minutes for VMs to complete the reboots.Īfter two reboots, if you are still experiencing cross-premises connectivity problems, please open a support request from the Azure portal. If the two reboots are requested back to back, there will be a slightly longer period where both VM instances (active and standby) are being rebooted. If the connection is not restored after the first reboot, issue the same command again to reboot the second VM instance (the new active gateway). There will be a brief gap during the failover from the active instance (being rebooted), to the standby instance. When you issue the command to reset the gateway, the current active instance of the Azure VPN gateway is rebooted immediately.
This means you won’t need to update the VPN router configuration with a new public IP address for Azure VPN gateway. The gateway keeps the public IP address it already has. When you reset the gateway, it reboots the gateway, and then reapplies the cross-premises configurations to it. What happens during a reset Gateway resetĪ VPN gateway is composed of two VM instances running in an active-standby configuration. This article helps you reset a VPN gateway or gateway connection. In this situation, your on-premises VPN devices are all working correctly, but are not able to establish IPsec tunnels with the Azure VPN gateways. Resetting an Azure VPN gateway or gateway connection is helpful if you lose cross-premises VPN connectivity on one or more Site-to-Site VPN tunnels.