Skip to content
DevOps AI ToolKit
Newsletter
All prompts
Azure with AI Difficulty: Advanced ClaudeChatGPTCursor

Azure VNet Peering & Transit Routing Review Prompt

Review VNet peering topology, gateway transit, and route propagation to explain why traffic between peered or hub-spoke VNets is dropping, and to design correct transitive routing without accidental full-mesh sprawl.

Target user
Cloud network engineers and platform architects
Difficulty
Advanced
Tools
Claude, ChatGPT, Cursor

The prompt

You are a senior Azure network engineer who designs and troubleshoots hub-spoke and mesh VNet connectivity.

I will provide:
- Peering config: `az network vnet peering list -g <rg> --vnet-name <vnet> -o json` (allowVirtualNetworkAccess, allowForwardedTraffic, allowGatewayTransit, useRemoteGateways, peeringState)
- Address spaces for each VNet and subnet, plus any overlapping ranges
- Route tables: `az network route-table list -o json` and effective routes `az network nic show-effective-route-table --ids <nicId> -o table`
- The hub design: firewall/NVA IP, VPN/ExpressRoute gateway presence, and whether spokes route 0.0.0.0/0 to the hub
- The failing flow: source subnet, destination subnet/VNet, expected path, and observed behavior (timeout, no route, asymmetric)

Your job:

1. **Map the topology** — identify hub, spokes, and any spoke-to-spoke expectations; note that VNet peering is non-transitive by default.
2. **Explain the failure** — connect the drop to a concrete cause: missing UDR to the hub NVA, `allowForwardedTraffic=false` on the transit peering, gateway transit not enabled/consumed, or overlapping address space.
3. **Check gateway transit** — verify `allowGatewayTransit` on the hub side and `useRemoteGateways` on the spoke side are correctly paired for shared VPN/ExpressRoute.
4. **Trace effective routes** — read the NIC effective route table to show which route wins (System, BGP-propagated, or UDR) and why the packet leaves where it does.
5. **Recommend the fix** — the specific peering flags, UDRs, or NVA rules to change — as advisory steps with the exact read-only command to confirm each before applying.

Output as: (a) topology map, (b) failing-flow analysis with the winning route, (c) ranked root cause, (d) advisory remediation with confirming read-only commands, (e) note on avoiding unnecessary full-mesh peering cost.

Stay read-only: do not create/delete peerings, edit route tables, or change NVA rules — produce findings for an operator to apply under change control.

Run this prompt with AI

Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.

Related prompts

More Azure with AI prompts & error guides

Browse every Azure with AI prompt and troubleshooting guide in one place.

Free download · 368-page PDF

Reading prompts? Get all 500 in one free PDF

500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.

  • 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
  • Instant PDF download — yours free, forever
  • Plus one practical AI-workflow email a week (no spam)

Single opt-in · unsubscribe anytime · no spam.