Playbooks¶
Symptom-oriented Azure Networking playbooks organized by connectivity, DNS, and routing.
mermaid graph TD A[Reported symptom] --> B{Primary domain} B --> C[Connectivity] B --> D[DNS] B --> E[Routing] C --> C1[Inbound] C --> C2[Outbound] C --> C3[Private Endpoint] C --> C4[Intermittent] C --> C5[Latency and loss] D --> D1[Resolution failures] E --> E1[NSG vs UDR vs Firewall] E --> E2[Peering] E --> E3[Hybrid]
Core Cross-Domain Playbooks¶
| Playbook | Symptom |
|---|---|
| Connectivity Failures | VNet peering, NSG, route, or firewall issues break east-west or hybrid reachability |
| DNS Resolution Issues | Private DNS, Azure DNS, or hybrid forwarding returns wrong answers or timeouts |
| VPN Gateway Troubleshooting | S2S, P2S, and failover paths are disconnected or route traffic incorrectly |
| Load Balancer Health Probe Failures | Load Balancer backends show unhealthy because probes, policy, or return paths are wrong |
Connectivity¶
| Playbook | Symptom |
|---|---|
| Inbound Connectivity Issues | Clients cannot reach a published service or frontend |
| Outbound Connectivity Issues | Workloads cannot reach internet or external dependencies |
| Cannot Reach Private Endpoint | Private Link traffic fails or resolves incorrectly |
| Intermittent Network Failures | Flapping or time-window connectivity failures |
| Latency and Packet Loss | High RTT, jitter, or packet loss without hard denial |
DNS¶
| Playbook | Symptom |
|---|---|
| DNS Resolution Failures | Wrong IP, NXDOMAIN, timeout, or custom DNS forwarding issues |
Routing¶
| Playbook | Symptom |
|---|---|
| NSG vs UDR vs Firewall | Need to identify which policy or path component blocks traffic |
| Peering and Routing Issues | VNet-to-VNet paths fail across peering or transit assumptions |
| Hybrid Connectivity Issues | VPN or ExpressRoute tunnels/routes fail |