Azure Internal LB used as next hop

Peter Stieber 130 Reputation points
2026-11-04T16:16:25.0666667+00:00

I'm using an internal Standard Load Balancer in front of a single NVA, with the frontend IP used only as a UDR next hop (never as the packet's destination).

SETUP

  • Two peered spoke VNets. Each spoke subnet has a UDR 0.0.0.0/0 with next hop type VirtualAppliance and next hop IP = the LB frontend IP.
  • The real destination is always the other spoke VM's own IP.
  • Health probe: TCP/22, healthy throughout (DipAvailability 100%).
  • NSGs on both spokes and the NVA allow all traffic between the spoke and hub CIDRs (checked with az network nic list-effective-nsg).

PROBLEM

Configuration A: one non-HA-ports rule

  • Protocol TCP, frontend port 22, backend port 22, Floating IP disabled. No HA ports rule exists.
  • Test: spoke1 to spoke2 on TCP/22 via the UDR next hop.
  • Result: the connection times out. A packet capture on the backend NIC shows zero packets arriving (no reset, no rejection, nothing delivered), even though the rule matches the protocol and port and the backend is healthy.
  • I replaced the NVA with a plain Ubuntu VM (net.ipv4.ip_forward=1, no firewall) and got the same result.

Configuration B: one HA ports rule

  • Frontend port 0, backend port 0, protocol All, Floating IP disabled. Same frontend IP, backend pool, probe and VM.
  • The same TCP/22 test succeeds.

The two rules differ in the port/protocol setting. Everything else was identical.

QUESTIONS

  1. Is it documented anywhere that a protocol/port-specific rule cannot forward UDR next-hop traffic to a backend pool, even when the traffic's protocol and port match the rule? The HA ports overview describes HA ports for NVA scenarios but doesn't say this explicitly.
  2. If so, is the reason that non-HA-ports rules only match traffic actually addressed to the frontend IP, with no "any destination, this port" flow like HA ports has?
  3. Has anyone seen the same behavior, with a specific-port rule not forwarding next-hop traffic until it was switched to HA ports?

I can share az network lb rule show output, effective route tables or packet captures if useful.

Azure Firewall
Azure Firewall

An Azure network security service that is used to protect Azure Virtual Network resources.

0 comments No comments

1 answer

Sort by: Most helpful
  1. James Gamble 340 Reputation points
    2026-11-04T16:26:00.0733333+00:00

    Hola Peter,

    Your controlled testing makes a pretty convincing case that the difference comes down to how Azure handles ordinary load-balancing rules versus HA Ports rules.

    Microsoft documents standard load-balancing rules as mappings between a frontend IP/port and backend IP/port. HA Ports, however, are specifically designed for scenarios involving network virtual appliances (NVAs) and user-defined routes, where the packet's actual destination differs from the load balancer's frontend IP.

    This explains why matching TCP/22 isn't necessarily sufficient. Your UDR uses the load balancer's frontend IP as the next hop, but the packet is still addressed to the destination VM in the other spoke. An ordinary TCP/22 rule isn't documented as supporting that transit behavior, whereas HA Ports explicitly supports NVA forwarding.

    Microsoft's reference architecture also confirms that HA Ports is the intended configuration for this type of traffic.

    Your results are consistent with that, particularly since changing only the rule type immediately resolved the problem.

    I couldn't find documentation that explicitly confirms the internal packet-classification behavior or categorically states that port-specific rules cannot forward UDR next-hop traffic. That would require confirmation from Azure engineering.

    I'd stick with Configuration B, which follows Microsoft's documented design. If you need definitive confirmation of why Configuration A drops the packets, an Azure Support case with your existing captures and rule configurations would be the appropriate next step.

    Thanks,

    James

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.