Inspect on-premises traffic with Azure Firewall
srv-onprem can't reach vm-spoke1 on 443.
- Get srv-onprem reaching vm-spoke1 on 443 through azfw-hub
- Keep SSH from on-premises to vm-spoke1 blockedbroken
Background
Security wants all traffic between vm-spoke1 and on-premises inspected by azfw-hub at 10.0.1.4. rt-spoke1 already sends 192.168.0.0/16 to the firewall. Traffic from on-premises enters Azure at vgw-hub, in the hub's GatewaySubnet. srv-onprem needs to reach vm-spoke1 on 443, and nothing works yet. SSH from on-premises must stay blocked.
- 1See it fail
Prove the problem yourself before you change anything. Reports are often wrong.
VM commands forVMsssh srv-onpremWhat's this?
Opens a shell on srv-onprem, so the next commands run on that VM. In this lab it's a shortcut. In real Azure you'd connect through something like Azure Bastion, or SSH to an address you can reach.
nc -zv 10.1.1.4 443What's this?
netcat, a standard Linux tool. Tries to open a TCP connection and reports whether it worked.
-zonly check whether the port answers. Send no data-vprint the result in words10.1.1.4where to connect443the port to try
Ticks off when the test runs on srv-onprem.
- 2Find where it stops
- 3Name the cause
- 4Fix it and test again
- 5Explain it
?
- 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.
srv-onprem → vm-spoke1:443should work: not workingsrv-onprem → vm-spoke1:22should stay blocked: blocked