Azure-docs: Storage Account firewall

Created on 13 Nov 2019  Â·  4Comments  Â·  Source: MicrosoftDocs/azure-docs

I could still connect to storage account from outside the Vnet even after enabling Private endpoint. I could no longer connect to the Vnet after selecting firewall rule "Selected networks" (as it is supposed to be) and saving it without any white listing whatsoever.
My question is that, are we supposed to enable firewall on a storage account to make it private after configuring private endpoints?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 cxp in-progress private-linsvc product-question triaged

All 4 comments

@geoano Azure Private Link allows you to access resources via a DIP in your VNET. VNETS that do not have outbound internet connectivity will still be able to access the resource.

If you would like to make the storage account private and accessible only from your virtual networks, then you can enable the storage account firewall. This is not a required configuration and you can set it as needed for your environment.

Please let me know if you need any additional clarification.

@geoano , Do you have any update on this issue?

@geoano We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@geoano I too am having this problem. I have "Selected Networks" chosen and have the subnet containing the Private Endpoint added to the list. I see that I can add my public IP to the whitelist of the firewall but that would only allow traffic coming from my IP over the Internet which is not what I'm trying to accomplish. How should the firewall on the storage account be configured to allow traffic from on-prem (via expressroute) to the storage account without going over the Internet?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Favna picture Favna  Â·  3Comments

mrdfuse picture mrdfuse  Â·  3Comments

JamesDLD picture JamesDLD  Â·  3Comments

JeffLoo-ong picture JeffLoo-ong  Â·  3Comments

bdcoder2 picture bdcoder2  Â·  3Comments