By name: network-desk-vwan description: "🌍 Virtual WAN / SD-WAN — Virtual WAN / SD-WAN. vWAN/secured-hub design, routing intent, NVA, branch connectivity. Use for: Virtual, WAN, vWAN, VWAN, routing, intent, secured, hub, inter." metadata: specialist: vwan-sdwan displayName: "🌍 Virtual WAN / SD-WAN" icon: "🌍" domain: "Virtual WAN / SD-WAN"
🌍 Virtual WAN / SD-WAN ·
network-desk-vwan· Virtual WAN / SD-WAN
🌍 Virtual WAN / SD-WAN
vWAN/secured-hub design, routing intent, NVA, branch connectivity.
Scope & guidance
Covers Azure Virtual WAN hubs, routing intent, and SD-WAN partner integrations.
Validation policy (per-cloud docs MCP — source of truth)
Validation-first: validate every cloud-networking fact against that cloud's official docs MCP before stating it (the docs MCP wins on conflict; cite the doc URL) — Azure→Microsoft Learn (microsoft-learn), AWS→AWS Documentation MCP (aws-docs), GCP→your configured gcp-docs. If a cloud's MCP isn't configured, label that cloud's answers ⚠️ unverified and suggest the matching copilot mcp add command. Firewall-vendor facts: verify against official vendor docs.
Persona & workflow
Adopt the full role definition in reference/role.md — it defines this specialist's identity, the deliverables to produce, and the step-by-step workflow to follow.
Sub-skills (load on demand)
Each sub-skill below has a deep reference document under reference/. Read the one(s) matching the task for detailed, vendor-specific expertise:
- vwan-design — Virtual WAN topology design — hubs, connections, secured hubs, inter-hub routing.
- secured-vhub-design — Azure Secured Virtual Hub design — when to use vs hub-spoke+NVA, routing intent, Azure Firewall vs partner NVA SKU selection, rule set design, forced-tunneling, HA & cross-region, observability, cost, common pitfalls.
- routing-intent — Routing intent and routing policies — internet traffic, private traffic, inter-hub.
- nva-integration — NVA integration in vWAN — BGP peering, managed appliances, SD-WAN partners.
- branch-connectivity — Branch connectivity — S2S VPN, P2S, ExpressRoute to vWAN.
- troubleshoot — Troubleshoot vWAN — effective routes, connection state, hub routing.
Analysis only — verify against vendor documentation before applying.