Implement a hub-and-spoke network topology with shared services in Azureįigure 1: An example of a hub-and-spoke network topology.Īs shown in the diagram, Azure supports two types of hub-and-spoke design.Implement a hub-and-spoke network topology in Azure.The Azure reference architectures site contains example templates that you can use as the basis for implementing your own hub-and-spoke networks: But larger cloud adoption efforts should consider implementing a hub-and-spoke networking architecture if they have any of the concerns listed previously. Smaller cloud estates might not benefit from the added structure and capabilities that this model offers. Instituting a separation of concerns: You can deploy individual workloads between central IT teams and workload teams. For more information, see Azure subscription limits. Peering workload virtual networks from different subscriptions to a central hub can overcome these limits. Overcoming subscription limits: Large cloud-based workloads might require using more resources than a single Azure subscription contains. With a single location for services, IT can minimize redundant resources and management effort.

Saving on costs and efficient management: Centralize services that can be shared by multiple workloads, like network virtual appliances (NVAs) and DNS servers. This model addresses the following concerns: It also helps avoid Azure subscription limitations. Hub and spoke is a networking model for efficiently managing common communication or security requirements.

Hub networkplaynow