665
Hi everyone,
I don't know why, but each morning I must to go in LCS to stop and restart my test environment.
Thoericaly, LCS shoots down the environment each night then restarts it each morning. But in practice I need to make these tasks. Someone know here is the problem ?
King regard,
Giorgio
Because Azure admin setup auto shut down this environment and LCS doesn't shows actual status. As you may don't have access to Azure, you need to click on stop and start on LCS to get environment up and running.
The simplest fix could be (as suggest by other experts) get your access on specific VM and use Azure mobile app, additionally ask Azure admin to add your email as shut down notification of VM so you will get get a email notification an hour before and you postpone/skip this auto shut down.
Hi Komi,
Yes. You can link multiple accounts in this app. I'm switching between my work and a private tenant.
Hi André,
Does the app allow multiple accounts. A situation where, as a partner we are in charge of several VM on different acconts.
Hi Hugo,
Thanks for sharing the blog. I have installed the Azure (portal) app on my phone and set some environments as favorite. It is then really easy to start an environment on demand.
Old thread and old problem. After 3 years the issue remains unsolved.
High cost for cloud-hosted env?! What if you shut it down everyday!
Besides Azure and LCS are not talking very well, we have the Stop button, but not the Restart. Great!
If we build any app this way, community would stone us, but since Microsoft did, it is pretty fine.
Depending on how long more you will keep clicking Stop (wait/refresh) Start, you might like to check this API idea...
https://www.sikich.com/insight/how-to-start-a-cloud-hosted-environment-via-email/
LCS doesn't do any shutdown / startup automatically.
You can set up such automation in Azure portal. But please be aware, that the environment status in LCS is not updated if the system is shut down / started from Azure (manually or by automation). The LCS status only knows what operation was the last one to be executed in LCS.
So, if you Start the environment from LCS, the status stays Deployed, even if the system is later shut down from Azure.
And, if you Stop the environment from LCS, the status stays Stopped, even if the system is later started from Azure.
It seems that in your situation someone has configured automatic shutdown for the machine in Azure. So every morning it's actually swithced off, but the status in LCS shows still Deployed. To start it, you must click Stop, then Start.
Hi Girogio,
You can also define those automatic shut downs at azure.
Have you checked that nothing is setup there that might cause this issue?
Best regards,
Ludwig
#1
André Arnaud de Cal...
292,933
Super User 2025 Season 1
#2
Martin Dráb
231,801
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
