Access Azure Storage on Local Laptop Via Azure VPN Client and Virtual Network Gateway

Hi Tom McCartan,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you're experiencing issues with using Azure Storage Explorer to connect to your Azure Storage Account and access the blobs.

 Storage accounts use a Private Endpoint, it likely has a DNS configuration that resolves to private IP addresses within your virtual network. Public internet users cannot use this DNS to reach the storage account.

You need to configure the storage account to allow public network access. This can be done by setting the Allow option for public network access on the storage account configuration.

In the Firewalls and virtual networks settings of the storage account, you can define the public IP addresses or IP ranges that are permitted to access it.

Regarding the FQDN, when public access is enabled, the storage account can be accessed through its public endpoint, usually formatted https://<account_name>.blob.core.windows.net. If public access is restricted to specific IPs, this will be the endpoint they utilize.

If you have any further concerns, please do not hesitate to contact us.

We are pleased to help you.

If the information is helpful, please click on "Upvote" and "Accept Answer" so that it would be helpful to other community members.

But I thought that if you create a Virtual Network Gateway in your VNET, with a Point-to-site configuration, you can use Azure VPN Client to connect to the Virtual Network Gateway. This way it is like you are inside the VNET and can connect to Azure Storage using the Private Endpoint using the Private IP.

In our case, we can't allow Public Access, or allow specific firewall rules to be configured to allow specific IP Addresses. This is due to compliance. But we need our local developers to access the Storage Account. Or SQL Server, etc. By using a VPN.

So how can you configure a VPN to be used by Local Developers to connect to the Azure VNET and access the resources, like Storage, and SQL Server?

Thanks,

Tom

But I thought that the purpose of a Virtual Network Gateway, was to be able to configure a Point To Site to your VNET and by using a VPN Client, you could connect to the VNET through the VNG.

We can not allow our Storage Account to be Publicly available, or allow IP Addresses thought he firewall, due to security and compliance restrictions.

But we need to have our local developers connect to a VPN, to allow secure private access to the VNET Resources like Storage and SQL Server, etc.