Azure Cloud Networking Learning Workspace
Explore how enterprise networks are designed, connected, secured and operated in Microsoft Azure. Investigate virtual networks, hybrid connectivity, routing decisions, security enforcement and real-world traffic paths through interactive engineering experiences.
Explore an Enterprise Azure Network
Select a component to inspect its engineering role. Then run traffic scenarios to examine the relationships between routing, peering, security and private connectivity.
Traffic Path Investigation
Choose a scenario to visualise a simplified traffic path. Actual Azure forwarding depends on effective routes, peering configuration, security rules and service settings.
Five Stages. Fifteen Engineering Labs.
Progress from fundamental Azure network design to advanced routing, hybrid architecture, security investigation and production troubleshooting.
Architecture & Foundations
VNets, subnet design, addressing and NSG evaluation.
Routing & Connectivity
Effective routes, peering, VPN and ExpressRoute.
Security & Delivery
Azure Firewall, Private Link and application traffic.
Enterprise Networking
Hub-spoke, Virtual WAN, DNS and multi-region design.
Troubleshooting & Capstone
Network Watcher, failure investigation and design validation.
Azure Cloud Networking Learning Dashboard
Explore five structured learning stages and 15 interactive engineering labs. Build Azure network architectures, investigate routing and security, trace connectivity and diagnose enterprise incidents.
Your Azure Learning Progress
Self-reported activity completion, saved locally in this browser.
Stage 1 · Continue your engineering journey
Your Five Learning Stages
Select a stage to open its next unfinished lab.
Interactive Engineering Lab Directory
Every published lab is listed below. Completion is recorded using the stage trackers after each group of three labs.
Azure VNet & Subnet Architecture Builder
Design an Azure virtual network, configure subnet address spaces and validate your architecture. Investigate how CIDR boundaries, subnet overlaps and Azure-reserved addresses influence production network design.
Configure a valid VNet address space
Create at least three valid subnets
Detect and resolve a subnet overlap
Pass the engineering validation checks
Subnet Configuration
Application Subnet
Subnet Address Allocation
| Subnet | CIDR | Total IPv4 | Azure Usable | Validation | Action |
|---|
The allocation bar represents IPv4 address space, not VM capacity. Small subnets may be visually exaggerated for readability.
Engineering Validation
Azure IP Address Planning & Subnet Validation
Design a production-ready IPv4 addressing plan for Azure workloads. Calculate subnet capacity, allocate address ranges, identify overlaps and resolve configuration failures using engineering validation.
Calculate IPv4 subnet capacity
Build a valid enterprise subnet plan
Detect and repair an overlap
Pass the engineering validation
Subnet Allocation
Add a subnet to your enterprise address plan.
Segment widths represent address quantities. Overlapping ranges are highlighted in red.
Enterprise Subnet Plan
Review each subnet for containment, network alignment, overlap and usable capacity.
| Subnet | CIDR | Addresses | Azure Usable | Validation | Action |
|---|
Engineering Validation
Validate the address plan and complete all four learning objectives.
Azure Network Security Group Rule Evaluation
Investigate how Azure Network Security Groups evaluate traffic using direction, priority, protocol, source and destination address ranges, and port matching. Trace rule decisions, diagnose unexpected access and explore stateful return traffic.
Investigate an allowed application flow
Diagnose a denied connection
Resolve a rule-priority conflict
Validate stateful return traffic
Traffic Investigation
Choose a scenario or customise the packet parameters.
Packet Evaluation Ready
NOT EVALUATEDRun the evaluation to inspect matching rules and packet decisions.
Security Engineering Notes
Azure NSGs are stateful. An established permitted flow can allow its reverse traffic without a separate matching return rule.
NSG Rule Table
Inspect priority ordering and remove custom rules. Built-in defaults are displayed separately from editable rules.
| Priority | Rule | Direction | Protocol | Source | Destination | Ports (Src → Dst) | Action | Manage |
|---|
Engineering Validation
Complete all four objectives, diagnose the priority fault and verify the resulting NSG decisions.
Architecture & Foundations — Completion Tracker
Complete the three foundational Azure networking activities to develop your understanding of virtual networks, subnet addressing and network security rules. Mark each activity complete after working through its interactive engineering lab.
Stage 01 Progress
VNet & Subnet Architecture Builder
Explore Azure virtual network architecture, construct subnet boundaries, and investigate how address spaces and network segmentation influence connectivity.
IP Address Planning & Validation
Practise CIDR allocation, inspect subnet capacity and investigate overlapping address ranges before validating a network design.
NSG Rule Evaluation Simulator
Evaluate Azure Network Security Group rules, understand priority ordering, inspect traffic decisions and investigate allow or deny outcomes.
Progress is self-reported and saved locally in this browser. Marking an activity complete updates the Azure Learning Dashboard and other compatible progress trackers. Technical validation inside each lab remains independent of this learning completion record.
Azure Route Selection & Effective Routes
Investigate how Azure selects routes using longest-prefix matching, system routes, user-defined routes and BGP-learned prefixes. Build custom route tables, redirect traffic through virtual appliances, detect blackholes and resolve production routing failures.
Investigate Azure system routing
Redirect traffic using a UDR
Investigate a BGP-learned route
Repair a routing blackhole
Route Investigation
Choose a scenario or enter a destination IPv4 address.
Route Evaluation Ready
NOT EVALUATEDEvaluate a destination to inspect prefix matching, route-source precedence and next-hop selection.
Routing Engineering Notes
Understand Azure route selection before adding custom routes.
Effective Route Table
Compare system, BGP and user-defined routes. The selected route is highlighted after evaluation.
| Prefix | Route Name | Source | Next-Hop Type | Next-Hop IP | Status | Action |
|---|
Engineering Validation
Complete the four routing objectives and verify that no injected blackhole remains active.
Azure VNet Peering Connectivity Lab
Configure a hub-and-spoke Azure network, examine peering states and address-space conflicts, test bidirectional connectivity, investigate forwarded traffic and gateway transit, and repair production-style networking faults.
Establish a bidirectional peering
Detect and resolve an address overlap
Configure gateway transit
Validate spoke-to-spoke forwarding
Connectivity Investigation
Select a test to inspect peering, transit and forwarding conditions.
Connectivity Test Ready
Configure peering settings, then test the network.
Address-Space Configuration
Change VNet CIDRs to investigate overlap errors.
Peering State & Effective Connectivity
Inspect both peering connections and their operational settings.
| Connection | State | Forwarded Traffic | Gateway Transit | Remote Gateway | Address Space |
|---|
Engineering Validation
Establish peering, repair an overlap, enable gateway transit and validate forwarded spoke traffic.
Azure VPN & ExpressRoute Path Explorer
Investigate enterprise hybrid networking across IPsec VPN tunnels and ExpressRoute private peering. Compare path availability, inspect BGP route advertisements, inject link failures and validate failover across a dual-connectivity architecture.
Validate VPN connectivity
Investigate ExpressRoute private peering
Verify hybrid BGP route exchange
Diagnose and recover from a path failure
Hybrid Path Investigation
Select the connectivity design and inspect the effective path.
Hybrid Path Ready
Run an evaluation to inspect connectivity and path selection.
Hybrid Engineering Notes
Consider the routing and availability dependencies.
Hybrid BGP Route Table
Inspect advertised prefixes, transport availability and route eligibility.
| Prefix | Direction | Transport | BGP | Eligibility |
|---|
Engineering Validation
Complete VPN, ExpressRoute, BGP and failover objectives.
Routing & Connectivity — Completion Tracker
Explore Azure effective routes, VNet peering and hybrid connectivity. Work through all three engineering labs, investigate routing behaviour and mark each activity complete when you have finished exploring it.
Stage 02 Progress
0 / 3 · 0%Azure Route Selection Explorer
Investigate longest-prefix matching, system routes, user-defined routes, BGP-learned prefixes and effective next-hop selection. Examine route conflicts and troubleshoot forwarding blackholes.
Azure VNet Peering Connectivity Lab
Explore regional and global VNet peering, address-space compatibility, gateway transit, forwarded traffic and connectivity dependencies. Investigate the causes of failed peering paths.
Azure VPN & ExpressRoute Path Explorer
Compare site-to-site VPN and ExpressRoute connectivity, investigate hybrid routing paths, inspect BGP propagation and explore redundancy and failover between connectivity options.
Progress is self-reported and stored locally in this browser. You may mark activities complete or incomplete at any time. These controls update the Azure Learning Dashboard independently of technical validation inside the engineering simulators.
Azure Firewall Policy Investigation Lab
Investigate Azure Firewall rule processing across network rules, application rules and DNAT. Trace packet decisions, inspect priority ordering, diagnose blocked workloads and repair security policy without introducing overly permissive access.
Evaluate a network rule
Inspect application FQDN filtering
Investigate inbound DNAT
Repair a blocked production application
Traffic Investigation
Choose a scenario and evaluate the firewall decision.
Policy Evaluation Ready
Run a traffic scenario to inspect rule matching and the resulting security decision.
Security Engineering Notes
Important distinctions when investigating Azure Firewall.
Firewall Rule Collections
Inspect configured rules and remove custom or injected entries.
| Priority | Rule | Type | Source | Destination | Protocol / Port | Action | Manage |
|---|
Engineering Validation
Complete the four security investigations and restore production application access.
Azure Private Endpoint & DNS Resolution Lab
Trace Azure Private Link name resolution, inspect private DNS zone records, diagnose VNet link and DNS forwarding failures, validate endpoint approval and restore private connectivity to a protected Azure Storage service.
Resolve the service to a private IP
Diagnose a DNS configuration fault
Validate hybrid DNS forwarding
Repair a production Private Link outage
DNS Resolution Investigation
Choose a resolver location and trace the service hostname.
DNS Investigation Ready
Resolve the storage hostname to inspect the private DNS chain.
Engineering Notes
Key distinctions in Private Link troubleshooting.
DNS Resolution Records
Inspect the illustrative public-to-private hostname chain.
| Record | DNS Name | Type | Target / Address | Status |
|---|
Engineering Validation
Resolve the private service, diagnose DNS, verify hybrid forwarding and repair the endpoint outage.
Azure Application Delivery Traffic Lab
Investigate application delivery through Azure Application Gateway and Azure Load Balancer. Evaluate listeners, backend pools, health probes, WAF enforcement and production traffic failures using an interactive application-routing model.
Route an application request
Investigate WAF enforcement
Diagnose backend health failure
Restore application availability
Application Request Investigation
Choose a request and inspect listener, WAF and backend selection.
Application Request Ready
Send a request to inspect the application delivery decision.
Engineering Notes
Important application delivery concepts.
Backend Health & Delivery State
Inspect backend availability and request distribution.
| Backend | Private IP | Health | Requests Served | Availability |
|---|
Engineering Validation
Route traffic, inspect WAF decisions, diagnose backend failures and restore service availability.
Security & Application Delivery — Completion Tracker
Investigate Azure Firewall policies, Private Endpoint connectivity, DNS resolution and application delivery. Work through the three interactive engineering labs and record each activity when you have finished.
Stage 03 Progress
0 / 3 · 0%Azure Firewall Policy Investigation
Investigate firewall policy decisions, network and application rules, traffic inspection and the effect of policy priorities. Diagnose connectivity failures caused by firewall configuration and rule evaluation.
Private Endpoint & DNS Resolution
Explore Azure Private Link connectivity, private endpoint addressing and DNS resolution. Investigate private DNS zones, name resolution paths and common configuration problems affecting access to private services.
Azure Application Delivery Traffic Lab
Trace application traffic through Azure application delivery components. Examine listeners, routing rules, backend pools, health probes, WAF behaviour and the causes of failed application requests.
Progress is self-reported and stored locally in this browser. Mark Complete and Mark Incomplete are always available. The Azure Learning Dashboard reads the same completion records. Engineering validation inside each simulator remains independent of learning progress.
Azure Enterprise Hub-Spoke Network Builder
Design and troubleshoot a centralised Azure enterprise network. Configure hub-spoke peering, Azure Firewall routing, gateway transit and spoke connectivity, then investigate the effect of missing routes and peering settings.
Validate hub-spoke peering
Route traffic through Azure Firewall
Verify gateway transit
Repair a spoke connectivity failure
Connectivity Investigation
Choose a traffic path and evaluate the network design.
Network Evaluation Ready
Evaluate a traffic scenario to inspect peering, routing and security dependencies.
Engineering Notes
Important enterprise design principles.
Enterprise Routing & Connectivity Matrix
Inspect each conceptual traffic path and its dependencies.
| Traffic Flow | Required Connectivity | Routing / Security | State |
|---|
Engineering Validation
Validate peering, centralised inspection, gateway transit and incident recovery.
Azure Virtual WAN Routing Lab
Investigate enterprise-scale connectivity across Azure Virtual WAN hubs. Configure route-table associations and propagation, trace branch-to-VNet and inter-hub traffic, and repair missing route advertisements.
Validate branch-to-VNet routing
Inspect inter-hub connectivity
Diagnose route propagation
Repair a missing route
Traffic Path Investigation
Select a route and inspect the forwarding dependencies.
Route Investigation Ready
Trace a connection to inspect route propagation and association.
Engineering Notes
Important Virtual WAN routing principles.
Effective Virtual WAN Route Matrix
Inspect modelled reachability and the route information required for each connection.
| Destination Prefix | Origin | Propagated To | Connection | Effective State |
|---|
Engineering Validation
Complete branch routing, inter-hub forwarding, route propagation diagnosis and repair.
Azure Multi-Region Resilience & Failover Lab
Design a resilient Azure application across two regions. Compare active-active and active-passive traffic steering, simulate regional outages, inspect Azure Front Door health-based routing and validate recovery against an engineering RTO target.
Validate normal regional delivery
Execute regional failover
Evaluate recovery against RTO
Restore multi-region resilience
Traffic & Failover Investigation
Send requests and inspect the selected Azure region.
Global Routing Ready
Send a request to inspect regional origin selection.
Engineering Notes
Resilience concepts for production Azure applications.
Regional Availability & Recovery Matrix
Inspect the current origin health and the conceptual failover estimate.
| Region | Role | Health | Requests Served | Routing Eligibility |
|---|
Engineering Validation
Validate normal delivery, execute regional failover, assess RTO and restore resilient operations.
Enterprise Azure Networking — Completion Tracker
Design enterprise hub-spoke networks, investigate Azure Virtual WAN routing and explore multi-region resilience. Complete the three engineering activities and record your progress through this stage.
Stage 04 Progress
0 / 3 · 0%Enterprise Hub-Spoke Network Builder
Design enterprise hub-spoke architectures, connect workload spokes through shared services, investigate routing and traffic inspection, and explore the operational implications of centralised network connectivity.
Azure Virtual WAN Routing Lab
Explore Azure Virtual WAN hubs, route tables, connection associations and propagations. Investigate branch, VNet and hybrid connectivity, routing isolation and enterprise transit paths.
Multi-Region Resilience & Failover
Investigate regional redundancy, connectivity failures and failover decisions. Compare healthy and degraded network states, examine alternative paths and validate recovery strategies for enterprise Azure architectures.
Progress is self-reported and stored locally in this browser. Mark Complete and Mark Incomplete remain available independently of each lab's technical validation requirements. Completion records are shared with Azure Learning Dashboard V4.
Azure Network Watcher Investigation Lab
Investigate an Azure application connectivity incident using Network Watcher-style diagnostics. Trace effective security rules, inspect next-hop routing, evaluate endpoint reachability and isolate the root cause of a failed TCP connection.
Run IP flow verification
Inspect the effective next hop
Identify an injected incident
Repair and validate connectivity
Diagnostic Tool Console
Select a Network Watcher investigation and inspect the result.
Diagnostic Console Ready
Run a diagnostic to inspect the current network state.
Engineering Notes
How to interpret Network Watcher-style evidence.
Effective Network Diagnostic State
Review the current security, routing and application conditions.
| Diagnostic Layer | Configuration | Expected Behaviour | Status |
|---|
Engineering Validation
Run IP flow verification, inspect next-hop routing, diagnose the injected incident and restore connectivity.
Azure Production Incident Troubleshooting Lab
Investigate a production application outage across Azure DNS, NSGs, routing, firewall policy, Private Link and application health. Use diagnostic evidence to identify the failed layer, apply corrective changes and validate the restored end-to-end traffic path.
Establish healthy baseline
Diagnose DNS fault
Diagnose security fault
Diagnose routing fault
Restore production service
Production Incident Console
Select an incident and investigate its effect on the application.
Production Investigation Ready
Load an incident or validate the healthy baseline.
Repair Configuration
Modify the failed component and validate the result.
Production Network State Comparison
Compare the current configuration with the expected healthy baseline.
| Component | Healthy Baseline | Current State | Validation |
|---|
Engineering Validation
Complete the healthy baseline, diagnose DNS, security and routing faults, and repair a production outage.
Enterprise Azure Network Capstone
Take responsibility for a production Azure enterprise network. Investigate five infrastructure incidents, correlate routing, security, DNS and application evidence, identify the correct root cause and restore end-to-end service. Complete every incident to earn the final lab completion status.
Production Incident Queue
Select an incident, investigate the evidence and repair the affected component.
Capstone Investigation Ready
Load the first production incident to begin.
Root Cause Assessment
Choose the failed component before applying a repair.
Capstone Engineering Rules
Each incident requires a complete evidence-based workflow.
Enterprise Incident Resolution Matrix
Track each incident through investigation, repair and validation.
| Incident | Failure Domain | Diagnosis | Repair | Final Status |
|---|
Final Engineering Assessment
Resolve all five incidents and validate the enterprise Azure network.
Troubleshooting & Capstone — Completion Tracker
Bring together your Azure networking knowledge through operational diagnostics, production incident investigation and an enterprise capstone. Complete the final three engineering activities and review your learning journey across all five stages.
Stage 05 Progress
0 / 3 · 0%Azure Network Watcher Investigation
Investigate connectivity using Azure Network Watcher concepts, effective security rules, effective routes, connection troubleshooting and diagnostic evidence. Identify the most useful checks for isolating network faults.
Production Incident Troubleshooting
Investigate realistic Azure networking incidents. Correlate routing, firewall, NSG, DNS and connectivity evidence to isolate the failure domain, determine the likely root cause and validate the proposed recovery action.
Enterprise Azure Network Capstone
Apply your knowledge across five integrated enterprise networking incidents. Investigate the architecture, interpret diagnostic evidence, repair the simulated faults and validate the resulting network state.
Progress is self-reported and stored locally in this browser. Mark Complete and Mark Incomplete remain available independently of each simulator's technical validation. Finishing this stage completes the final three activities in the five-stage Azure learning journey.