@Nandha Kumar RP Please note that Docker Compose is not supported for Bring Your Own Storage with Azure App Service.
Limitations
The limitations of custom-mounted storage include:
- Storage firewall is supported only through service endpoints and private endpoints (when VNET integration is used).
- FTP/FTPS access to custom-mounted storage isn't supported (use Azure Storage Explorer).
- Storage account shared access keys are the only means of authentication that are supported; Entra ID and RBAC Roles are not supported.
- Azure CLI, Azure PowerShell, and Azure SDK support is in preview.
- Mapping
/
or/home
to custom-mounted storage isn't supported. - Don't map the storage mount to
/tmp
or its subdirectories as this action may cause a timeout during app startup. - Azure Storage isn't supported with Docker Compose scenarios.
- Storage mounts aren't included in backups. Be sure to follow best practices to back up the Azure Storage accounts.
- NFS support is only available for App Service on Linux. NFS isn't supported for Windows code and Windows containers. The web app and storage account need to be configured on the same VNET for NFS. The storage account used for file share should have "Premium" performance tier and "Filestorage" as the Account Kind. Azure Key Vault is not applicable when using the NFS protocol.
- With VNET integration on your app, the mounted drive uses an RFC1918 IP address and not an IP address from your VNET.
Let us know if you have any further questions or concerns by replying to this message.