Learn Cloud NetAzure networking, beginner to advanced0 XP0/80
Your path

Explore a virtual network

Beginner · Level 1 · Foundations

0 of 80 levels solved · 0 XP
Start level 1
1

Beginner Guided

One concept per level. Every command is shown and explained, flag by flag.

0/15

Foundations

  2. 2Read CIDR and create a VNetLevel 2
  3. 3Carve subnets from an address spaceLevel 3
  4. 4Find a VM's NIC and private IPLevel 4
  5. 5Add address space to a VNetLevel 5

Security

  1. 6Create and attach an NSGLevel 6
  2. 7Find the blocking rule with IP flow verifyLevel 7
  3. 8Allow HTTPS with a service tagLevel 8
  4. 9Block outbound SSH with an NSG ruleLevel 9
  5. 10Attach an NSG to a single NICLevel 10

Routing

  1. 11Read effective routesLevel 11
  2. 12Drop traffic with a route tableLevel 12

Connectivity

  1. 13Peer two VNetsLevel 13

Name resolution

  1. 14Create a private DNS zoneLevel 14

Review

  1. 15Review: peer two VNets and add an NSGLevel 15
2

Intermediate Symptom and tools

Real break/fix issues. You get the symptom and the diagnostics, not the command.

Locked

Traffic filtering

  1. 1HTTPS blocked despite an allow ruleLevel 1
  2. 2API blocked despite a subnet allow ruleLevel 2
  3. 3App can't reach its databaseLevel 3
  4. 4Peered partner can't reach the web appLevel 4

Peering

  1. 5Spoke can't reach the hub after peeringLevel 5
  2. 6Peer a spoke built from an old templateLevel 6
  3. 7Hub can't reach a new subnet in a spokeLevel 7

Routing

  1. 8Route spoke-to-spoke traffic through the hubLevel 8
  2. 9Spoke-to-spoke down after an overnight rebuildLevel 9
  3. 10Spoke-to-spoke down after maintenanceLevel 10
  4. 11Spoke-to-spoke down after the appliance was reimagedLevel 11

Peering

  1. 12Spoke-to-spoke fails through a new hubLevel 12

Name resolution

  1. 13Storage returns 403 from a spokeLevel 13
  2. 14Private endpoint name doesn't resolveLevel 14

Review

  1. 15Review: spoke can't reach a hub APILevel 15
3

Advanced Stacked faults

Several things wrong at once across hub and spoke, hybrid, PaaS, DNS, outbound, load balancing, the VM itself, Azure Firewall and Bastion.

Locked

Hub and spoke

  1. 1New spoke can't reach the other spokeLevel 1
  2. 2Spoke-to-spoke down after a redeployLevel 2

Hybrid

  1. 3Use the hub's VPN gateway from a spokeLevel 3
  2. 4Spoke can't reach on-premisesLevel 4
  3. 5On-premises users can't reach a spoke appLevel 5
  4. 6New spoke can't reach on-premisesLevel 6

PaaS access

  1. 7Allow a subnet through a storage firewallLevel 7
  2. 8VM can't reach storage locked to selected networksLevel 8
  3. 9Storage returns 403 after public access was disabledLevel 9

Review

  1. 10Review: spoke, gateway and an old routeLevel 10

DNS

  1. 11Resolve private endpoints with a custom DNS serverLevel 11
  2. 12Private endpoint resolves wrong with custom DNSLevel 12
  3. 13Resolve names with DNS Private ResolverLevel 13
  4. 14Finish a DNS Private Resolver migrationLevel 14
  5. 15Spoke can't resolve on-premises namesLevel 15
  6. 16On-premises can't reach a private endpointLevel 16

Review

  1. 17Review: storage, DNS servers and a missing recordLevel 17

Outbound access

  1. 18Give a private subnet internet accessLevel 18
  2. 19Private subnet still can't reach the internetLevel 19

Load balancing

  1. 20Load balancer backends marked downLevel 20
  2. 21Load balancer down after a port changeLevel 21

Inside the VM

  1. 22Check the VM's own firewall and appLevel 22
  2. 23Load balancer marks both backends downLevel 23
  3. 24App is up, but Spoke 2 can't reach itLevel 24

Review

  1. 25Review: outbound, load balancer and an old ruleLevel 25

Azure Firewall

  1. 26Allow traffic through Azure FirewallLevel 26
  2. 27Azure Firewall blocks allowed HTTPSLevel 27
  3. 28Inspect on-premises traffic with Azure FirewallLevel 28

Bastion

  1. 29Deploy Azure BastionLevel 29
  2. 30Bastion deployment failsLevel 30
  3. 31Bastion can't reach a VM in a spokeLevel 31

Review

  1. 32Review: firewall, DNS and BastionLevel 32
4

Expert Incident mode

A complaint in the words users use, one or more faults, sometimes not in the network at all. No hints, and a clock.

Locked

Incident

  1. 1The reports site is downLevel 1
  2. 2The intranet site is downLevel 2
  3. 3Spoke 2 can't reach Spoke 1Level 3
  4. 4Monitoring lost both app serversLevel 4
  5. 5Uploads keep failingLevel 5
  6. 6Checkout times out for everyoneLevel 6
  7. 7The office can't get inLevel 7
  8. 8Servers can't download updatesLevel 8
  9. 9The firewall broke everythingLevel 9
  10. 10The partner API rejects the new job serversLevel 10
  11. 11Locked out of the app serverLevel 11
  12. 12Some users get errors, others are fineLevel 12
  13. 13Corp names stopped resolvingLevel 13
  14. 14The office can't reach the HR appLevel 14
  15. 15The wiki is goneLevel 15
  16. 16The API stopped answering Spoke 1Level 16
  17. 17Order app can't reach its database or storageLevel 17
  18. 18Nothing works on launch dayLevel 18
Your skills by topic
Foundations0 of 5 levels
Security0 of 5 levels
Routing0 of 6 levels
Connectivity0 of 1 levels
Name resolution0 of 3 levels
Traffic filtering0 of 4 levels
Peering0 of 4 levels
Hub and spoke0 of 2 levels
Hybrid0 of 4 levels
PaaS access0 of 3 levels
DNS0 of 6 levels
Outbound access0 of 2 levels
Load balancing0 of 2 levels
Inside the VM0 of 3 levels
Azure Firewall0 of 3 levels
Bastion0 of 3 levels
Incident0 of 18 levels
Clear my progress

This removes all stars and unlocks saved in this browser.