You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: