I have created and torn down the vMX 3 times now as I run into one problem or another, initially I tried to use a VNET that was already existing in another resource group (all resource groups are in the same region), and that VNET had nothing associated with it but only 3 subnets defined within it, I got an error message every time I tried to create this, so I had to let the vMX create it's own VNET within it's resource group, but now there are such draconian "deny" controls that it is basically useless as you can't create any route paths on the VNET in the Meraki Resource group. SO here we go for round 4 of deploying the vMX100, this time I will create a new VNET in an empty Resource Group and then pre-create a /30 subnet within that VNET range for the vMX to use and see if I can then setup a VNET peer from that /30 to other subnets within the same VNET.
... View more