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.
-
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.
169 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).
78 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.
77 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.
56 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.
54 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.
48 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.
44 votesThis is a great suggestion, we’ll look into it – in the meantime please upvote to help us prioritize appropriately!
-
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.
43 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
41 votes -
allow all 365 management shell access via cloudshell
Allow all 365 management shell access via cloudshell so one can administer their environment from the cloud. allow cmdlets and modules for Skype for Business, Exchange, SharePoint, OneDrive, etc all from within 1 cloud shell...
33 votes -
Requesting a Cloud Shell.Failed to provision a Cloud Shell: {"code":"TenantActiveUserQuotaReached","message":"Tenant '604c1504-c6a3-4080-81a
Requesting a Cloud Shell.Failed to provision a Cloud Shell: {"code":"TenantActiveUserQuotaReached","message":"Tenant '604c1504-c6a3-4080-81aa-b33091104187' has '306' active users in location 'westus', which exceeds the active user quota."}
28 votes -
Add MFA Server (on-premises) management via Powershell
Add powershell modules.cmdlets to manage MFA Server (on-premises) management
26 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).
24 votes -
Add rest API support for cloudshell
It will be great if azure exposes rest APIs to access the cloudshell, pass commands and get outputs.
There are too many azure ad features that are only accessible via powershell. Microsoft graph API does not support all the functionalities including basics like get password policy, update password policy, enable MFA etc.
Having cloudshell rest API, one can actually pass command to cloudshell from REST API interface and get the job done. No need to have powershell or azure CLI installed on myachine just to automate something.
19 votes -
We need Azure Cloud Shell available for both admin and tenant portals on Azure Stack.
Azure Cloud Shell should be in Azure Stack.
17 votes -
Include Exchange Online PowerShell Module
Want to be able to PowwerShell against Exchange Online, including when you have MFA enabled for your admin.
15 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.
14 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…
14 votes -
quota
Cannot connect to cloud shell for training due to quota:
Requesting a Cloud Shell.Failed to provision a Cloud Shell: {"code":"TenantActiveUserQuotaReached","message":"Tenant '604c1504-c6a3-4080-81aa-b33091104187' has '300' active users in location 'westus', which exceeds the active user quota."}
13 votes -
add support for Internet Authentication Proxy
Cannot leverage Azure Cloud Shell from on-premise. We use an Internet Authentication Proxy. We can implement a Proxy by-pass, but the application needs to be proxy aware.
Requesting a Cloud Shell.
PowerShell may take up to a minute.Succeeded.
Connecting terminal...Failed to connect terminal: websocket cannot be established. Press "Enter" to reconnect.
Requesting a Cloud Shell.
PowerShell may take up to a minute.Succeeded.
Connecting terminal...Failed to connect terminal: websocket cannot be established. Press "Enter" to reconnect.
13 votes
- Don't see your idea?