You should add a route table and add a route to vnet2 through vpn-gateway-1.
And add any routes you might need to access external networks from vnet2 via vpn-gateway-1.
Hope this helps.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This is the setup currently
vnet1 in subscription 1
vnet2 in subscription 2
vpn-gateway-1 is linked to vnet1
vnet1 & vnet2 are linked to each other using vnet to vnet connection
using vpn-gateway-1 i can connect to resources of vnet1 however I cannot connect to resources of vnet-2
Is it possible to achieve this?
Reason:
I have reports which uses SQL Azure from both this subscriptions and I do not want to expose either of SQL Server to public internet.
You should add a route table and add a route to vnet2 through vpn-gateway-1.
And add any routes you might need to access external networks from vnet2 via vpn-gateway-1.
Hope this helps.
@Anonymous , P2S configuration with global VNET peering is possible in Azure. To achieve this, you need to peer the VNETs before the VPN client/profile is downloaded otherwise the profile will not have routes to the peered vnets.
Here is a doc for quick reference.
----------
Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.