Increase 10 minute inactive timeout
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.
We have doubled the timeout length from 10 minutes to 20 minutes. We hope this improves your experience, if this is still too short for you please open a new item and provide feedback on why that is. Thanks for your feedback and contribution to Cloud Shell and our community!
Cliff Davis commented
Please just make this a user defined setting!
Russell deGrove commented
I'm getting logged out every 20 minutes even though I'm doing things in the shell during that time. Doing exercises and have to set up vars over and over again. Would hesitate to use this in production.
20min timeout renders Azure CloudShell pretty much useless to me.
I'm losing all my variables every time
this is so sad
BTW: I'm using AWS Cloud9 all the time and it does not have this issue
Sorry Microsoft, I know you can do better
How does this work? mine still times out after like 2 minutes?
Martin van Boven commented
Problems with timeout for studying at MS Learn:
When busy with some exercise and taking some break, or investigating some peripheral aspects that come up resulting from the exercise, the shell will time out, losing the environment variables typically used in those exercises, necessitating going back to previious pages and redoing some stuff.
20 Minutes seems way too short. Having an option to have it configurable, perhaps if MS so wishes up to a certain maximum, seems a good solution.
Tab S commented
Adding a configurable timeout length would be great. But at least if it is possible for Microsoft to extend the timeout, please extend it to at least an hour. I have created scripts that automate deployment of a lot of resources that altogether takes up to that long to complete (it includes creating and setting up an API Management Service, which by itself takes more than 20 minutes). And we have a need to use the Cloud Shell for this for 2 reasons: multiple people would have access to the script files and the platform, and success of the deployment is not dependent on a particular user's system. We need this for the sake of regulation and compliance.
Why don't give an option to let the administrator determine how long the session should keep.
20 seconds is still too short to move VM instances. I really need around 30-40 minutes for this.
You guys should need to fix it, Microsoft!
This is still way too short, I'm developing and sign into the cloud shell every time I need it, it's intensely frustrating.
This is very irritating. If Microsoft wants us to use this they need to fix it!
I am still running into a lot of issues with Azure Cloud Shell and the 20 minute timeout. I feel like every time I look over it has disconnected without warning, and once disconnected I need to close the browser window to reconnect (in a way that allows for Connect-ExopsSession.
Christian Pearce commented
The shell might be active but the browser stops responding. I spent the better part of the day trying to use this. I have reloaded it 50 60 times in a couple hours. This needs to be fixed if it is going to be useful.
Whats the update on this, why cant we get access to this config and make it configurable as everyone has their own requirements. Security should be left to companies who are using rather than be forced upon I think everyone is responsible enough and there are cases like terraform etc will need this running longer than 2-3 minutes for sure
Javeed Khan commented
Can i get a resolution as my session is getting timed-out every 1 minute.. its really irritating when you are running a script.. how to increase the session atleast for 20 mins.. mine is loged out every 1 minute..
Robert Aspinall commented
Still too short. I'm trying to develop terraform scripts and the timeout keeps resetting my working directory. At least make it resume into the directory and environment you were in when it timed out.
Please make this a configurable setting.
Here is another user facing the same issue. I'm getting kicked out of every session after 2-3 minutes.
Same error .. the bash azure cli disconnects within 2-3 minutes ... very irritating
It does not work. Its time out in a min. Please check and update the time to 20 - 30 mins.
I could not complete a lab with long running copies due to the timeout. The sessions were actively copying session was technically "idle". This isn't good.
Anton Kalcik commented
Deployment of API Management still takes more than 20 minutes.