I know its an old question, however we had the same problem where we wanted to provide the users the possibility to use their known credentials they used from Office 365. In Azure we enabled Domain services. After that we could just use their accounts by saying to Meraki we had AD.   Btw... Azure Domain Services will cost you about 93 euro per month  🙂   ... View more

I'm now in the same boat as you. I just deployed a vMX-M and I can't hit the outside interface to make a VPN connection. I'm on hold with Cisco, but I've deployed at least 5 of these and haven't had this issue. ... View more

You can do multiple S2S VPNs from Azure, the VPNs just have to be to different Meraki networks/sites. I'm not sure what you'd achieve with multiple S2S VPNs to the same site, unless you're looking at redundancy to different Azure regions? You can also achieve the HA configuration across regions with the vMX now, so that's an alternative. Have a look at these two documents.   https://documentation.meraki.com/MX/Site-to-site_VPN/Configuring_Site_to_Site_VPN_tunnels_to_Azure_VPN_Gateway   https://documentation.meraki.com/MX/Other_Topics/Deploying_Highly_Available_vMX100s_in_Azure   ... View more

Hi RubenL   Only one tunnel ... View more

Route based is the Default in Azure Just click on your Dashboard and search for "Virtual Network Gateways"  click ADD Choose your subscription, name the gateway, make sure you choose correct region and put the gateway in same resource group as your Vnet (keep it easy).  SKU can be standard or VpnGw1 << is better than you can modify later. under Virtual Network choose the Vnet you want to put the VPN on. Create new public IP and wait for like 20 minutes it takes a bit. you will have to create a Root Certificate and User Certificates for IKE SSTP this one is tricky to manage if you want a cert for each user.  There are guides out there but its not difficult to setup. I configured mine for Radius Authentication. FYI policy based is the IKE_v1 we dont want that !!!   ... View more