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!
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.
John Dawson commented
I have an ARM deployment that takes 28 minutes and I want screenshots afterwards. Twice now I've lost the screen and had to do over. I'd really appreciate a 1 hour timeout or even better (as I assume it consumes resources) make it configurable similar to font size as something like 10 mins, 30 mins, 60 mins.
Washim Nawaz commented
Cloud shell does not work well, timeout occurs every two 3 mins while you are typing.
Is there any solution to this annoying interruption ?
I believe the timeout is much shorter than 20 minutes. I think it's closer to 2-3 minutes. It will even quit in the middle of a command. This is ridiculous for a development tool. I understand not wanting it to be misused for lengthy processes, but it's a rather short timeout (shorter than 20 minutes).
philip gahan commented
also happening for me , even if I use a separate tab of shell.azure.com within the browser , 5 mins max and it times out
Fryderyk Supinski commented
Why not make this a session idle timeout? Only increment the session timeout counter while waiting for user input, and don't increment the session time-out counter while waiting for an operation to complete.
Vidar Hagen commented
I'm using Cloud shell for training session and would like it to be extended to 1 hour. Alternative there could be a setting with default 20min and max 1hour
Richard Cove commented
The cloud shell is almost unusable due to the time out issues
I get time outs even when I am typing or editing a file, I am pretty sure that the 20 minutes is not related to activity but the time since login, so a session has to be less than 20 minutes
If i use shell.azure.com, i have to go through the ms login process each time i timeout
Tom Ptacek commented
I agree with the others, 20 minute timeout is too short. Should be a settable parameter. It would be different if you could pop open an Azure PowerShell like a cmd window - and it came up quickly. The pain comes because it's a minute wait to start one up. I could see an hour being the max, people could live with that.
Falco Alexander commented
why not add a setting for timeout?
Peter Neil commented
my timeout i s 2 for 4 minutes
Dimi Goranov commented
The timeout is 2-4 min on my end as well. If I switch to another browser tab for more than 3-4min I have to restart the shell. This is very annoying and makes the developers live difficult.
Joshua Niland commented
I agree with others. The timeout is 2-4 mins at best!
This unfortunately makes the use of the Azure Cloud Shell useless for lengthy tasks such as deployments or AZCopy etc.
I'd doubt it is 20 minutes before a timeout - normally around 3 or 4 minutes of inactivity (while looking up technet articles, etc), then I come back to the shell and it's timed out already. If it was actually 20 minutes, then it's probably something I can live with, but the 3-4 minute timeout definitely needs to be increased.
Even 20 minutes is not really long enough. I am trying to deploy application gateways which are notoriously slow.
The same here. 2-4 minutes and you are out. Annoying,