Here is the issue: the far end firewall (near end is your meraki) has an IP on the interface that receives the VPN connection (the WAN interface) that is not the Public IP that the near end/meraki is connecting to (this can be because the far end firewall is double-NATed, etc) you will put the interface ip of the far end firewall as the "Remote ID" on the meraki vpn config   for example   far end: ASA in Azure, with interface IP (WAN) of 10.20.30.40, and azure public ip "resource" of 55.66.77.88   near end: meraki, vpn config with public ip = 55.66.77.88 remote id = 10.20.30.40   Normally the remote id is assumed to be the remote public ip, but if the interface ip is not the public ip, you will have to specify the interface ip as the remote id ... View more