NETWORK INSIGHT / LEARNING WORKSPACES
INTERACTIVE ENGINEERING AZURE CLOUD NETWORKING
Cloud Infrastructure / Architecture / Troubleshooting

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.

05 Learning stages
15 Engineering labs
01 Integrated capstone
HUB VNET 10.0.0.0/16 APP SPOKE DATA SPOKE HYBRID CONNECT SECURITY POLICY AZURE ENTERPRISE NETWORK CONNECTIVITY • ROUTING • SECURITY
ANIMATED CLOUD ARCHITECTURE / CONCEPTUAL MODEL
01 / Interactive Architecture

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.

AZURE / HUB-SPOKE ARCHITECTURE INTERACTIVE MODEL
HUB VNET 10.0.0.0/16 APPLICATION SPOKE 10.10.0.0/16 DATA SPOKE 10.20.0.0/16 APP VM 10.10.1.4 DATA VM 10.20.1.4 HUB Connectivity FIREWALL Policy enforcement ON-PREMISES VPN / ExpressRoute PRIVATE SERVICE Private Endpoint AZURE REGION / LOGICAL NETWORK MODEL Select a network component to inspect Allowed Blocked
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.

Application Spoke → Data Spoke

ALLOWED
02 / Structured Learning

Five Stages. Fifteen Engineering Labs.

Progress from fundamental Azure network design to advanced routing, hybrid architecture, security investigation and production troubleshooting.

STAGE 01 / LABS 1–3
Architecture & Foundations

VNets, subnet design, addressing and NSG evaluation.

STAGE 02 / LABS 4–6
Routing & Connectivity

Effective routes, peering, VPN and ExpressRoute.

STAGE 03 / LABS 7–9
Security & Delivery

Azure Firewall, Private Link and application traffic.

STAGE 04 / LABS 10–12
Enterprise Networking

Hub-spoke, Virtual WAN, DNS and multi-region design.

STAGE 05 / LABS 13–15
Troubleshooting & Capstone

Network Watcher, failure investigation and design validation.

Engineering learning objective: By the end of this workspace, learners should be able to reason about Azure network architecture, evaluate traffic paths, investigate connectivity failures and explain the operational implications of routing and security policies. The 15 labs are the planned workspace curriculum.
NETWORK INSIGHT — Azure Cloud Networking Learning Workspace
EXPLORE · TRACE · CONFIGURE · DIAGNOSE
Network Insight · Learning Workspace

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.

15Engineering Labs
0Labs Complete
0 / 5Stages Complete
0%Overall Progress
0 of 15 activities complete
RECOMMENDED NEXT ACTIVITY VNet & Subnet Architecture Builder

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.

Network Insight / Stage 01 / Lab 01

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.

Interactive Architecture IPv4 / CIDR Subnet Validation Address Planning Engineering Objectives
1

Configure a valid VNet address space

2

Create at least three valid subnets

3

Detect and resolve a subnet overlap

4

Pass the engineering validation checks

Live VNet Architecture 3 subnets configured
AZURE REGION / VIRTUAL NETWORK vnet-production / 10.20.0.0/16 CONCEPTUAL SUBNET TOPOLOGY / SELECT A NODE
Selected: Application Subnet Logical network model
Network Configuration Editable parameters

Subnet Configuration

SELECTED SUBNET
Application Subnet

Subnet Address Allocation

Subnet CIDR Total IPv4 Azure Usable Validation Action
VNet Address Space Allocation

The allocation bar represents IPv4 address space, not VM capacity. Small subnets may be visually exaggerated for readability.

Engineering Validation

ENGINEERING EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 01
DESIGN · VALIDATE · INVESTIGATE
Network Insight / Stage 01 / Lab 02

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.

IPv4 CIDR Calculator Enterprise Address Planning Subnet Capacity Overlap Investigation Interactive Validation
1

Calculate IPv4 subnet capacity

2

Build a valid enterprise subnet plan

3

Detect and repair an overlap

4

Pass the engineering validation

Enterprise Address Space Planner Scenario-based configuration

Subnet Allocation

Add a subnet to your enterprise address plan.

IPv4 Address Space Allocation

Segment widths represent address quantities. Overlapping ranges are highlighted in red.

IPv4 / CIDR Engineering Calculator Interactive analysis
AZURE VNET 10.40.0.0/16 APPLICATION DATA MANAGEMENT
—Network address
—Last address
—Subnet mask
—Total IPv4 addresses
—Azure usable addresses
—Requirement utilisation
Calculate a CIDR range to inspect Azure address reservations and workload capacity.

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.

Start by calculating a CIDR range, review the subnet plan, inject and resolve an address conflict, then run engineering validation.
NETWORK INSIGHT / ADDRESS PLANNING EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 02
CALCULATE · ALLOCATE · VALIDATE · TROUBLESHOOT
Network Insight / Stage 01 / Lab 03

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.

NSG Rule Engine Priority Evaluation Inbound / Outbound Service Tags Stateful Flows Security Troubleshooting
1

Investigate an allowed application flow

2

Diagnose a denied connection

3

Resolve a rule-priority conflict

4

Validate stateful return traffic

Azure Network Security Architecture Animated packet-path visualisation
AZURE VIRTUAL NETWORK / SECURITY PATH VNET 10.10.0.0/16 SOURCE 10.10.1.4 NSG RULE EVALUATION READY DESTINATION 10.10.2.4 SUBNET / NIC NSG POLICY BOUNDARY CONCEPTUAL SINGLE-NSG EVALUATION MODEL
Select a traffic scenario Awaiting evaluation

Traffic Investigation

Choose a scenario or customise the packet parameters.

Packet Evaluation Ready
NOT EVALUATED

Run the evaluation to inspect matching rules and packet decisions.

NSG Rule Configuration Editable custom policy
Rules are evaluated in ascending priority order. The first matching rule determines the decision.

Security Engineering Notes

Azure NSGs are stateful. An established permitted flow can allow its reverse traffic without a separate matching return rule.

Priority: Lower numerical values are evaluated first.
Default rules: Azure includes built-in allow and deny rules with priorities 65000–65500.
Service tags: This model supports VirtualNetwork, Internet and AzureLoadBalancer.
Scope: This lab evaluates one conceptual NSG attachment, not combined subnet and NIC NSGs.

NSG Rule Table

Inspect priority ordering and remove custom rules. Built-in defaults are displayed separately from editable rules.

PriorityRuleDirection ProtocolSourceDestination Ports (Src → Dst)ActionManage

Engineering Validation

Complete all four objectives, diagnose the priority fault and verify the resulting NSG decisions.

Begin by evaluating the application HTTPS scenario. Then investigate denied SSH traffic, inject a priority fault, repair it and test stateful return traffic.
NETWORK INSIGHT / NSG EVALUATION EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 03
INSPECT · EVALUATE · DIAGNOSE · ENFORCE
Network Insight · Azure Learning Workspace · Stage 01

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.

Not Started
0 of 3 activities complete

Stage 01 Progress

0 / 3 · 0%
Complete the activities below to finish Stage 01.
ACTIVITY 01 · LAB 01 NOT COMPLETE
VNet & Subnet Architecture Builder

Explore Azure virtual network architecture, construct subnet boundaries, and investigate how address spaces and network segmentation influence connectivity.

ACTIVITY 02 · LAB 02 NOT COMPLETE
IP Address Planning & Validation

Practise CIDR allocation, inspect subnet capacity and investigate overlapping address ranges before validating a network design.

ACTIVITY 03 · LAB 03 NOT COMPLETE
NSG Rule Evaluation Simulator

Evaluate Azure Network Security Group rules, understand priority ordering, inspect traffic decisions and investigate allow or deny outcomes.

Network Insight / Stage 02 / Lab 04

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.

Longest Prefix Match System Routes User-Defined Routes BGP Propagation Next-Hop Selection Routing Troubleshooting
1

Investigate Azure system routing

2

Redirect traffic using a UDR

3

Investigate a BGP-learned route

4

Repair a routing blackhole

Azure Hub-and-Spoke Routing Architecture Interactive route-path visualisation
AZURE ENTERPRISE ROUTING FABRIC INTERNET 0.0.0.0/0 HUB VNET 10.0.0.0/16 SPOKE VNET 10.1.0.0/16 VIRTUAL NVA 10.0.2.4 ON-PREMISES 172.16.0.0/16 CONCEPTUAL ROUTE SELECTION / NEXT-HOP MODEL
Select a routing scenario Awaiting evaluation

Route Investigation

Choose a scenario or enter a destination IPv4 address.

Route Evaluation Ready
NOT EVALUATED

Evaluate a destination to inspect prefix matching, route-source precedence and next-hop selection.

Azure Route Table Configuration Editable user-defined routes
Azure selects the longest matching prefix. When prefix lengths are equal, user-defined routes take precedence over BGP routes and system routes.

Routing Engineering Notes

Understand Azure route selection before adding custom routes.

Longest-prefix match: The most specific matching route wins.
Equal prefix: UDR → BGP → System.
Virtual appliance: Traffic can be redirected through an NVA or Azure Firewall.
Blackhole: A next-hop type of None drops traffic.
Effective routes: Real Azure route tables also depend on subnet associations, propagation and topology.

Effective Route Table

Compare system, BGP and user-defined routes. The selected route is highlighted after evaluation.

PrefixRoute NameSource Next-Hop TypeNext-Hop IP StatusAction

Engineering Validation

Complete the four routing objectives and verify that no injected blackhole remains active.

Begin by evaluating the Internet route, then investigate the spoke VNet, BGP-learned routes, and a routing blackhole.
NETWORK INSIGHT / AZURE ROUTING EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 04
DISCOVER · SELECT · FORWARD · TROUBLESHOOT
Network Insight / Stage 02 / Lab 05

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.

VNet PeeringHub & SpokeGateway Transit Forwarded TrafficOverlap DetectionConnectivity Diagnostics
1

Establish a bidirectional peering

2

Detect and resolve an address overlap

3

Configure gateway transit

4

Validate spoke-to-spoke forwarding

Interactive Hub-and-Spoke TopologyThree Azure VNets
AZURE PEERING & CONNECTIVITY FABRIC VPN / ER GATEWAY On-premises access HUB VNET 10.0.0.0/16 Gateway + NVA APPLICATION SPOKE 10.10.0.0/16 DATA SPOKE 10.20.0.0/16 PEERING DOES NOT AUTOMATICALLY PROVIDE TRANSITIVE ROUTING
Topology readyLogical architecture model

Connectivity Investigation

Select a test to inspect peering, transit and forwarding conditions.

Connectivity Test Ready

Configure peering settings, then test the network.

Peering ConfigurationEditable topology state

Address-Space Configuration

Change VNet CIDRs to investigate overlap errors.

Select a peering connection and configure its settings.

Peering State & Effective Connectivity

Inspect both peering connections and their operational settings.

ConnectionStateForwarded TrafficGateway TransitRemote GatewayAddress Space

Engineering Validation

Establish peering, repair an overlap, enable gateway transit and validate forwarded spoke traffic.

Start by testing connectivity between the hub and application spoke. Then inject an overlap and repair it before configuring gateway transit and forwarded traffic.
NETWORK INSIGHT / PEERING EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 05
PEER · ROUTE · VALIDATE · TROUBLESHOOT
Network Insight / Stage 02 / Lab 06

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.

Site-to-Site VPNExpressRouteBGPHybrid RoutingFailoverIncident Investigation
1

Validate VPN connectivity

2

Investigate ExpressRoute private peering

3

Verify hybrid BGP route exchange

4

Diagnose and recover from a path failure

Enterprise Hybrid Connectivity ArchitectureInteractive path visualisation
HYBRID AZURE NETWORK / DUAL TRANSPORT ON-PREMISES 172.16.0.0/16 Enterprise Edge Router AZURE HUB 10.0.0.0/16 VPN / ER Gateways IPSEC VPN Encrypted Internet Tunnel EXPRESSROUTE Private Peering Circuit PATH PREFERENCE IS A SIMPLIFIED LAB POLICY, NOT AN AZURE GUARANTEE
Hybrid topology readyTwo independent transport models

Hybrid Path Investigation

Select the connectivity design and inspect the effective path.

Hybrid Path Ready

Run an evaluation to inspect connectivity and path selection.

Transport & BGP ControlsFault injection and recovery
Both paths begin operational. Evaluate VPN, ExpressRoute and dual-connectivity behaviour.

Hybrid Engineering Notes

Consider the routing and availability dependencies.

VPN: IPsec connectivity across an Internet transport, with optional BGP route exchange.
ExpressRoute: Private connectivity via a provider, with BGP used for private peering.
Failover: Requires usable alternative routes and appropriate routing preferences.
Redundancy: A single conceptual circuit does not represent ExpressRoute's complete physical redundancy model.
Security: ExpressRoute private peering is not inherently end-to-end encrypted.

Hybrid BGP Route Table

Inspect advertised prefixes, transport availability and route eligibility.

PrefixDirectionTransportBGPEligibility

Engineering Validation

Complete VPN, ExpressRoute, BGP and failover objectives.

Start by evaluating the dual-connectivity design. Then investigate each transport independently, inspect BGP route availability and simulate ExpressRoute failure.
NETWORK INSIGHT / HYBRID NETWORK EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 06
CONNECT · ADVERTISE · SELECT · FAIL OVER
Network Insight · Azure Learning Workspace · Stage 02

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.

Not Started
0 of 3 activities complete

Stage 02 Progress

0 / 3 · 0%
Complete the three routing and connectivity activities.
ACTIVITY 01 · LAB 04 NOT COMPLETE
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.

ACTIVITY 02 · LAB 05 NOT COMPLETE
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.

ACTIVITY 03 · LAB 06 NOT COMPLETE
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.

Network Insight / Stage 03 / Lab 07

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.

Azure FirewallNetwork RulesApplication RulesDNATPriority EvaluationSecurity Troubleshooting
1

Evaluate a network rule

2

Inspect application FQDN filtering

3

Investigate inbound DNAT

4

Repair a blocked production application

Azure Firewall Security ArchitectureAnimated policy decision path
AZURE SECURITY INSPECTION / FIREWALL POLICY APPLICATION SUBNET 10.10.1.0/24 AZURE FIREWALL POLICY ENGINE READY DESTINATION INTERNET / SERVICE DNAT → NETWORK RULES → APPLICATION RULES → DEFAULT DENY SIMPLIFIED CLASSIC RULE-COLLECTION EVALUATION MODEL
Firewall readyConceptual single-policy evaluation

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.

Firewall Policy EditorCustom rule configuration
Rules are evaluated by collection type and priority in this simplified model. Network-rule matches are processed before application-rule matches.

Security Engineering Notes

Important distinctions when investigating Azure Firewall.

DNAT: Destination translation is evaluated before network and application rules in classic processing.
Network rules: Match IP addresses, protocols and ports.
Application rules: Support HTTP/S FQDN-based filtering, subject to protocol and configuration.
Default deny: Traffic without a matching allow rule is blocked.
Policy hierarchy: Parent/child policies and rule collection groups introduce additional processing structure not fully modelled here.

Firewall Rule Collections

Inspect configured rules and remove custom or injected entries.

PriorityRuleTypeSourceDestinationProtocol / PortActionManage

Engineering Validation

Complete the four security investigations and restore production application access.

Begin with the DNS network rule, then investigate an application rule, DNAT and the production application outage.
NETWORK INSIGHT / FIREWALL POLICY EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 07
INSPECT · FILTER · TRANSLATE · DIAGNOSE
Network Insight / Stage 03 / Lab 08

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.

Azure Private LinkPrivate EndpointPrivate DNS ZonesDNS ForwardingHybrid DNSTroubleshooting
1

Resolve the service to a private IP

2

Diagnose a DNS configuration fault

3

Validate hybrid DNS forwarding

4

Repair a production Private Link outage

Private Link Resolution ArchitectureInteractive DNS + data path
PRIVATE LINK / NAME RESOLUTION / PRIVATE DATA PATH AZURE WORKLOAD 10.10.1.4 DNS RESOLVER Azure DNS / Forwarder PRIVATE DNS ZONE privatelink.blob.core.windows.net PRIVATE ENDPOINT 10.10.2.5 APPROVED DNS RESOLUTION AND PRIVATE ENDPOINT CONNECTIVITY ARE SEPARATE CHECKS ILLUSTRATIVE AZURE STORAGE BLOB PRIVATE ENDPOINT MODEL
Private DNS readyPrivate IP resolution model

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.

Private Endpoint & DNS ControlsConfiguration and fault injection
Private DNS zone, VNet link, A record, hybrid forwarding and endpoint approval are initially configured.

Engineering Notes

Key distinctions in Private Link troubleshooting.

DNS: Clients normally use the public service hostname, which can resolve through a privatelink CNAME to a private A record.
VNet links: Azure Private DNS resolution requires the appropriate zone link or DNS forwarding architecture.
Hybrid: On-premises DNS commonly forwards via an Azure DNS Private Resolver inbound endpoint or a DNS forwarder.
Approval: A pending or rejected private endpoint connection cannot provide an operational service path.
Public access: Disabling public network access does not prevent approved private endpoint connectivity.

DNS Resolution Records

Inspect the illustrative public-to-private hostname chain.

RecordDNS NameTypeTarget / AddressStatus

Engineering Validation

Resolve the private service, diagnose DNS, verify hybrid forwarding and repair the endpoint outage.

Start by resolving the Azure Storage hostname from the linked VNet. Then investigate DNS and endpoint failures.
NETWORK INSIGHT / PRIVATE LINK DNS EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 08
RESOLVE · LINK · APPROVE · TROUBLESHOOT
Network Insight / Stage 03 / Lab 09

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.

Application GatewayAzure Load BalancerHTTP RoutingBackend HealthWAFFailover
1

Route an application request

2

Investigate WAF enforcement

3

Diagnose backend health failure

4

Restore application availability

Azure Application Delivery ArchitectureAnimated request path
AZURE APPLICATION DELIVERY / REQUEST ROUTING CLIENT HTTPS REQUEST APPLICATION GATEWAY LISTENER / WAF BACKEND A 10.10.2.4 BACKEND B 10.10.2.5 APPLICATION GATEWAY: L7 ROUTING / AZURE LOAD BALANCER: L4 DISTRIBUTION CONCEPTUAL APPLICATION GATEWAY DATA PATH
Application delivery readyLayer 7 routing model

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.

Application Delivery ControlsHealth and security policy
Both backends are healthy. The HTTPS listener is enabled and WAF is operating in Prevention mode.

Engineering Notes

Important application delivery concepts.

Application Gateway: Layer 7 HTTP/HTTPS routing, TLS termination and optional WAF integration.
Azure Load Balancer: Layer 4 load distribution using configured rules, backend pools and health probes.
Health probes: Unhealthy backend targets are excluded from normal distribution.
WAF Prevention: Requests matching blocking rules are denied.
WAF Detection: Matching requests are logged but not blocked by WAF detection alone.

Backend Health & Delivery State

Inspect backend availability and request distribution.

BackendPrivate IPHealthRequests ServedAvailability

Engineering Validation

Route traffic, inspect WAF decisions, diagnose backend failures and restore service availability.

Begin with a normal HTTPS request, then investigate WAF enforcement and backend health failures.
NETWORK INSIGHT / APPLICATION DELIVERY EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 09
LISTEN · INSPECT · BALANCE · RECOVER
Network Insight · Azure Learning Workspace · Stage 03

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.

Not Started
0 of 3 activities complete

Stage 03 Progress

0 / 3 · 0%
Complete the three security and application delivery activities.
ACTIVITY 01 · LAB 07 NOT COMPLETE
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.

ACTIVITY 02 · LAB 08 NOT COMPLETE
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.

ACTIVITY 03 · LAB 09 NOT COMPLETE
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.

Network Insight / Stage 04 / Lab 10

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.

Hub-Spoke ArchitectureVNet PeeringAzure FirewallUDRsGateway TransitEnterprise Segmentation
1

Validate hub-spoke peering

2

Route traffic through Azure Firewall

3

Verify gateway transit

4

Repair a spoke connectivity failure

Enterprise Hub-Spoke ArchitectureAnimated VNet connectivity
AZURE ENTERPRISE NETWORK / HUB-SPOKE TOPOLOGY SPOKE A 10.10.0.0/16 SPOKE B 10.20.0.0/16 HUB VNET 10.0.0.0/16 AZURE FIREWALL HYBRID GATEWAY ON-PREMISES CONNECTIVITY PEERING DOES NOT AUTOMATICALLY PROVIDE TRANSITIVE SPOKE ROUTING
Enterprise topology readyCentralised inspection model

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.

Enterprise Network ControlsPeering, routing and security
Both spokes are peered to the hub, centralised firewall routing is configured and gateway transit is enabled.

Engineering Notes

Important enterprise design principles.

Peering: Hub-spoke VNet peering is not transitive by itself.
Central inspection: UDRs can direct spoke traffic toward a firewall or network virtual appliance.
Forwarding: Peering and forwarding configuration must permit routed traffic through the hub.
Gateway transit: Spokes can use an eligible hub gateway when the required peering options are configured.
Production: Route symmetry, NSGs, firewall policy and effective routes must also be validated.

Enterprise Routing & Connectivity Matrix

Inspect each conceptual traffic path and its dependencies.

Traffic FlowRequired ConnectivityRouting / SecurityState

Engineering Validation

Validate peering, centralised inspection, gateway transit and incident recovery.

Begin by testing spoke-to-spoke connectivity, then hub services and on-premises connectivity. Inject a route failure and restore the design.
NETWORK INSIGHT / ENTERPRISE NETWORK EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 10
PEER · ROUTE · INSPECT · RECOVER
Network Insight / Stage 04 / Lab 11

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.

Virtual WANVirtual HubsRoute TablesPropagation LabelsInter-Hub RoutingHybrid Connectivity
1

Validate branch-to-VNet routing

2

Inspect inter-hub connectivity

3

Diagnose route propagation

4

Repair a missing route

Virtual WAN Enterprise TopologyAnimated route propagation
AZURE VIRTUAL WAN / MULTI-HUB ROUTING FABRIC BRANCH 172.16.0.0/16 VIRTUAL HUB A WEST EUROPE VIRTUAL HUB B NORTH EUROPE VNET A 10.10.0.0/16 VNET B 10.20.0.0/16 VIRTUAL WAN ROUTING CONTROL PLANE ROUTE TABLE ASSOCIATION / PROPAGATION / LABELS SIMPLIFIED STANDARD VIRTUAL WAN MODEL
Routing fabric readyRoute-aware connectivity

Traffic Path Investigation

Select a route and inspect the forwarding dependencies.

Route Investigation Ready

Trace a connection to inspect route propagation and association.

Virtual WAN Routing ControlsHub connection policy
All connections currently propagate routes into the modelled Default route table, and both virtual hubs are connected.

Engineering Notes

Important Virtual WAN routing principles.

Association: Each connection associates with a route table for forwarding decisions.
Propagation: Connections advertise prefixes to selected hub route tables or labels.
Labels: A label can group multiple route tables as propagation targets.
Inter-hub: Standard Virtual WAN provides managed hub-to-hub connectivity, subject to routing configuration.
Routing intent: Private and Internet traffic can be steered through supported security solutions; advanced intent policies are outside this lab's forwarding model.

Effective Virtual WAN Route Matrix

Inspect modelled reachability and the route information required for each connection.

Destination PrefixOriginPropagated ToConnectionEffective State

Engineering Validation

Complete branch routing, inter-hub forwarding, route propagation diagnosis and repair.

Start by tracing Branch → VNet A and VNet A → VNet B. Then inject a route propagation failure and restore reachability.
NETWORK INSIGHT / VIRTUAL WAN ROUTING EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 11
ASSOCIATE · PROPAGATE · TRACE · REPAIR
Network Insight / Stage 04 / Lab 12

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.

Azure Front DoorMulti-RegionActive-ActiveActive-PassiveHealth ProbesFailoverRTO
1

Validate normal regional delivery

2

Execute regional failover

3

Evaluate recovery against RTO

4

Restore multi-region resilience

Azure Multi-Region Application ArchitectureAnimated global request routing
AZURE GLOBAL APPLICATION DELIVERY / REGIONAL RESILIENCE GLOBAL CLIENT HTTPS REQUEST AZURE FRONT DOOR HEALTH / PRIORITY WEST EUROPE PRIMARY ORIGIN NORTH EUROPE SECONDARY ORIGIN ORIGIN HEALTH + ROUTING CONFIGURATION DETERMINE REQUEST DESTINATION CONCEPTUAL FRONT DOOR ORIGIN-SELECTION MODEL
Multi-region delivery readyGlobal origin selection

Traffic & Failover Investigation

Send requests and inspect the selected Azure region.

Global Routing Ready

Send a request to inspect regional origin selection.

Resilience ConfigurationRouting and health controls
Both regions are healthy. West Europe is primary and North Europe is available for failover.

Engineering Notes

Resilience concepts for production Azure applications.

Active-passive: A preferred origin handles traffic until it becomes unhealthy or unavailable.
Active-active: Multiple eligible origins can serve requests, subject to origin selection configuration.
Health probes: Origin health affects eligibility, but probe timing is not the same as a guaranteed failover time.
RTO: The target maximum time to restore service following a disruption.
RPO: The acceptable data-loss window. Application replication and data consistency are outside this routing-only model.

Regional Availability & Recovery Matrix

Inspect the current origin health and the conceptual failover estimate.

RegionRoleHealthRequests ServedRouting Eligibility

Engineering Validation

Validate normal delivery, execute regional failover, assess RTO and restore resilient operations.

Start by sending a normal request. Inject a West Europe outage, verify failover to North Europe and restore both regions.
NETWORK INSIGHT / MULTI-REGION RESILIENCE EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 12
DESIGN · DETECT · FAILOVER · RECOVER
Network Insight · Azure Learning Workspace · Stage 04

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.

Not Started
0 of 3 activities complete

Stage 04 Progress

0 / 3 · 0%
Complete the three enterprise networking activities.
ACTIVITY 01 · LAB 10 NOT COMPLETE
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.

ACTIVITY 02 · LAB 11 NOT COMPLETE
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.

ACTIVITY 03 · LAB 12 NOT COMPLETE
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.

Network Insight / Stage 05 / Lab 13

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.

Network WatcherIP Flow VerifyNext HopEffective NSGsConnection TroubleshootIncident Diagnosis
1

Run IP flow verification

2

Inspect the effective next hop

3

Identify an injected incident

4

Repair and validate connectivity

Network Watcher Investigation TopologyAnimated packet path
AZURE NETWORK WATCHER / CONNECTIVITY INVESTIGATION SOURCE VM 10.10.1.4 NSG + ROUTE EVALUATION NETWORK WATCHER APPLICATION VM 10.20.1.4 : 443 DIAGNOSTIC EVIDENCE NSG RULE / NEXT HOP / TCP REACHABILITY SIMULATED NETWORK WATCHER WORKFLOW
Investigation readyDiagnostic evidence model

Diagnostic Tool Console

Select a Network Watcher investigation and inspect the result.

Diagnostic Console Ready

Run a diagnostic to inspect the current network state.

Network Incident ControlsNSG, routing and service state
The source VM has an allowed TCP 443 path to the destination application. The service is listening and the effective next hop is VNet peering.

Engineering Notes

How to interpret Network Watcher-style evidence.

IP Flow Verify: Identifies whether a tested flow is allowed or denied by applicable NSG rules.
Next Hop: Reports the next-hop type and address used for a destination.
Effective Security Rules: Combines applicable NIC and subnet NSG rules.
Connection Troubleshoot: Helps investigate reachability and relevant network conditions.
Packet Capture: Can collect traffic evidence on supported Azure VMs, subject to permissions and configuration.

Effective Network Diagnostic State

Review the current security, routing and application conditions.

Diagnostic LayerConfigurationExpected BehaviourStatus

Engineering Validation

Run IP flow verification, inspect next-hop routing, diagnose the injected incident and restore connectivity.

Begin with IP Flow Verify and Next Hop. Inject a production incident, diagnose it and restore connectivity.
NETWORK INSIGHT / NETWORK WATCHER EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 13
OBSERVE · ISOLATE · DIAGNOSE · REPAIR
Network Insight / Stage 05 / Lab 14

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.

Production IncidentsDNSNSGsUDRsAzure FirewallPrivate LinkRoot Cause Analysis
1

Establish healthy baseline

2

Diagnose DNS fault

3

Diagnose security fault

4

Diagnose routing fault

5

Restore production service

Enterprise Production Traffic PathAnimated investigation
AZURE PRODUCTION / MULTI-LAYER CONNECTIVITY INVESTIGATION CLIENT VM 10.10.1.4 DNS PRIVATE ZONE NSG / UDR POLICY FIREWALL INSPECTION APP 443 PRODUCTION INCIDENT INVESTIGATION BASELINE → FAULT → EVIDENCE → REPAIR → VALIDATION CONCEPTUAL CONTROL-POINT VIEW, NOT PHYSICAL PACKET ORDER
Production baseline readyFive-layer investigation

Production Incident Console

Select an incident and investigate its effect on the application.

Production Investigation Ready

Load an incident or validate the healthy baseline.

Diagnostic & Repair ControlsEngineering investigation tools

Repair Configuration

Modify the failed component and validate the result.

All production components are healthy. Select an incident to investigate.

Production Network State Comparison

Compare the current configuration with the expected healthy baseline.

ComponentHealthy BaselineCurrent StateValidation

Engineering Validation

Complete the healthy baseline, diagnose DNS, security and routing faults, and repair a production outage.

Start by tracing the healthy baseline. Load DNS, NSG and UDR incidents, run the matching diagnostics, then repair an outage.
NETWORK INSIGHT / PRODUCTION INCIDENT EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Lab 14
BASELINE · DIAGNOSE · REPAIR · VERIFY
Network Insight / Stage 05 / Lab 15 / Final Capstone

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.

Enterprise ArchitectureHub-SpokeVirtual WANAzure FirewallPrivate LinkHybrid NetworkingIncident Response
0/5INCIDENTS RESOLVED
0DIAGNOSTICS RUN
0SUCCESSFUL REPAIRS
ACTIVECAPSTONE STATUS
Enterprise Azure Production ArchitectureInteractive incident topology
ENTERPRISE AZURE / FINAL PRODUCTION CAPSTONE BRANCH 172.16.0.0/16 VIRTUAL WAN HUB ROUTING AZURE HUB FIREWALL / UDR APP VNET 10.20.0.0/16 PRIVATE DNS RESOLUTION PRIVATE LINK DATA SERVICES ENTERPRISE NETWORK OPERATIONS CENTRE OBSERVE / CORRELATE / REPAIR / VALIDATE CONCEPTUAL AZURE ARCHITECTURE
Capstone readyFive production incidents

Production Incident Queue

Select an incident, investigate the evidence and repair the affected component.

Capstone Investigation Ready

Load the first production incident to begin.

Engineering Diagnostic WorkbenchRoot-cause investigation

Root Cause Assessment

Choose the failed component before applying a repair.

The incident is waiting for investigation. Use the appropriate diagnostic tool before attempting the repair.

Capstone Engineering Rules

Each incident requires a complete evidence-based workflow.

1. Load the production incident.
2. Run the matching diagnostic tool.
3. Select the correct root cause.
4. Apply the correct repair.
5. Run the production trace again to verify recovery.

Enterprise Incident Resolution Matrix

Track each incident through investigation, repair and validation.

IncidentFailure DomainDiagnosisRepairFinal Status

Final Engineering Assessment

Resolve all five incidents and validate the enterprise Azure network.

Resolve all five production incidents to complete the final Azure Cloud Networking capstone.
NETWORK INSIGHT / ENTERPRISE CAPSTONE EVENT LOG
NETWORK INSIGHT — Azure Cloud Networking / Final Capstone
INVESTIGATE · DIAGNOSE · REPAIR · VALIDATE
Network Insight · Azure Learning Workspace · Stage 05

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.

Not Started
0 of 3 activities complete

Stage 05 Progress

0 / 3 · 0%
Complete the three troubleshooting and capstone activities.
ACTIVITY 01 · LAB 13 NOT COMPLETE
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.

ACTIVITY 02 · LAB 14 NOT COMPLETE
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.

ACTIVITY 03 · LAB 15 NOT COMPLETE
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.