Currently deploying some complex ARM templates from powershell on my computer can take up to 30 minutes - Powershell is running inside New-AzureRmResourceGroupDeployment commandlet and then returns success/failure. 10 minutes inactivity timeout is too low for such scenarios.
BTW, Google Cloud shell has 1 hour limit https://cloud.google.com/shell/docs/features - The instance persists while your Cloud Shell session is active and terminates after an hour of inactivity.1 vote
Curent portal integration is fine but please allow access to cloudshell also as a separate component without portal integration e.g. https://cloudshell.azure.com or portal.azure.com/cloudshell
Typically I don't need portal at all when I have command line or I can open portal in different tab/window if needed. Also it would speed up page loading on slow/mobile devices.2 votes
we can make the Cloud shell usable from the ARM template so that we can deploy the resources on a single click which are currently not possible using the ARM template or additional configuration of the services once those are installed using ARM templates.1 vote
After initial configuration of Cloud Shell, make the Storage Account the user is using:
* Visable what Storage Account is configured for him
* Changeable what Storage Account is used
* ARM Policy enforcing in which Subscription/ResourceGroup the Storage Account can or cannot reside
* Ultimate end goal: Have the option to deploy without Storage Account, or let this be a seperate resource via a separate resource provider (like the current Managed Disks for VMs). So deploy Cloud Shell with "Cloud Shell Managed Storage".2 votes
Instead of requiring zoom feature of the browser, which makes the portal UI elements also big, allow a setting to change just the console fonts2 votes
- Don't see your idea?