[Premium] Azure Function on a VNET can't start because of no access to zip using WEBSITE_RUN_FROM_PACKAGE
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 215
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 1
Description
**Describe the bug**
When on a premium plan, and on a VNET, where the azure function is deployed using WEBSITE_RUN_FROM_PACKAGE. The Azure function cannot start. It has no access to the zip configured in WEBSITE_RUN_FROM_PACKAGE.
We have tried whitelisting the IP addresses of the azure function. But this does not work.
When we create a separate storage account which is not on a vnet. Only to make the zip available. Then configure WEBSITE_RUN_FROM_PACKAGE to get the zip from this location. Then the azure function is able to download the zip and runs fine.
**To Reproduce**
Steps to reproduce the behavior:
Run an azure function on a premium plan, use a vnet and deploy the azure function using WEBSITE_RUN_FROM_PACKAGE.
**Expected behavior**
The azure function should be able to download the zip.
**Additional context**
We are going to try to deploy using an alternative. Like with a Docker container.
If there are other alternatives to deploy the azure function. please let us know.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.