You don't need to add anything to maintain internet access on your VMs besides a NAT gateway on their VNET or assign a public ip to the VM. That's it. If you want a control point and further firewalling that's a different story, but you don't need any of that. If you don't have anything now, you add one of the above items and you are all set for now. You are otherwise asking a bunch of detailed design questions, to the point where I suggest you involve your Meraki or Partner Rep. https://documentation.meraki.com/MX/MX_Sizing_Information/MX_Sizing_Principles is somewhere to start on your capacity questions. https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Firewall_Logging https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Event_Log for your logging questions Geo Blocking is available via Layer 7 rules https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_a_Layer_7_Firewall_Rule Regardless, I strongly recommend getting a rep involved who can engage an engineer. 10 VMs is quite different from 200 and IMO 200 servers in azure is where you should be looking at other solutions for outbound firewalling. Might still want vMX for branch connectivity, but A server environment that big is going to ahve needs that an MX is not great for in my experience.
... View more
