BYOS means bring your own Azure Storage File share or Blob container into Azure Container Web App as network file share.
It supports Azure Linux Web App and Windows Container Web App, but does not support Azure Function Apps as of now. (Linux Function App cannot be configured from portal but can be configured via Azure CLI)
When using AzureFiles, it mounted as CIFS with read/write permission, when using AzureBlob, it mounted as blobfuse with readonly permission.
Azure Storage in App Service 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.
Storage mounts are not backed up when you back up your app
It is not recommended to put the Storage Account in a different region from the Web App because this adds latency. Latency between App Service and Storage can cause crashes due to not being able to mount the Storage share.
The share name for AzureFiles should come from Files shares in Storage Account
The share name for AzureBlob should come from Containers in Storage Account
If we mount the blob container as AzureFile in Advanced mode, the web app will crash.
After mounting, the web app will restart automatically, then we can check the mount info via ‘cat /etc/mtab’.
For AzureFiles, it will be shown as cifs rw, which means read/write. For AzureBlob, it will be shown as fuse ro, which means readonly.
4. What is CIFS? And related issue.
Common Internet File System (CIFS) is a network filesystem protocol used for providing shared access to files and printers between machines on the network. A CIFS client application can read, write, edit and even remove files on the remote server. CIFS client can communicate with any server that is set up to receive a CIFS client request.