About This Architecture

Hub-and-spoke network topology across Azure UK regions with vnet-naht-hub-uks as the central hub connecting production and disaster recovery spokes. Traffic flows from Internet through public IPs to vm-naht-crm01-uks and vm-naht-gbhhsagesql-uks, with NAT gateways managing outbound connectivity via Public IPs 20.162.223.157 and 51.141.50.149. Private endpoints pe-naht-sact-files-uks and pep-stfslsnahtuks01 secure access to Azure Storage file shares while maintaining network isolation. This architecture demonstrates Azure best practices for scalability, security, and disaster recovery by isolating workloads in separate subnets with dedicated NSGs while maintaining centralized hub routing. Fork and customize this diagram on Diagrams.so to adapt the hub-and-spoke pattern for your multi-region Azure deployments.

People also ask

How do I design a hub-and-spoke network topology in Azure across multiple regions with disaster recovery?

This diagram shows a hub-and-spoke topology using vnet-naht-hub-uks as the central hub connecting production (UK South) and DR (UK West) spokes via vnet peering. NAT gateways manage outbound traffic through public IPs, while private endpoints secure storage access without exposing data to the Internet.