(Posting on the forum to alert the issue and impact)
An issue on Azure P2S (Point-to-Site) VPN was found last week that could prevent customers from using Azure P2S VPNs.Note that P2S is a CTP feature and should not be used for production workloads.
- Impact:
- For the affected P2S VPN gateways (DynamicRouting Gateways), customers will not be able to connect their VPN clients to their Azure VPN gateways
- The S2S VPN tunnel on the affected gateway is NOT impacted – so S2S VPN tunnels for DynamicRouting gateways will continue to work
- (StaticRouting gateways are NOT affected by this issue)
- Mitigation:
- Customers with affected P2S VPN gateways should delete and recreate their VPN gateways, then download/install the VPN client installation packages again. This should mitigate the issue.
- The potential side effect is that their VPN gateway VIPs (public IP addresses) may change. If they also have S2S VPN tunnels on the same gateways, they may need to update their VPN configuration to connect to the new VIPs.
- Fix:
- The product team is working on a hotfix to this issue. We will roll this out as soon as possible.
Apologize for the inconvenience. Please contact me if you have any questions.
Thanks,
Yushun Wang [MSFT]