Enable App Service without ASE to access Storage Account with Firewall enabled
Currently it is not possible to configure storage account firewall to accept requests from App Services without ASE. This requires App Service to enable trusted access to storage: https://docs.microsoft.com/en-us/azure/storage/common/storage-network-security#trusted-microsoft-services.
It is great if above is possible.
Masayuki Tanaka
shared this idea
Thank you for the feedback. We understand the limitation and will update this ticket as information becomes available.
- Jason
50 comments
-
Anonymous
commented
+10 (Also should be open for Functions, but guess that should be the same)
-
Illbegood
commented
I have a desktop app accessing some Azure File Shares setting firewall, now I need to access the same shares from a Web Api published on Azure Web App and I've been forced to disable firewall because even selecting Allow trusted Microsft Services I receive a 403 error accessing the files. Please fix this issue as soon as possible.
-
Regee Chacko
commented
We had setup the backup to storage account in same region (based on advice from MS engineer) and backups were successfully completed. Later the storage account firewall was setup to allow access from azure virtual networks only and we noticed the backups were failing. When customer support was contacted we were advised that this is not supported.
Due to this I have to allow storage account access from all networks.
This is a must have feature. -
VooDooMaN
commented
+ from Azure DevOps!!
so Azure DevOps not part of Microsoft software family :)
made by Aliens? :) -
Siju Mathew
commented
This is definitely not the intended behaviour based on Azure-(Function)-App documentation and the storage account firewall documentation. This behaviour works in CosmosDB and I have spent many hours trying to figure out why it will not work as intended.
Options to use ASE/Vnet or use it in two different regions are not workarounds but money making options. -
Cory
commented
Looking forward to this feature. I am currently backing up our web app manually.
-
VooDooMaN
commented
+1
-
André Sørhus
commented
I've found that we now can log application logs from non-ASE app services connected to VNet and with a storage account with a service endpoint. The logging is done using an IP address in the app service subnet's address space. (This can e.g. be monitored using "Diagnostics settings", currently in preview). However, "web server logging" is still not possible. In this case the logging is done using the non-subnet address space, in fact it's not even done using one of the listed IP addresses for the service plan, but some other shared address space IP. This forces us to have to either not use web server logging at all, log to the file system, or leave the storage account without firewall.
-
Anonymous
commented
Now, it still is not possible to just select "allow trusted Microsoft services".
But you can add the web app that is on a normal web plan to a regional subnet and set the storage to allow that subnet!
https://docs.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet
hope that helps anyone reading this.
-
Vansevenant, Stijn
commented
Impossible to follow Microsofts own Azure Security Center recommendations to configure firewall rules on the storage account and to configure backups on your app services using those storage accounts.
This is a must have feature. I'm forced now to either disable my firewall or disable my periodic backups.
-
Kozak, Daniel
commented
This feature is absolutely required. Any backup/core service that Microsoft offers should be included under the "Allow trusted Microsoft services to access this storage account"
-
Anonymous
commented
It's been more than 2 years, everyone has already exposed how important this feature is. Is there any news about it? At least a timeline please!
-
Anonymous
commented
Please add this feature - we followed security centre recommendations to lock down our firewall rules and broke SQL vulnerability scanning and web app backups. As far as I can tell there is no warning in security centre or in the Storage firewall. Please fix as things like this create waste for customers and Microsoft. This is technical debt and should be resolved.
-
[Deleted User]
commented
Please add this feature - we followed security centre recommendations to lock down our firewall rules and broke SQL vulnerability scanning and web app backups. As far as I can tell there is no warning in security centre or in the Storage firewall. Please fix as things like this create waste for customers and Microsoft. This is technical debt and should be resolved.
-
Dian, Steven
commented
If you read the documentation on "Trusted Microsoft Services" - Azure App Services or Azure webapps IS NOT one of the supported "Trusted Services" today. This is ridiculous. I should NOT have to setup an Internal ASE just to be able to effectively firewall off storage to an app service.
Forcing me to create storage in one region and the app service in another is NOT reasonable.Turning off firewall rules to support access to a storage account from an App Service / Azure Webapp is NOT a reasonable solution for production use. Microsoft, please for the love of all that is holy - add App Services / Azure webapps to the list of "trusted microsoft services" so that your customers can effectively isolate access to storage accounts from GENERAL OPEN to internet when using App services. THANK YOU.
-
Ty Hill
commented
This works if the App Service is in a different region than the Storage Account.
-
Anonymous
commented
This is actually a deal breaker. Just using storage key rotation is not a real option. And vnet integration / private endpoint is for my not feasable.
-
Tuhin Mukherjee
commented
Its a basic security feature which should be enabled for storage accounts.
-
Mick
commented
The checkbox that reads .... "Allow trusted Microsoft services to access this storage account" should be all that's required to give an app service in the same Azure Subscription access...
-
Raghid
commented
Securing connections between different azure services is a bit confusing. Private Endpoint connection or whitelisting appservices should be a high priority item to build.