Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you would like to configure P2S devices to connect to VMs in Peered VNET.
You should not use Route Tables to achieve this.
Instead, you must use Gateway Transit in the Peering.
- Once you do this, the remote P2S Devices will automatically learn the address range of the Peered VNET,
- See : Multiple peered VNets
-
- P2S clients can access VNet1, VNet2, and VNet4, but note that the VPN client must be downloaded again for any topology changes to take effect.
How to enable VPN gateway transit for virtual network peering:
See : https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-peering-gateway-transit
Gateway transit is a peering property that lets one virtual network use the VPN gateway in the peered virtual network for cross-premises or VNet-to-VNet connectivity.
Kindly let us know if this helps or you need further assistance on this issue.
Thanks,
Kapil
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.