Forum Discussion
Az Virtual Network Manager Multi-Region Hub-Spoke Topology
Would suggest taking a look at below key points as well:
- Global Mesh Connectivity:
- The global mesh option primarily connects spokes across regions, not hubs. To achieve inter-region hub connectivity, you may need to explicitly configure peering between the hub VNets in different regions.
- Hub-to-Hub Connections:
- Ensure that the hub VNets in each region are peered with each other. This step is crucial for enabling direct communication between hubs.
- Verify that the peering settings allow traffic forwarding and gateway transit if needed.
- Network Groups and Connectivity Configurations:
- Your approach of grouping VNets by region and applying hub-spoke connectivity configurations is correct for regional setups.
- For inter-region hub connections, create a separate connectivity configuration specifically for the hub VNets and apply it to the network group containing the hubs.
- Visualization in Azure Portal:
- If the visualization doesn't show hub-to-hub connections, double-check the peering status and ensure that the connectivity configurations are applied correctly.
Thanks for the structured reply. However, could you please elaborate more on the point 3.2? What kind of connectivity configuration do I need to create for connecting the hub VNets when on the other hand you say in point one, that I need to create manual peerings for inter-region hub connectivity?
Mesh network configuration connects all associated VNETS in the same Network Group together in a mesh topology. You can extend this across Azure regions with the Global Mesh option.
Described better here: https://learn.microsoft.com/en-us/azure/virtual-network-manager/concept-connectivity-configuration
However, I may have misunderstood your topology design slightly. Are you aiming for full mesh, hub-spoke full mesh or hub-to-hub?
Cheers!
