Palo Alto may want to expedite this feature request because I just received a call from one of our customers who stated that to become PCI compliant, they are required to use IKEv2. They are using Cisco ASA's.
Just hit this brick wall when trying to move our Azure VPNs from a Juniper to the Palo, no IKEv2??? The Junipers are 7 years old and they have it. Really stuck now, looks like our old Junipers are going to have to stay running just for these VPN's. We used IKEv1 with Azure but had countless problems and changed after a long support case with MS so going back really isn't an option.
Hi, we can get it to work with IKEv1 but the link is not reliable, it kept dropping at the MS side. In the end after lots of testing with MS their only solution was to change to IKEv2 which has not failed yet.
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!