>Since I had two vMX for each org,  I was told to deploy first in AZ1 and second in AZ2 for high availability. if I select NONE   If you found it unreliable and intermittently had to restart the VMXs to get AutoVPN going again - would you call that compromised HA?  Because that is what you'll experience if you use availability zones.   Actually, since you have two VMX for each org the static route approach is more complicated.  You will have to use this approach: https://documentation.meraki.com/MX/Other_Topics/Deploying_Highly_Available_vMX_in_Azure  What this does is monitor each VMX and updates the static routes in Azure should one fail.  Note that the Meraki instructions and the Azure instructions both contain serious grevious errors, and it is quite difficult getting this approach working if you have not done it before (you need to be able to figure out, correct and work through the documentation errors).   You'll need a supernet static route in Azure pointing to a VMX from each org for the branches that sit behind that VMX.   This is where you add the subnets located in Azure in the VMX (you'll need to do this on all VMXs).  You'll also need to add routes here for the branches sitting in the other org.   You are much better off configuring the BGP approach: https://documentation.meraki.com/MX/Deployment_Guides/vMX_and_Azure_Route_Server      So be warned.  This is doable, but it is going to be labour-intensive, complex, and it is going to need a good head when running into documentation errors and figuring out what the correct approach is. ... View more