Azure Cloud Shell
Have feedback for Azure Cloud Shell? Submit your idea or vote up an idea submitted by another Cloud Shell user. All of the feedback you share here will be monitored and reviewed by the Azure Cloud Shell engineering team. By suggesting or voting for ideas here, you will help us shape the future of Cloud Shell. Remember that this site is only for feature suggestions and ideas, if you have technical questions please try our documentation or StackOverflow.
-
Canadia Region support for storage account
It would be nice to support the canadian region(s) for the storage account that stores the cloud drive. Customers are requesting this more and more.
64 votes -
Timeout is to short, or needs to be configured to monitor for running processes.
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.
53 votes -
Do not require a storage account
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.
36 votesThanks for this suggestion – we currently plan to continue requiring storage so users can get the best experience possible with persisted state across all the interfaces Cloud Shell is available. Please upvote this if you agree though as we’re always listening to the community!
-
Allow cloudshells to be whitelisted in network security groups
We whitelist IP's that are allowed to access privileged services. We'd like to be able to whitelist cloudshells for our staff members.
32 votes -
Make the Azure Cloud Shell container available for public download
The Azure Cloud Shell uses containers on the back end. It would be great if the container images used for Cloud Shell were publicly available and open source. The existing images are a great start for those who want to start using Azure and the extended tooling that is included. For those who want to avoid the dreaded timeout or would like to customize the container, it would be great to be able to grab the images and launch them in ACI or locally.
24 votes -
User-friendly way to get a list of preinstalled tools
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.
23 votesThis is a great suggestion, we’ll look into it – in the meantime please upvote to help us prioritize appropriately!
-
Add MFA Server (on-premises) management via Powershell
Add powershell modules.cmdlets to manage MFA Server (on-premises) management
21 votes -
Don't automatically terminate the shell without warning
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.
17 votes -
Allow cloudshell to be created inside a VNET
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).
16 votes -
Preconfigure Storage Account used by Azure Cloud Shell for all users
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.
15 votes -
Pass a command tp shell
As authentication is already a pre-requisite, it would be useful to be able to pass a command when launching the shell programmatically
13 votes -
12 votes
-
Make the cloud shell timeout configurable (with policy support)
Please make the timeout of cloud shell configurable - possibly even set to '0' for no timeout. Include policy control so that a company that wants to impose a max can do so (some will want/need this).
11 votes -
Allow access to PowerShell from CSP account
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.AddAzureRMAccountCommand10 votes -
Since you don't provide full support for docker at least prove full support for docker-machine
Currently docker-machine is the only way to run docker inside the Azure Cloud shell. Docker works to build images and run images, once you set up and eval a docker-machine. But if you want to push the image you created in the docker-machine to an ACR, you get the following message when you run the command: "az acr login..."
This command requires running the docker daemon, which is not supported in Azure Cloud Shell.
For other docker commands, you get the error "daemon not found" if the docker-machine isn't set up, For ACR, for some reason, you totally block use…
9 votes -
Add HashiCorp Packer to Bash
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.
8 votes -
Increase Tab-Completion performance
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.8 votesThanks for the feedback, at this moment we need more input to look into this! We’re regularly sync with the AZ CLI team to make sure performance is great on all fronts, but providing votes helps us prioritize our resources appropriately so please cast votes across ideas you feel are important to you!
-
Add support for running Azure Cloud Shell in secure Azure subscription
I'm working in a subscription where I only give users the minimum permissions that are necessary. I would like these users to have access to Azure Cloud Shell, but I want to have it pre-configured for them before they even try. For this, I need the following:
1. An API (and ideally one or more PowerShell cmdlets) that allows for the initial configuration of Cloud Shell to be done automatically for a user before they even try to access Cloud Shell. This would create the resource group if it did not already exist in the subscription, create the storage account,…
8 votes -
Preconfigure PowerShell in Cloud Shell with PowerShell help files
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?7 votes -
Allow connection to cloud shell from putty or other clients over ssh
It would be awesome if there was an option to connect via putty or other ssh client to a cloud shell instance. I’m thinking the prompt app on an iPad for ssh to cloudshell to remove any overhead connecting I. A browser
6 votes
- Don't see your idea?