This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 70%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Due to a number of limitations in my current environment I have been using cloudshell on a regular basis. Recently I keep getting this message (bash):
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.
Or this one (powershell):
Your Cloud Shell session will be ephemeral so no files or system changes will persist beyond your current session.
The thing is, the clouddrive shows as mounted, I can write to it and the changes are persisted. I'm just worried that sometimes they won't be and I will lose data. I have tried running clouddrive unmount then remounting both my existing file share and a new file share but still get this message. I also tried the "Reset User Settings" option but it does the same.
It is also inconsistent, it seems to appear for a long period then disappear for a long period.
Anyone else seeing this? Any suggestions for a root cause or what can be done to ensure the drive is definitely not ephemeral?
Michael Cameron: Hope you have verified the following, if not can you perform the basic checks as below and let me know?
clouddrive unmount.Dismount-CloudDrive command instead of clouddrive unmount.![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 98%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
@Michael Cameron The first time you start Cloud Shell, you're prompted to select your storage options. If you want to store files that can be used every time you use Cloud Shell, you must create new or choose existing storage resources. Cloud Shell uses a Microsoft Azure Files share to persist files across sessions.
How long have you been seeing this issue? How often do you use Cloud shell? This could be a temporary issue, but I would like to check with the internal teams on this. Let me know.
What are you MSFT guys not getting? The OP clearly states the drive is mounted, they can write to it, and the writes persist. Why would you remotely suggest the storage may no longer exist???
At any rate, I'm having the same issue now with same symptoms. I've gone as far as deleting my actual file share and let it recreate during the new cloudshell session, which gets recreated successfully, but cloudshell continues to warn it was unable to connect to storage. Yet I can upload files fine, unmount the storage, start up a new session, reconnect to the existing storage/share, and the file(s) I uploaded are still there.
There is clearly a bug with the shell.
I have to say Matthew has nailed it - the suggested answers so far largely seem to be cut and paste from docs which I have (clearly) already read or irrelevant as I have explained in my question.
I'm afraid this points to a flaw in the MS Q&A forums more than anything else. There is incentivisation to post answer and have them accepted and I am getting more and more convinced that some answers are just AI generated meaningless mince.
To reiterate:
My clouddrive appears to be working as it should BUT I am getting this warning. I would hate to lose the data that is allegedly ephemeral (but appears persistent) so I would like to get to the bottom of why the message is appearing and whether I need to take any action.
Given that Matthew is also experiencing the same issues (and now that I have asked around, other members of my extended team are too) I believe this is not isolated to my account or even my tenant.
The forums are for helping each other, not scoring points and winning gift cards with a splatter gun approach to answers hoping that something sticks. Please think about your answers before posting them.
Thanks for all the responses, I do appreciate that people believe they are being helpful but a little more thought wouldn't go amiss.
How long has this been happening? Maybe a few weeks, not entirely certain but it was intermittent but seems consistent over the last few days.
It will likely be more productive to just reach out to Azure support. Clearly these answer forums are not the place to receive actual assistance.
Currently that means going through a CSP, it's not as simple as a request via the portal
@Michael Cameron Thanks for sharing the details.
As I shared earlier, I have now reached out to the internal teams to confirm this issue and the potential cause for it. Thanks for your patience.
@Michael Cameron I got the confirmation from the internal team - "The error was due to a bug where one step in the mounting process is failing but the rest of the mounting operation completed successfully. We have a fix for it that will be included in the next Cloud Shell image update."
The image release with the fix completed on July 23rd.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 89%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMW%3C/text%3E%3C/svg%3E)
SMB channel encryption was my issue.
AES-128-GCM had to be enabled
having just AES-256-GCM enabled to setting to maximum security caused the clouddrive to not mount.