Configure Azure Files in a Windows Container on App Service


This article applies to custom Windows containers. To deploy to App Service on Linux, see Serve Content from Azure Storage.

This guide shows how to access Azure Storage in Windows Containers. Only Azure Files Shares and Premium Files Shares are supported. You use Azure Files Shares in this how-to. Benefits include secured content, content portability, access to multiple apps, and multiple transferring methods.



Azure Files is non-default storage and billed separately, not included with the web app. It doesn't support using Firewall configuration due to infrastructure limitations.


  • Azure Storage in Windows containers is in preview and not supported for production scenarios.
  • Azure Storage in Windows containers supports mounting Azure Files containers (Read / Write) only.
  • Azure Storage in Windows containers is currently not supported for bring your own code scenarios on Windows App Service plans.
  • Azure Storage in Windows containers doesn't support using the Storage Firewall configuration because of infrastructure limitations.
  • Azure Storage in Windows containers lets you specify up to five mount points per app.
  • Azure Storage mounted to an app is not accessible through App Service FTP/FTPs endpoints. Use Azure Storage explorer.
  • Azure Storage is billed independently and not included with your web app. Learn more about Azure Storage pricing.

To mount an Azure Files Share to a directory in your App Service app, you use the az webapp config storage-account add command. Storage Type must be AzureFiles.

az webapp config storage-account add --resource-group <group_name> --name <app_name> --custom-id <custom_id> --storage-type AzureFiles --share-name <share_name> --account-name <storage_account_name> --access-key "<access_key>" --mount-path <mount_path_directory of form c:<directory name> >

You should do this for any other directories you want to be linked to an Azure Files share.


Once an Azure Files share is linked to a web app, you can verify this by running the following command:

az webapp config storage-account list --resource-group <resource_group> --name <app_name>

Next steps