Networking for Microsoft Azures
Azure virtual networking connects and isolates resources using virtual networks, subnets, network security groups, routes and peering. Private DNS and load balancing add name resolution and traffic distribution. This unit opens the Networking and Operations stage and sets the traffic rules that decide which workloads can talk to each other.
Stage: Networking and Operations · Part of the Microsoft Azure roadmap · Last reviewed 19 November 2026
What to learn in Networking
- Design a virtual network address space and split it into subnets
- Write network security group rules with correct priority, source and port
- Connect two virtual networks with peering and explain its non-transitive nature
- Add a user-defined route to force traffic through a firewall
- Compare Azure Load Balancer with Application Gateway for a scenario
Networking interview questions
How does a network security group evaluate rules?
Rules are processed by priority number, lowest first, and processing stops at the first match that allows or denies the traffic. Default rules at high numbers allow traffic inside the virtual network and deny inbound traffic from the internet.
Is virtual network peering transitive?
No. If network A peers with B and B peers with C, A cannot reach C unless A and C are peered directly or traffic is routed through a hub appliance with suitable routes. Hub and spoke designs use this to control traffic paths.
Where Networking fits in the Microsoft Azure roadmap
Networking belongs to the Networking and Operations stage (advanced level). Connect and monitor.
Other units in this stage
Back to the full Microsoft Azure roadmap