Unfortunately, the article doesn’t offer any help on how to configure the Azure side, it only suggests to read a Microsoft article that is very generic.
Please, give us a howto document with examples for both sides; otherwise, it is worthless.
In our reference architecture and companion deployment guide, we do not typically recommend terminating the VPNs on the Virtual Appliance running in Azure. This is b/c you will need to use SNAT to enforce return path routing through the proper firewall to prevent asymmetric routing as we cannot extend BGP from the firewalls to the Azure Route Table. Instead, you may consider terminating the VPN on the Azure VPN Gateway and use our backhaul routing design to force all traffic to and from the Gateway subnet through the firewall utilizing UDRs and the Load Balancer.
We are currently working design to use Azure as DR site. We stuck at the connectivity from our remote sites to Azure as all our remote sites are having ADSL connections with dynamic Public IP address which is not supported by Azure VPN Gateway.
We through for using Palo Alto firewall at Azure for on-premise connectivity but after looking at this discussion we have to rethink for that.
Can someone advise the best way to go? Alternate option is we can migrate our ADSL connections to Managed ADSL connection on which we will get single static public IP address, however additional operational cost involve in this option we are keeping this as a last option.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!