Top 10 Networking Features in Windows Server 2019: #3 Azure Network Adapter

Jorrit055

Thanks for your try-out and reply.

There is no specific inbound or outbound firewall rules required. 

From the error message there could be two potential issues here - 

1.  The created Azure Virtual Network Gateway "WACVPN-22148" is not a "Gen 3" Gateway, you can contact the support to confirm the gateway is "Gen 2" or "Gen 3". Or you can simply download the P2S VPN Client of this gateway from the Azure portal, then manually install it on the server. If you can successfully made the P2S VPN connection, then this Gateway is "Gen 3" otherwise it's "Gen 2". And the Azure support can upgrade it to "Gen 3".
2.  Most likely, the issue could be caused by the IKEV2 micro-segmentation bug in Windows. Currently the bug has not been fixed in Windows Server 2016 (or we call it RS1) yet. The bug has been fixed in RS3+ and Windows Server 2019. The issue should be fixed soon in Windows Server 2016. 

Hope it helps. Thanks very much!