Your subscription contains VirtualNetworkA (which has a static-routing VPN gateway and a site-to-site VPN to your on-premises network) and VirtualNetworkB. You configured a point-to-site VPN from a Windows 10 workstation to VirtualNetworkA and peered VirtualNetworkA with VirtualNetworkB. On-premises systems can reach VirtualNetworkB, but the Windows 10 workstation cannot. You must allow the workstation to connect to VirtualNetworkB. Solution: enable Allow gateway transit on VirtualNetworkA. Does this meet the requirement?

Enabling "Allow gateway transit" on VirtualNetworkA is not sufficient. This setting allows VirtualNetworkA to use VirtualNetworkB's gateway (if VirtualNetworkB had one and "Use remote gateways" was enabled on VirtualNetworkA), or allows VirtualNetworkB to use VirtualNetworkA's gateway if "Use remote gateways" is enabled on VirtualNetworkB. To allow the Windows 10 workstation (connected via P2S to VirtualNetworkA) to reach VirtualNetworkB, you need to enable "Allow gateway transit" on the peering link from VirtualNetworkA to VirtualNetworkB, AND enable "Use remote gateways" on the peering link from VirtualNetworkB to VirtualNetworkA. This ensures that VirtualNetworkA's VPN gateway can forward traffic to VirtualNetworkB. Additionally, the P2S client configuration will need to be updated to include the routes for VirtualNetworkB.