Design network solutions
Internet connectivity, connecting to on-premises, optimising performance and security, and choosing load balancing and routing.
- 18 min
- 5 concepts
- Try it yourself
- 4-question check
Learn
Network design decides how users and systems reach workloads, how securely, and how fast. Most enterprise designs use hub and spoke or Azure Virtual WAN to centralise connectivity and security.
- 1
Recommend a connectivity solution that connects Azure resources to the internet
Inbound: publish through Application Gateway or Front Door (with WAF), or a load balancer with Standard public IPs. Outbound: use NAT Gateway for predictable, scalable outbound SNAT (default outbound access is retired for new VNets), or route through Azure Firewall for inspection.
Remember: Outbound internet at scale: NAT Gateway.
- 2
Recommend a connectivity solution that connects Azure resources to on-premises networks
Site-to-site VPN over the internet (quick, encrypted, up to several Gbps with active-active gateways). ExpressRoute for private, predictable, high-bandwidth links (with Global Reach to connect sites, FastPath for performance, and VPN as backup). Point-to-site VPN for individual users. Virtual WAN for many branches.
Remember: Private, predictable bandwidth: ExpressRoute.
- 3
Recommend a solution to optimize network performance
Use accelerated networking on VMs, proximity placement groups for low latency between VMs, Front Door and CDN to serve content from the edge, ExpressRoute FastPath, and place resources in regions close to users. Use Network Watcher Connection Monitor to measure.
Remember: Lowest latency between VMs: proximity placement group.
- 4
Recommend a solution to optimize network security
Layer controls: NSGs and ASGs for segmentation, Azure Firewall (Premium for TLS inspection and IDPS) in the hub, private endpoints for PaaS, DDoS Network Protection, WAF for web apps, Azure Bastion for admin access, and Azure Virtual Network Manager security admin rules for organisation-wide rules.
Remember: PaaS without public exposure: private endpoints.
- 5
Recommend a load-balancing and routing solution
Decide on global or regional and HTTP(S) or not. Global HTTP: Front Door. Global non-HTTP: Traffic Manager (DNS) or cross-region Load Balancer. Regional HTTP: Application Gateway. Regional non-HTTP: Load Balancer. Combine them, for example Front Door in front of Application Gateway.
Remember: Global + HTTP = Front Door.
Load-balancing decision
| HTTP(S) | Any TCP/UDP | |
|---|---|---|
| Global | Azure Front Door | Traffic Manager or cross-region Load Balancer |
| Regional | Application Gateway | Azure Load Balancer |
Try it
Hub and spoke reminder: see why spokes need routing through the hub to reach each other.
This interactive part needs JavaScript.
In the portal
- NAT gatewaysAzure portal: NAT gateways > Create
- ExpressRoute circuitsAzure portal: ExpressRoute circuits > Create
- Virtual WANAzure portal: Virtual WANs > Create
- Network ManagerAzure portal: Network managers > Create
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your AZ-305 study plan.
Global HTTP load balancing with WAF across regions?
Front Door is global layer 7.
Many VMs need reliable outbound internet with fixed IPs. What do you recommend?
NAT Gateway provides scalable outbound SNAT.
Which connection doesn't traverse the public internet?
ExpressRoute is a private connection.
Which applies security rules across many VNets centrally?
AVNM applies rules org-wide.
Sources
- Microsoft Learn: Hub-spoke network topology
- Microsoft Learn: Load-balancing options
- Microsoft Learn: What is Azure NAT Gateway?
- Microsoft Learn: ExpressRoute overview
- Microsoft Learn: Azure Virtual Network Manager
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.