2.3.5. Azure Virtual Network Manager
Peering is a per-pair operation. Twenty virtual networks in a full mesh is 190 peerings, each created and maintained by hand, and every new VNet means remembering to wire it to all the others. Azure Virtual Network Manager replaces that bookkeeping with an intent you declare once and apply to a group of virtual networks.
The four stages, in order:
| Stage | What you define | Why it matters |
|---|---|---|
| Scope | A list of subscriptions, or a management group | The manager can only see and change resources inside this boundary |
| Network group | A logical container of virtual networks | Membership is either static (hand-picked) or dynamic, driven by Azure Policy conditions |
| Configuration | Connectivity, Security admin, or Routing | Describes the intent to apply to that group |
| Deployment | The regions to push the configuration to | Nothing takes effect until this step runs |
⚠️ Exam Trap: A configuration that has been created but never deployed to the region holding the target VNets does nothing whatsoever. "I built the connectivity configuration and the spokes still cannot reach each other" is a deployment problem, not a configuration problem. This is the single most testable fact about the service.
Connectivity topologies:
- Mesh — every virtual network in the group connects to every other one. Enabling global mesh extends that across regions.
- Hub and spoke — spokes connect to a hub you nominate. Switching on direct connectivity additionally lets spokes reach each other without transiting the hub, which is exactly what plain peering cannot give you without building the mesh by hand.
Dynamic membership is what makes this scale. With an Azure Policy condition such as "any virtual network tagged env=prod", a newly created VNet joins the group and inherits the topology on its own. Nobody has to remember to add it.
💡 First Principle: Peering describes a relationship between two named networks. Virtual Network Manager describes a rule about a set of networks. Whenever a question stresses scale, consistency, or "all current and future virtual networks", it is pointing at the manager rather than at peering.
