I’m trying to figure out which direction to go here for a new project. We are configuring an Azure VM for Papercut xerox cloud printing that needs to be accessible to 3 main remote branches. As we are 100% cloud and do not have any on-prem servers, we want to have our first one in Azure. All branches have a Meraki stack with an MX84 and need to have their own S2S VPN connection from their MX84 to the vNet in Azure in order to connect to the server. Researching S2S VPN options has brought me to either using the built-in VPN Gateway option or by using the vMX option. Any recommendations on what’s reliable and simpler to deploy/maintain based on our environment?
Add a vmx, it gives you auto vpn option.
I’ve done both actually. I’d only recommend using a azure vpn if you only need to connect to one location. With multiple locations you’re better off using a vmx and letting it handle all the redundancy and routing.
We have 3 vMX’s in Azure globally that connect our offices in 20 countries. It works great, just configure, set up auto vpn, and make sure your routing table in Azure is updated and good to go
Use the vMX - it’s super easy to setup. It’s simple and creates a VPN hub in your Azure environment.
what is the benefit of auto vpn?
Auto VPN will simplify your vpn deployment from Meraki side, additionally this will make sure that you will bypass the limitations as quoted by Meraki.
“Please note that due to compatibility limitations between the Meraki MX and Microsoft Azure Gateways, site-to-site VPN connections between the MX and Azure VNet Gateways may experience occasional instability. We recommend that customers use the vMX network virtual appliance found in the Azure Marketplace for optimal site-to-site VPN performance, stability, and visibility.”
He just means it will work like a physical mx and connect to all your other mx’s