An Azure network security service that is used to protect Azure Virtual Network resources.
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