Virtual Network Manager setting that creates mesh or hub-and-spoke topologies, using peerings or connected groups, over a network group; route exchange between gateways isn't part of it.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Connectivity configuration in context, with comparison tables and the common traps.
Terms in this definition
- VNet
A private network belonging to a single subscription and region and covering all of that region's availability zones. A VM can only use a VNet located in the same region.
- Hub-and-spoke
A network layout in which a central hub virtual network holds shared services and the on-premises gateway, and each workload's spoke network is peered with the hub. Peering by itself does not let spokes reach one another via the hub.
- OVER
Gives a T-SQL window function its window: PARTITION BY, ORDER BY and, if wanted, a ROWS or RANGE frame. Rankings and running totals can then be worked out while every row is kept.
- Network group
Collection of VNets or subnets in Azure Virtual Network Manager, drawn only from within the manager's scope and filled either statically or dynamically by Azure Policy. VNets outside the scope can never be members.
- Branch-to-branch
Optional Azure Route Server feature, disabled by default, that passes routes among NVAs and the VPN and ExpressRoute gateways in its VNet, enabling transit between ExpressRoute and site-to-site VPN.
Related terms
- Mesh topology (Virtual Network Manager)
Connectivity configuration in Virtual Network Manager where a connected group links each VNet in the network group to all the others in both directions. It is regional unless you opt for global mesh.