If you try to start PowerShell Core 6.0.0-beta.9 in the current image for PowerShell in Cloud Shell it fails with the error: "The term 'pwsh' is not recognized as the name of a cmdlet, function, script file, or operable program."

Path environmental variable is not updated with a path to PowerShell Core 6.0.0-beta.9.

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.

Upload files and folder using drag and drop. Kudu has this one. it's very useful.

https://github.com/projectkudu/kudu/wiki/Kudu-console#upload-files-and-folder-using-drag-and-drop

SF PowerShell module or sfctl (or both)

Its nice, But it should show all the directories, I'm managing 6 Directories its showing only 3 Directories.

Steps
- Start cloud shell in powershell mode
- enter an invalid command, eg 'invalid'

Expected result:
- The error message is displayed in red text on black background (same as Windows 10 behavior)

Actual result:
- The error message is displayed in red text on blue background.

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.)

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.

Noticed that by default the AzureAD Powershell Module is not installed for Cloud Shell. I verified I could install it with Install-Module AzureAD, however once installed you still need to login with Connect-AzureAD if you hard code your creds with $creds you can then login with Connect-AzureAD -credentials $creds but it would also be nice if it inherited your logged in shell credentials like the AzureRM module does. See attached

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 would like to be able to create a new session within the same browser tab.

I would love to be able to copy and paste. In macOS, Cmd+C/Cmd+V work as intended in the shell. However, Ctrl+c/Ctrl+V do not work in Windows to copy and paste text.

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

It would be great to have the option to invoke commands and enter an interactive session into a VM using PowerShell remoting from the cloud shell.

Shift+TAB to reverse tab completition in Poweshell (Cloud Shell) just like we have in classic Powershell console.

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?

AZ CLI in BASH is powerful, easy to use and has commands such as file copy batch that are superior to PowerShell. It would be great to add CLI support for Automation / Run Books to keep efforts consistent.

I am using a lot the Azure Cloud Shell, and because company policy I have to login using a Service Principal.
Since today I discovered I cannot use "az login" anymore from the shell, I'm getting the following error:

Azure Cloud Shell relies on the user account it was initially launched under, as a result 'az login' is disabled.