Private subnet still can't reach the internet
Problem
vm-app can't reach updates.example.org, even though nat-gw exists.
Your job
- Get vm-app reaching updates.example.org through nat-gw
Without breaking
- Don't give vm-app a public IP of its ownbroken
Background
vm-app in the private subnet-app still can't reach updates.example.org on 443, even though nat-gw exists and has a public IP, pip-nat. A month ago traffic went through an appliance in the hub that has since been removed. vm-app must not get a public IP.
How to work it
- 1See it fail
This traffic starts outside the lab VMs, so you can't log in to test it. Watch it instead.
Tap Explain on the red line under the map.
Ticks off when you tap Explain on the broken line.
- 2Find where it stops
- 3Fix it and test again
Sources on Microsoft Learn (2)
0/2 changes
Network map
?
- Resource group, the outer dashed frame
- Virtual network, with its address space top right
- Subnet, with range and usable IPs (5 reserved)
- Network security group. A small shield on a VM's NIC means the NIC has one too
- Route table on the subnet
- VM Appliance Private endpoint
- Peering Connected Initiated or access off
- Goal working Goal broken, X marks where it stops
- Private DNS zone, dotted lines go to linked VNets
- Orange pulse: what your last command changed. Drag to pan, Ctrl and scroll to zoom.
Goals 0/2
Cloud Shell · bashVMsrg-lab · eastus2
cloudshell:~$