Enable "vNet peering" as UDR next hop
Enable "vNet peering" as UDR next hop. Currently if you have a large range, a /16 for example, set in a UDR with a next hop of an NVA it is not possible to override or point a single subnet, for example a /24, in the /16 at the vNet Peering. This would be useful to bypass an NVA for certain subnets or IPs.
Robert Colbert commented
I actually have the something close to the opposite problem. Our peer network has multiple subnets and the default peer route bypasses our NVA when it shouldn't. We need the ability to disable the creation of the default peer route and add it manually where needed (for the NVA subnet only) in the peer.
I second this request.
Having peered vNets without NVA and wanting to force just certain subnets directly over the peering and invalidating the system default vNet peering for all subnets.