@patbeautz  if it can help this is what we did at our side... I created a new network in Meraki Dashboard; Retrieved the Token to deploy a new Meraki v-MX-M Deployed a new v-MX-M in the same vNet of the v-MX-100, in Azure I originally planned to reassign the IP of address of vMX-100 to the new vMX-M, but this operation was not possible because of the restriction o the Meraki Managed App deployed. I then managed to adjust the routing by modifying the Routing Table in our vNet I deleted the vMX-100 resources group in Azure and removed the vMX-100 from our Meraki dashboard. This action 6. Triggered a downtime of about 30’ during which all our sites could not connect to Internet, even though all VPN were ok. After 30’ (apparently a sync of all routes) everything went back to normal, Documentation is rather poor and support is lousy. It's a pity, because I am a great fan of Meraki on a day to day basis, but on those days I have a different opinion 🤷‍♂️ ... View more

We went through the same pain, after discovering the hard-way (at licenses renewal) that we were obliged to upgrade a vMX-100 to a vMX-M (which on Azure are equivalent, after Meraki doc) and when asked for support we were also bounced back to Azure support. ... View more

I can't agree more on your comment about Meraki communication quality. Meraki support bounced me back to Azure support! And their documentation is also confusing: 1) they talk about an upgrade but in fact in Azure you have to redeploy all the resources and network configuration. 2) Quote from vMX100 to vMX S/M/L Transition FAQ - Cisco Meraki What is the difference between vMX100 and vMX-M? vMX-M supports AWS C5 and its additional regional support. vMX100 and vMX-M are equivalent in Azure.   If they are equivalent why on earth should we allocate time in redeploying resources.. What a waste of time. Nicola ... View more