That's right. Thanks for clarifying ... View more

Another issue we found:  Please NOTE if the vMX will be doing 1:1 NAT port forwarding then the server subnet cannot be a part of Secure Connect. When you enable a subnet to traverse the tunnel via Secure Connect then this breaks any 1:1 NAT port forwarding rule configured in the Meraki Dasbhoard as that traffic is not sent out the local WAN anymore but over the AutoVPN tunnel to Secure Connect. So in order to do this you would need whatever server/devices that need the port forwarding to be disable from VPN participation. ... View more

Ok, got it working. I had to create the LAN subnet before Meraki deployment, not during deployment. Same goes for the WAN subnet. Thanks!  ... View more

I think that's what I tried but I got an interface error: "error": { "code": "InvalidResourceReference", "message": "Resource /subscriptions/c3417xxx/resourceGroups/TEST-Meraki-vMX/providers/Microsoft.Network/virtualNetworks/TEST_vMX_vnet/subnets/lan-subnet referenced by resource /subscriptions/c3417exxxxc/resourceGroups/mrg-cisco-meraki-vmx-20250422171814/providers/Microsoft.Network/networkInterfaces/TEST-AZ-FWLanInterface was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.", "details": [] } } ... View more

Hey ShaunB93, I'm trying to deploy the Meraki vMX in routed mode, but I'm running into issues installing version 19.1 from the Azure Marketplace. Could you share how you went about deploying it or if there’s a specific workaround you used? Thanks in advance! ... View more

Hi Shaun - Great POC.....I'm wondering if Azure Route Server is a requirement, or you could accomplish the same with UDR for smaller setups? Also, what do you mean by "Traffic Interruption" when making changes to vMX? What kind of changes can cause that? Thanks in advance! ... View more