Azure Cloud Shell has the following known limitations:
System state and persistence
The machine that provides your Cloud Shell session is temporary, and it is recycled after your session is inactive for 20 minutes. Cloud Shell requires a file share to be mounted. As a result, your subscription must be able to set up storage resources to access Cloud Shell. Other considerations include:
- With mounted storage, only modifications within your
clouddrivedirectory are persisted.
- File shares can be mounted only from within your assigned region.
- Azure Files supports only locally redundant storage and geo-redundant storage accounts.
Permissions are set as regular users without sudo access. Any installation outside your
$Home directory will not persist.
Although certain commands within the
clouddrive directory, such as
git clone, do not have proper permissions, your
$Home directory does have permissions.
Cloud Shell supports the latest versions of Microsoft Edge, Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, and Apple Safari. Safari in private mode is not supported.
Copy and paste
Ctrl+C and Ctrl+V do not function as copy/paste shortcuts in Cloud Shell on Windows machines, use Ctrl+Insert and Shift+Insert to copy and paste respectively.
Right-click copy-and-paste options are also available, but right-click function is subject to browser-specific clipboard access.
Take caution when editing .bashrc, doing so can cause unexpected errors in Cloud Shell.
Your history of bash commands may be inconsistent because of Cloud Shell session disruption or concurrent sessions.
Cloud Shell is intended for interactive use cases. As a result, any long-running non-interactive sessions are ended without warning.
Any latency in Cloud Shell is subject to local internet connectivity, Cloud Shell continues to attempt to carry out any instructions sent.