My apologies for not replying with my solution. My deployments were being blocked by Azure security polices that our cloud services team implemented without my knowledge, that probably doesn't help too many people but something to look out for. @patw-agr, I am using the vMXs coupled to Azure vWAN so not entirely sure this applies to your situation. My vMXs are deployed by setting the Azure NIC to static with the private IP address and the associated public IP address. In the Meraki portal, on the vMX local status page, uplink I have the WAN interface set for 'Auto'. That is picking up DHCP Azure settings of the static IP I set and then default gateway and DNS (Azure wire server - 168.63.129.16). The vMXs are BGP peered to vWAN so I just have to make sure that the proper routes are propagated to the remote site so they can access the DNS servers, in Azure, that the remote offices have configured in DHCP. This works flawlessly, I hope it gets you to some sort of resolution for your situation. -Grant ... View more

I had only tried the DNS setting on the 'DNS Servers' on the VNet blade in Azure and only added 8.8.8.8. Meraki support has passed this off as an Azure problem but I am going to try setting the DNS on the local status page and see what happens. I also spotted in the deployment guide under (Re)deployment failure: A few common fixes for (re)deployment failures could be: • updating the VNET DNS settings <-- Already tried this • removing any special characters in the name of the vMX <-- I do have dashes in my naming convention so this might be the smoking gun. Thank you both for the suggestions! ... View more