well actually i did not consider that option as the this is in azure, and I am not sure this scenario would be supported? at least not as an active-active solution as described on the link you mentioned - I guess this requires shared IP on the MXs? which I don't think is supported in Azure...   However of course I could deploy 2, and manually control which spoke connect to which hub (each set of spokes with their own supernet) - and create routes in azure for these supernets, to their respective vMX hub ... View more

Thanks for clarifying - I guess I have to be a bit more forward thinking then 😉 ... View more

thanks for your reply, however I don't see anything in the deployment guide for Azure, in regards to choosing a specific VM size, depending on the license level - therefore it would make sense to me, if this is just a question of the license applied which limitations is enforced - and thus also possible to upgrade.   Hopefully someone from Meraki will answer this thread, to shed some light on this matter... ... View more