vMX in Azure as standalone appliance - VPN issues

[DocMartin]

Does the vMX require a Meraki MX appliance in a VPN to function correctly? 

I have deployed a vMX in Azure. I have no other MX appliance at present (there will be in the future but at this point in time its just the vMX).  I wanted to setup a site to site vpn to a non meraki peer but this won't connect. Also I tried setting up Remote Access Client VPNs but these won't connect either.  Packet capture shows traffic coming to the meraki on ports 500 and 4500 from the Clients when they attempt to connect but seems to be encrypted mostly. The client just gets the error that the remote host isn't responding. 

[PhilipDAth]

I haven't tested either of these two cases, but I would have expected it to work.

[DocMartin]

Just an update for anyone else having the issue

The client VPN was due to this issue

https://documentation.meraki.com/MX/Client_VPN/Guided_Client_VPN_Troubleshooting#Windows_Error_809

Had to enter the registry key in as a 32bit value (and remove the 64bit one). 

Site to Site VPN is working now. IKEv1 but one side (the MX appliance) needed a remote ID (of the vMX internal IP).