I started creating a route-based VPN today. After building the virtual gateway, someone tells me that a policy-based VPN connection is better.
When creating a virtual network gateway, is it best to use a route-based or policy-based VPN?
When I select policy-based VPN, I see a pop-up stating that the policy-based VPN is only compatible with IKEv1, and the only SKU choice I have is basic. The public IP address automatically switches to dynamic and is grayed out.
Looking at the gateway SKU table, I see that the basic SKU is limited to 100 Mbps. I do not appear to have the option to select a static IP when I create a VPN gateway using policy-based routing. Do I need to create a static public IP before creating the policy-based VPN so I can choose to use the existing public IP?
Could a route-based VPN gateway with a custom IPsec/IKE policy perform similarly to a policy-based VPN gateway?
I have read: