Can I Change a Gateway Tunnel Type Without Affecting Current VPN's

Sapphire2022 1 Reputation point

I have a client moving to Azure and we are in the final stages of testing. Currently I have a SKU VPNgw1 vnetgateway in the East US 2 region, setup with an IKEv2 tunnel type. I have set this up for about 15 people, after testing with a small group. We now have one Apple MAC that simply will not let us use the child certificate for the VPN. The certificate says it installs, but when we go to setup the VPN, it does not display in the drop down list. We've tried a bunch of different things, but I figured we could try using OpenVPN with a OpenVPN compatible client, but the vnetgateway is only set to IKEv2, not "IKEv2 and OpenVPN".

The current P2S tunnel type is set to IKEv2. Can I change the tunnel type to "IKEv2 and OpenVPN" without disrupting or having to reconfigure currently existing IKEv2 client connections.

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,362 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. GitaraniSharma-MSFT 46,761 Reputation points Microsoft Employee

    Hello @Sapphire2022 ,

    Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

    You can change the tunnel type of your Azure P2S VPN configuration from "IKEv2" to "IKEv2 and OpenVPN" without having to reconfigure existing IKEv2 client connections. However, when you select the new tunnel type on the P2S config and hit save, it will disconnect any active P2S VPN sessions for a minute. The tunnel type change will hardly take a couple of minutes and the users can re-connect immediately after the disconnect. Hence, you can prepare for the change accordingly.

    Kindly let us know if the above helps or you need further assistance on this issue.


    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments