Hi Cat Mucius,
I understand that you want to allow Spoke VNETs to send traffic to NVA without manual UDR overrides for each prefix from VPN Gateway and also enable VPN Gateways to automatically learn Spoke VNETs' prefixes and route traffic via NVA. Your actual configuration can be showed as this one:
The solution will require deploy an Azure Route Server in the HUB VNET, This enables dynamic route propagation and learning between components. Bellow configuration required:
- Peer the NVA with the Azure Route Server to advertise learned routes.
- Peer the VPN Gateway with the Azure Route Server to dynamically learn Spoke VNET prefixes.
- On Spoke VNETs set a default route (0.0.0.0/0) pointing to the NVA for outgoing traffic
- On HUB VNET GatewaySubnet include a UDR to send all traffic destined for on-premises to the NVA first, then to the VPN Gateway.
Therefore the Traffic Flow on Spoke VNETs send traffic to the NVA due to the default route and VPN Gateway learns Spoke VNET prefixes from the Route Server and routes traffic through the NVA, ensuring traffic inspection before it reaches its destination.
This configuration, eliminates the need for manual UDR updates for each prefix and ensures all traffic from Spoke VNETs is inspected by the NVA before reaching on-premises or other destinations.
References:
- https://zcusa.951200.xyz/en-us/azure/route-server/peer-route-server-with-virtual-appliance
- https://zcusa.951200.xyz/en-us/azure/route-server/route-server-faq
- https://zcusa.951200.xyz/en-us/azure/virtual-network/virtual-networks-udr-overview
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Regards,
Luis