really strange and I am not sure if it is a limitation somewhere with Meraki, but when i decreased the address space from /22 to a /23 and updated accordingly in Meraki the tunnel came up. ... View more

Thanks for the reply. Gateway is route based. i tried a few different things.. starting simple with: Azure side: default setting on the gateway connection. Meraki: Azure policy (with Meraki support enabling IKEv2 on the back-end) this resulted in the tunnel showing as connecting in azure and as establishing and tearing down on Meraki side.   After a call to Meraki, they informed me that IKEv2 is hard set to 3600s lifetime on their side on both phases and I need to match that in Azure, they also recommend that I hard specify an encryption algorithm on Azure side, which I did by creating an ipsecpolicy via powershell with AES256 SHA1 dfgroup 2 for phase 1 and AES256 SHA1 no PFS for phase 2. this unfortunately had the same result.     ... View more

Hi, would you mind sharing what exact configuration did the trick.. on both MX and Azure end. In our lab we have an MX64 with the 15.13 beta firmware and IKEv2 enabled. I've worked with Meraki and MS support but still no dice. ... View more