Best practice for multiple vMX's

[Dunky]

I am seeking some advice on Best Practice in setting up multiple VMX's.

I have a need to create a number of vMX's in Azure.

Each will have VPN's to different sites (1 combined network/site in the dashboard)

What is the best way to add these to the dashboard?

- A single network for the vMX's and put them all in there

- Add the VMX to an existing dashboard network (network is a combined network for a location)

- Create multiple networks for the Azure locations and put the relevant VMX's in these

TIA

[CptnCrnch]

I'd say this is more of a "depends on what you want to achieve" than a best practice thing.

First and foremost, there must alsways be a single (with its warm spare) MX within a given network. Guess I'd create a seperate network for each vMX.

[Dunky]

Yeah, a separate network per VMX is what I was leaning towards.

If we cant create a security appliance network and put a dozen VMX's in it then I guess a network per VMX it will have to be - just would have been nice to create one network with them all in to aid in navigation and keep the number of networks to a minimum.

Cheers

[Inderdeep]

@Dunky : Did you check this guide 

https://documentation.meraki.com/MX/MX_Installation_Guides/vMX_Setup_Guide_for_Microsoft_Azure