Check VM which is power status is "off" in studio ->    power on VDA VM in studio   ->   VDA VM start power "on"  but the power status  turn back to "off" soon. From Azure side the power state is still on. As the power state is off in studio, no avaiable VDA can be brokered for end user. 
 

DDC will send the resource graph query to get VDA's machine states. But we get an unexpected response from azure and trigger a exception. Then All of vda's state will be changed to off due to the exception.

The customer reported that the issue is fixed by MS Azure team. They found a new updated SDK on Azure which caused this issue. Now they roll it back and the MCS issue has been fixed.

All Azure VDAs' power state is off in DDC. But from Azure side the power state is on. All end users fail to launch the published desktop