Hi,

I have been using Azure and the Azure shell (Bash) on the Azure portal for nearly half a year.

Yesterday when I started the Azure shell, I got this warning message:

Warning: Failed to mount the Azure file share. Your cloud drive won’t be available.
Your Cloud Shell session will be ephemeral so no files or system changes will persist beyond your current session.

As far as I know, I never unmounted or changed any permission of the storage account to the clouddrive folder.

However, I found that my cloud drive (mounted to the clouddrive/ folder) was still accessible, and the files I created there could still be found when I started another Cloud Shell session.

I tried to reset my user settings and remount the same storage account to the clouddrive/ folder, and restarted the Bash Cloud Shell again. The warning message still appeared while the clouddrive/ could still be accessible.

So I wonder if the warning message was a false alarm, or if it referred to something else. May I ask if there is any command I can run to display the mounting log that resulted in the warning message, so I can check if it is really a false alarm?

Best Regards,

Benny (@evergrn_tree).

​Hi, I have been using Azure and the Azure shell (Bash) on the Azure portal for nearly half a year. Yesterday when I started the Azure shell, I got this warning message: Warning: Failed to mount the Azure file share. Your cloud drive won’t be available.
Your Cloud Shell session will be ephemeral so no files or system changes will persist beyond your current session. As far as I know, I never unmounted or changed any permission of the storage account to the clouddrive folder. However, I found that my cloud drive (mounted to the clouddrive/ folder) was still accessible, and the files I created there could still be found when I started another Cloud Shell session. I tried to reset my user settings and remount the same storage account to the clouddrive/ folder, and restarted the Bash Cloud Shell again. The warning message still appeared while the clouddrive/ could still be accessible. So I wonder if the warning message was a false alarm, or if it referred to something else. May I ask if there is any command I can run to display the mounting log that resulted in the warning message, so I can check if it is really a false alarm? Best Regards,Benny (@evergrn_tree).    Read More

​