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.
Any update on this?
James Burnham commented
This is a major pain point in our organization. This would be great to see introduced! We have a large number of subscriptions, and an even larger number of users on those subscriptions.
The necessity for each user to create a storage account or configure the advanced settings just right is the biggest pain point in cloud shell adoption.
Steven Judd commented
Another issue is the limit of storage accounts per subscription. For an organization that wants to setup and use CloudShell for their staff, there is a limit to how many users can be setup in a particular subscription. It would be better to be able to share a particular Storage Account, but secure the files in the storage account for the specific user.
Adoki, Charles commented
We have the same concerns here. We have to provide a lengthy tutorial to our teams to get them started with Cloud Shell. It would be great if they could just click on it and go.
Getting access to default modules/files/scripts in Cloud Shell would be great too (Items specified by us).
The tutorial doesn't show you how to add a storage account. I created one in azure portal but it is still asking me to create another storage account. I go into advanced settings but I don't know how to fill in the text boxes correctly. This is horrible for people who are using tutorials! We waste lots of time trying to figure out how to name and create a new storage account. Ridiculous!
John Neville commented
As an administrator I would also like to create this in advance because I don't want to grant full Contributor rights on a Resource Group to users.