VMx - Azure deployment

Just browsing

VMx - Azure deployment


I’ve deployed a vMX to my Azure tenancy. 
I now want to secure it using a network security group. 
Its not allowing me to attach an NSG to the NIC or Subnet the VMX is using. 
Have you encountered this in your deployments and if so how have you managed to overcome this. 
I would appreciate any info. 
Thank you. 

3 Replies 3
Kind of a big deal
Kind of a big deal

Maybe it can help you.




I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
A model citizen

Meraki vMX on Azure belongs to the Managed Resource group and cannot be configured.
In addition, it is necessary to belong to an existing virtual network because it is not possible to change the configuration.


vMX Setup Guide for Microsoft Azure - Cisco Meraki

> Virtual network: Choose an existing virtual network from the list; minimum allowed prefix size for the virtual network is /24 and max is /8

Ok thanks.

So I have to create a pre-existing vNet & Subnet un Azure. I had setup a brand new subscription and was able to create and add a new vNet and Subnet but not allowed bind them to an NSG.

Get notified when there are additional replies to this discussion.