1. Create a virtual WAN resource. After creating, verify if deployment is complete:
2. Create a P2S configuration. On the virtual WAN you created. Select Create user VPN config at the top. Follow along default or recommended prompts but on the Public Certificate Data, choose: Base-64 encoded X.509 certificate data.
3. Create a virtual hub and for the DNS server, it is optional unless you need to reference your own or internal DNS.
4. Generate and download the VPN client profile configuration package. This is the zip archive where you will need to extract the vpnconfig.ovpn to be filled up with certificate parameters.
5. Configure VPN client(s) using OpenVPN.
– Download and install the OpenVPN client.
– Unzip the VPN profile config package you downloaded from your WAN. Open the vpnconfig.ovpn configuration file in notepad and fill in the P2S client certificate section with the P2S client certificate public key in base64. You can open the .cer file and copy the base64 key. Click here to see how to export a certificate to get the encoded public key. Fill in the private key section with the P2S client certificate private key in base64. Then afterwards, copy this vpnconfig.ovpn file to C:\Program Files\OpenVPN\config folder, and right-click the OpenVPN icon and select connect or simply hover to app and click to execute.
6. Ways to verify that OpenVPN client is now connected to remote WAN.
– Succeeded hub status on your Azure WAN overview panel:
– OpenVPN icon with green led on your computer status bar:screenshot: Taskbar icon showing OpenVPN with greed led
– Client connected on WAN->Hub panel:
– Command prompt ipconfig /all: