I've deployed a vMX100 through the Azure CSP workaround template method and while it is still a problematic deployment since it creates a resource group outside of the desired resource group for the Pub IP, Disk, and NIC while putting the VM resource in the desired Resource Group which breaks some of the reporting tools in Azure but I digress. The vMX100 is not a Virtual MX100. I've never been led to believe that the vMX100 was anything but a "Virtual MX100". The functionality is not the same, there is no "Security Center", no L7 rules for blocking by country, no L3 rules for blocking by service, the 1:1 NAT rules are not managed from the Meraki but rather through Azure (which is not made clear in the vMX documentation). Why call it a vMX100? Why is the documentation for the vMX100 linked with the MX100 when they are not deployed the same, managed the same or even share functionality? What gives Meraki? My Cisco ASAv is a "Virtual ASA" and I can have my ASA team manage it like an ASA. I'm having a hard time finding value in the vMX100 and especially around the Meraki support around that virtual device. ... View more