Additionally, for some configurations, you'll also need to install root certificate information.įor information about working with certificates, see Point-to site: Generate certificates - Linux. The client certificate you want to use must be exported with the private key, and must contain all certificates in the certification path. Generate certificatesįor certificate authentication, a client certificate must be installed on each client computer. If you're using TLS for point-to-site connections on Windows 7 and Windows 8 clients, see the VPN Gateway FAQ for update instructions.

If you’re using TLS for point-to-site VPNs on Windows 10 or later clients, you don’t need to take any action. Only point-to-site connections are impacted site-to-site connections won't be affected. Starting July 1, 2018, support is being removed for TLS 1.0 and 1.1 from Azure VPN Gateway.

Steps differ, depending on the authentication type, tunnel type, and the client OS. The following table shows the configuration articles available for Azure VPN Gateway P2S VPN clients.

The Azure VPN Client isn't available for macOS and iOS when using certificate authentication, even if you selected the OpenVPN tunnel type for your P2S configuration.īefore beginning, verify that you are on the correct article. Note the following when working with certificate authentication:įor the IKEv2 tunnel type, you can connect using the VPN client that is natively installed on the macOS system.įor the OpenVPN tunnel type, you can use an OpenVPN client. There are multiple sets of steps in this article, depending on the tunnel type you selected for your P2S configuration, the operating system, and the VPN client that is used to connect. This article helps you connect to your Azure virtual network (VNet) using VPN Gateway point-to-site (P2S) and Certificate authentication.

Openvpn mac client install