Reputation: 139
Ok this is to save someone else 4 days of work.
Trying to use VNet integration to connect an Azure Function in the North Central US region to a storage account in the US West region. The storage account in the US West region has the firewall enabled. The only reason I am posting this is our staff normally sets this up for virtual machines which have an IP address that can be added into the storage account firewall and not app service plans.
Upvotes: 0
Views: 2383
Reputation: 139
If you want to secure your azure storage behind a private endpoint and you want a service plan (I.E. Azure Function or Web App) to access said storage account.
When the storage account firewall is disabled. An App service in the same Vnet containing the storage account endpoints (within a subnet for the app service) works. So to further clarify. You would have a Vnet with the default subnet, a storage subnet, and a app subnet. The storage account firewall is off. Then the web app can access the endpoints that you setup in the storage subnet.
When the storage account firewall is enabled.
Also a subnet that is not within the same region or a region pair will not show up in the storage account firewall for you to add it.
There is the option to try a preview feature AllowGlobaltagsForStorage but I cannot use that within a production environment.
So to clarify this:
With this setup you can simply use the storage account connect string and everything should work as long as you have the endpoints setup that you need.
So my fix was to move my setup to the US West region.
Upvotes: 0