So a early morning call to Meraki support got me talking to a engineer in the US. They were much helpful than the Sydney guys.   Basically if you don't create a new RG and vNET, it just doesn't work. We had an existing vNet that we wanted to use but had to create another one. Luckily we hadn't started using the existing vNet so we were able to leverage the Meraki created vNet and create additional Subnets for our infrastructure. ... View more

How are you looking now? I still have an active ticket open with Meraki but the engineer says I have to contact Azure. Really getting sick of the blame game. ... View more

Unfortunately no. The resource is a managed application and there is a no boot diagnostics configured so you cannot access the console. ... View more

Zero firewall rules and no network security groups on this vNET.   12 hrs felt like a support engineer trying to get rid of me 🙂 ... View more

From what I can see is that you have 2 seperate vNETs. 1 for Meraki, 1 for Infrastructure.   In this situation, you have to setup vNET peering between the two vNETS for communication. Unfortunately this will increase costs as there is a cost for network traffic over peering.   Now to do it the way you want it, you need to setup the following configuration.   Delete your Meraki resource group that contains the managed app. This will also delete the other LOCKED resource group containing the Meraki VM infrastructure.  In your Infrastructure resource group, open your existing vNET configured as 10.100.0.0/16. Create a new subnet for the Meraki VM. I typically have the range away from any other infrastructure such as 10.100.254.0/24. Do not assign anything in the vNET. Open your infrastructure resource group. Note the location of your resource group. Click the plus sign and search for Meraki. Click create. a.Give the vMX a name b.Add the Meraki Auth Token from your dashboard. c. Select your subscription. d. Click Create new for the Resource Group. Call it what ever you want. This is where the Meraki managed app will live. e. Choose the same location as your Infrastructure resource group. Most likely Australia East. Very important. Now when you move to the deployment details step, it will try to create a vNET for you (vmx-vnet). Don't do this. Click on Virtual Network, select your Infrastructure vNET name. Click on Subnets, select the Meraki subnet you created in step 2. Click Ok and create the VM. Once the VM is up, you will need a route table in your Infrastructure vNET. Add your onprem networks and forward them to the IP of your vMX. Associate it to your your Infrastructure subnet, NOT the Meraki subnet.   What we have done here is create a Meraki vMX to use the same vNET as your internal infrastructure. Meraki only have the requirement to create infrastructure in its own Resource Group. If resource groups are in the same region, they can share vNETs. If you create seperate vNET's, the only way they can communicate is via vNET peering. This is a Azure networking basics. ... View more