Deploying an Azure Function or App Service inside a VNET makes it difficult to connect with storage accounts, leading to plenty
"Storage access failed. Storage volume is currently in R/O mode" errors. We ran into similar issues as other people with deploying the application code to file share, but were able to successfully deploy this using the regularly references solution of setting "WEBSITE_CONTENTOVERVNET"=1. However, have been unable to have such luck with enabling the App Service Logs to be able to review the log stream.
We have tried several options, including the one references here: https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-diagnostic-logs#networking-considerations. But regardless of how we configure our storage account we seem unable to get beyond this "Storage access failed. Storage volume is currently in R/O mode" error. We have tried:
- storage accounts with no networking rules (same and different regions)
- storage accounts in the same subnet (same and different regions)
- storage accounts in the same vnet but different subnets (same and different regions)
(we are unable to use service endpoints due to company policies)
When inspecting the storage account logs of these experiments we only find 404 errors for missing $logs or $blobchangefeed, or the proper path expected for the app service logs. Sometimes even all 200 responses. Where is this error coming from, and how can we get around it?