Access Azure Key Vault and/or Azure Storage via Site to Site VPN from local network.

Copper Contributor

The following article explains how to establish a site to site VPN with an Azure VNET (not a public IP space).


This article shows how to lock down Azure Key Vault to only allow access from a specific Azure VNET.


My question is why couldn’t we establish Azure Key Vault in an Azure VNET that is accessible only from a site to site VPN?  If we can, it eliminates the “Public IP” access that is concerning to me for access to Credential data.


Additionally, this article makes me think we could do the same thing with Azure Storage.


The basic approach would be:


1. Establish a Key Vault locked down to the VNET only.

2. Establish a Site to Site VPN with access to the VNET from a local subnet.

3. Update Key Vault Network Security to allow access from the local subnet IP space

4. Voila private access to Key Vault from protect local network space.


Does anyone have experience with such a configuration?

2 Replies



This is a roadmap item for Key Vault.  The solution will provide a private IP address within your VNET that maps to your keyvault instance. The Private IP will be accessible over ER, S2S VPN, P2S VPN.   In the short-term a potential workaround could be using AzFW as a TCP Broker.  AzFW provides a private IP facing on-premises (S2S VPN) and you enable service endpoints on the AzFW subnet and you white-list the vnet/subnet/azfw to have access to keyvault.   You can further whitelist the FQDN of KeyVault on AzFW as well.  

@Jason Gmitterwould it be possible for you to provide some Azure CLI examples of setting up the workaround?  My issue is that I don't have a "sandbox" to test things out in and I need to provide ideas to the implementation team.  Thanks for this response btw, it helps a lot!