allow Bastion used in VWAN spoke Vnets
For spokes VNETs of VWAN, currently, bastion is not supported like this:
Bastion (Spoke 1) -> Hub -> VM (Spoke 2).
Support for Bastion via a peered vnet connected to our VWAN hubs would literally remove the need for jump boxes in our Azure environment. Given the push for customers to move to Azure VWAN if this capability is not present it really should be high on the priority list as it improves our environment security and governance while reducing complexity and costs.