Score:0

Azure VPN (P2S OpenVPN) - no connection to public internet via VPN

az flag

Our IT landscape is based on the cloud and utilizes IP whitelisting for access to it. This has been working just fine though all summer as our offices IP addresses are whitelisted. Now that our offices have closed again due to covid, I am working on a solution to allow developers to access all cloud resources from home, without whitelisting private people's IP Addresses.

To solve this problem, I want to implement a VPN, that will tunnel all requests to the services which require whitelisting. When developers are using the VPN, they should all come out at the same public IP which I will then whitelist.

I've been able to setup an Azure VPN with a P2S Configuration and the OpenVPN tunnel type. It is in it's own virtual network that has no peerings to any other virtual networks (because I do not want any connectivity inside the azure network) I've also setup the appropriate IP routes.

However, when I connect to the VPN and try to open our development resources, they do not load but instead socket timeout (seems as if all packets are dropped).

I am quite stuck here, as I can't find any useful information to what could be missing to get this setup to work the way I would want it to work.

I would appreciate any hint and suggestions to make this work.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.