0
votes

I have a P2S VPN to connect to an Azure subscription that contains several servers I want to access. Connecting from my private Notebook to this P2S VPN works perfectly.

In addition I have my own Azure subscription containing several virtual machines. Now I can setup the P2S VPN Client on each of these. However, this does not seem to be an elegant solution. I'd like to just create one VNET and connect this VNET to my existing P2SVPN. Then I could connect all my virtual machines to that VNET and would be very happy.

How can this be done? All my research just shows how to connect a client to the P2S VPN. Other pages show how I can connect to one VNET and setup a S2S VPN to another VNET.

Thanks

2
Are all machines in the same tenant? When you login to 'the portal' can you see all machines?Hannel
No the systems are located in totally different regions with totally different administrators in no shared subscription.Felix

2 Answers

0
votes

You can implement a hub-spoke topology in Azure. The topology like this:

enter image description here

You can connect your VMs in different Vnet just through only one Vnet. And this topology overcomes subscriptions limits by peering VNets from different subscriptions to the central hub. For more details, see Implement a hub-spoke network topology in Azure. Hope this would be helpful.

0
votes

Since VMs (subscriptions) are not in the same Tenant, it will be easier to just have a P2S connection for each.

Peering will not work, but you can setup S2S for both VNet but that is not a feasible solution.