When you just want to execute some scripts on an environment, you perhaps do not need persistent storage.

On some environments you don't have the permissions to create a storage account dedicated for this, and have to fallback on your own powershell/bash commandline.

Make it an (advanced) option to not use storage when launching the shell, lowering the barrier even more to run a one-off command.

I have been trying to generate a listing of all of the blob sizes in a container, and it takes longer than the timeout settings and will not complete. If I run against a small container it works properly. Also, while it states I have been idle for 20 minutes I don't believe it was actually that long.

We whitelist IP's that are allowed to access privileged services. We'd like to be able to whitelist cloudshells for our staff members.

Add powershell modules.cmdlets to manage MFA Server (on-premises) management

Both, Linux and Windows, Cloud Shell(s) are frequently updated with new preinstalled tools. To get a list of those tools and their versions we need to consult the docs. If would be much easier and efficient to get that info directly in the Cloud Shell session. For example, in PowerShell Cloud Shell, one could run Get-CloudShellTool and get tools' info. Similar command could be added to Linux as well.

Seems like there is no way to currently break command execution.

For example instead of Get, I accidentally performed:
New-AzureRmADServicePrincipal

The above causes PowerShell to prompt for ApplicationId. At this point I realized the mistake, but there is no way to abort the command.

Pressing enter, asks for the ApplicationId again, and Ctrl+c is currently not handled. (Tested not to work under both Chrome and Edge). The only current solution is to restart the shell.

Please add support for Ctrl-c to interrupt the current command.

As authentication is already a pre-requisite, it would be useful to be able to pass a command when launching the shell programmatically

Deploying complex ARM templates, or jobs that encounter error conditions after timeout can take longer than 20 minutes. Please extend the shell timeout and provide a warning message prior to termination that will allow you to keep the session active. It's incredibly frustrating to be running a job that prevents interaction with the shell, then part way through the job, the session terminates without any warning. All history of the job is lost and there is no log stored anywhere, so you can't track down the error.

When attempting to use PowerShell in Cloud Shell with my CSP account, which has delegated Owner rights within Azure for the customer tenant, I get the error below. It works if I switch to a Global Admin account.

Add-AzureRmAccount : Cannot validate argument on parameter 'AccountId'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
At C:\Users\ContainerAdministrator\PSCloudShellStartup.ps1:73 char:71
+ ... ProfileModule\Add-AzureRMAccount @addAzureRMAccountParameters -ErrorA ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Add-AzureRmAccount], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Azure.Commands.Profile.AddAzureRMAccountCommand

Please add support for Ctrl+Backspace(or other browser safe alternative) to delete whole words and another command to clear the whole line.
(Linux clear line and clear word commands Ctrl+w and Ctrl+u are a no-go in a browser.)

When we run Update-Help the downloaded help files are not persistent across PowerShell sessions because they are written in $pshome's subfolder.

Could you preconfigure the Cloud Shell with the current PowerShell help files?

It would be quite helpful to be able to SSH or PowerShell into systems that are only accessible from inside of the VNET. This would reduce the need for me to fire up my laptop if I just need to check on something quickly on a VM (I could just use the Azure app on my phone at that point).

Bash already has Terraform from HashiCorp included. It would be nice to also have Packer (https://www.packer.io/) to build custom images from marketplace images.

Everytime a different user wants to use Azure Cloud Shell in the same Azure subscription, the prompt suggests to create a new Storage Account.

For a subscription that follows a strict naming convention, this is very unfortunate. Ideally, an administrator should be able to preconfigure Azure Cloud Shell to use the same Storage Account everytime anyone with access to that subscription wants to use Azure Cloud Shell.

Just like in the Monaco based app editor there is no support for the cursor keys on the console window when working with an external keyboard and the ipad. Should be possible to solve because the site http://codeanywhere.com works with cursor keys in the editor.

Today, if you want to start Cloud Shell or max/min a terminal in the Portal, you need to click on icons. It would be nice to do those tasks from the keyboard.

Using tab completion feels very slow sometimes and may lock the shell for a few seconds (3-10). Tab completion is an essential tool for me to work with speed and not having to remember every command (discovering new functionality too).
Due to its varying reliability i find myself going back to my local install a lot.