Same scenario: Client1 uses P2S IKEv2 to VNet1; VNet1 peered to VNet2 with gateway transit enabled. Client1 cannot reach VNet2. Solution: enable BGP on VNet1's gateway. Does this solution meet the requirement?

Enabling BGP on VNet1's gateway is not sufficient. While gateway transit allows VNet1 to use VNet2's gateway for connectivity to other networks, it doesn't automatically extend P2S client routes from VNet1 to VNet2. For a P2S client connected to VNet1 to reach VNet2, VNet1's virtual network gateway needs to advertise the VNet2 address space to the P2S client. This typically requires configuring the P2S VPN gateway in VNet1 to include VNet2's address space in its routing information, or ensuring the peering configuration correctly propagates routes. Simply enabling BGP on the VNet1 gateway without proper route propagation or P2S client configuration will not resolve the issue.