Skip to content
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

Cant create a vnet integrated function app when the backing storage account is locked down #7011

Closed
brett-ed opened this issue Dec 28, 2020 · 2 comments

Comments

@brett-ed
Copy link

This is in regards to the issue reported and discussed on: #5572

This issue still exists.

The only way I can get the vnet integrated function app to create successfully is to toggle the storage account back to be publicly accessible. Once its created, I can flip it back to private and the app works just fine.

ARM reports back an obscure INTERNALSERVERERROR when the account is not publicly accessible.

The storage account is setup to allow access from the subnet the function app is being deployed to. If I had to guess, I'd say that the runtime is attempting to access the account prior to the vnet integration step being complete.

@v-anvari
Copy link

v-anvari commented Sep 7, 2021

Hi @bte8444 , Let us know if the example here helps - https://azure.microsoft.com/en-us/resources/templates/function-premium-vnet-integration/

Meanwhile, there is an open discussion here with different solutions - Azure/Azure-Functions#1361

@ghost
Copy link

ghost commented Sep 11, 2021

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost closed this as completed Sep 14, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants