When the VM in a cloud-hosted environment is stopped or started in Azure (e.g. via Azure automation run books), the status of the environment is not reflected in LCS. This is causing confusion on the part of users who navigate to these environments via LCS.
Our customer is using the automation run books to manage their Azure VMs in order to optimize their Azure run costs. The Azure management portal shows the correct status of the VMs in these environments.
Comments
Scripting Logic Apps automation to use LCS API, as provided by above MS Reply, to shutdown VM's/ Stop Environment has been able to stop and start VMs with correct status on LCS.
Using default DevOps shutdown process will still cause LCS status to be out of sync.
Category: Lifecycle Services
Completely agree with Rich Hims below.
Even though the idea is shown as “Completed”, the original issue has never been resolved. This is 2023 by the way.
The LCS API provided is not doing its function as expected. That is LCS Environment VM Status is not sync properly to the actual environment.
Category: Lifecycle Services
Given the "Completed" comment regarding the LCS API, presumably that means that Azure stop/start doesn't use said API (understandable: as far as Azure is concerned, the cloud-hosted VMs are like any other Azure VM, right?), because scheduled shutdown within Azure still leaves the LCS environment page showing the status as "Deployed" when it's really "Stopped". Feels like the "Complete" status of this idea is only if users change how they're managing VM status, when everyone's request appears to be that the LCS Status & Azure status would be in line no matter how the VM is stopped/started.
Category: Lifecycle Services
Is there an update on this? We use the Azure Portal to auto shutoff the cloud boxes in the evenings. In LCS the status still says "Deployed" but if you look in Azure Portal you can see they are stopped. Now to turn them on we have to go to Azure Portal. LCS does have the ability to start/stop the boxes but not to schedule it. So going to Azure is still required. Are there plans to move this functionality to LCS?
Category: Lifecycle Services
Developers must be authorized to start/stop their security assigned Cloud Hosted machine as well. Currently they have to use the Azure portal (currently not synchronized).
Category: Lifecycle Services
Great Idea Khee. I would also like the ability to rejoin a VM to LCS. So for example if I had to restore a VM or I had to remove and re-add we need to be able to re-attach it to continue managing. Not sure If I should post this as a seperate thread.
Category: Lifecycle Services
Totally agree. This is critical in controlling cloud hosted environment (CHE) costs as our developers (and I'm sure others), much like my children, never remember to "turn the lights off" at the end of a day.
Microsoft--please simply update LCS to poll the status of CHE's using ARM and update the status accordingly in LCS.
Category: Lifecycle Services
Administrator on 1/26/2021 3:46:50 AM
We have released the LCS API to start and stop customer managed environments. Using these APIs will ensure the LCS environment status is synced with the actual environment.
Database movement API - Reference - v1 - Start and stop environments - Finance & Operations | Dynamics 365 | Microsoft Docs