@ClaytonMeyer wrote: I was told recently, by a Meraki SE, that IKEv2 was in fact supported but was a hidden feature. Correct me if I'm wrong, but doesn't the "S" in "Meraki SE" stand for Sales?   Just sayin'. ... View more

@TimW wrote: Yes, while IKEv1 will work with a single S2S connection, it does not work for multiple S2S connections in Azure. Thanks Tim! As you can probably surmise from my signature, networking is not my forte, but alas here I am. I want to move our (small) office's network domain and Active Directory to Azure so I can retire the dinosaur currently running Windows Server 2008! Will a single S2S connection work for remote employees who currently VPN into the MX in order to access the network? ... View more

@PhilipDAth wrote: You can connect to Azure using a policy based VPN (which can use IKEv1): https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq   But I'm with you - I don't see any reason for the industry to continue to use IKEv1.  IKEv2 is better in every way.  Death to IKEv1 I say! Sorry Philip, I meant to quote the post I referenced above.... ... View more

Hi Philip, I know this post is more than a year old, and while I did see your other post about using StrongSwan to create a Meraki to Azure VPN, the Microsoft documentation for creating a policy-based VPN still mentions requiring a compatible VPN gateway (I'm looking at you Cisco). Are you saying we can ignore that? I am concerned about the expense of adding another VM for the StrongSwan solution.   vin ... View more