BYO - Storage for Windows Web Apps
It seems to me a little strange that I can mount Azure Files in App Service on Linux and Web App for Containers but not in standard/regular Web App.
Our specific use case is a big web app spawned across more App Service Env under a Traffic Manager umbrella: for some kind of application logic a regular file system is better (more simple to use / less rework) than use the Storage API.
We are working on enabling bring your own storage to Windows based Web Apps
Any update on the release date? Will this be ready in next 3 months?
When will this be announced/released?
Peter Wallenius commented
We need this feature urgently! Any estimated release date?
Cenzato, Marco commented
Any update? Will this feature released in next months?
We'd be interested in this capability. Do you have an estimated release date?
Yeetender Gupta commented
Currently, there is no support for "bring your own storage" feature for Web apps on Windows. I'd like to mount azure file storage to my windows Web app. I understand currently app on Linux support this feature but not quite clear why it's not available on Windows.
Kevin Candlert commented
I've got an app that is divided by multiple tenants (one for each country) that share data today through a network drive. I'm currently experimenting with moving from multiple VPS's to multiple Azure Web Services.
However, the only blocking problem I've encountered is the possibility to share a folder between apps. I cannot rebuild the CMS I'm using and it's plugins that write to App_Data.
For the other paths that are not App_Data I can simply write a VirtualPathProvider - but attaching a network storage lets me kill two birds with one stone. :)
Ryan E. commented
We all miss the old and simple method in ASP.NET to store file by using Server.MapPath and File.Save to store user-uploaded file into the server.
I think if a developer can browse to App Service instance settings in the dashboard and attach a File Storage mapped as a separate drive in the web application, it will be revolutionary.
For example, if I have an Azure File storage, I should be able to map it to Z: drive in my App Service instance. Then when I develop the application, I can use file.Save(@"Z:\images\myfile.jpg") for example.
That file will be easily accessible from http://samples.file.core.windows.net/images/myfile.jpg when developing the application.
Later on, developer can just download the file from the File Storage using Windows File Explorer via the SMB protocol. (Or better idea, please implement FTP to the file storage). Simple, effective, and developer-friendly.
This way, we can harness the full power of Azure App and Storage without compromising on developer's experience.
Thanks for reading!