-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot publish a function from Visual Studio if backing storage account restricts access through firewall #2536
Comments
Hi @ADH-LukeBollam Thanks for reporting Don't use direct option .you can refer other option for publish https://learn.microsoft.com/en-us/azure/azure-functions/functions-deployment-technologies?tabs=windows |
The alternatives add complexity that I would prefer to avoid right now, will there be a fix for the issue? It's not great to have to expose the storage to the internet to simply publish an app. |
What specifically are you referring to in there? |
hi @bhagyshricompany , I've followed the instructions for connecting an azure function to a secured storage: Can you please tell me specifically which part you wanted me to look at so I can publish without having to expose the storage? |
@kshyju please comment and validate. |
I have a premium function with a backing storage account. The function is on a subnet of a virtual network, and the backing storge is connected to the same subnet via a Service Endpoint. I have also added my own IP address to the function whitelist so that I can publish.
If the backing storage account is locked down behind a VPN, a number of issues start happening:
You get this error in the Overview:
With these details:
You also cannot publish from Visual Studio anymore:
"Error : The attempt to publish the ZIP file through ****/api/zipdeploy failed with HTTP status code InternalServerError."
You also cannot swap, with another Internal Server Error.
Adding my own IP to the backing storage whitelist did not resolve this. The only way I could successfully publish was to enable access from all networks on the backing storage.
The text was updated successfully, but these errors were encountered: