Microsoft are performing reboots of Virtual Machine hosts in Azure. These may impact you if you run Azure IaaS VMs. This is due to the hardware-based security vulnerability disclosed yesterday.
You should have received an email notifying you, however, we thought it best to share an example of how to check the status of your VMs below, following the steps:
1. Your VMs will be rebooted. You can see whether they are due to be impacted by visiting Azure Service Health from the Azure Portal.
2. Click on affected resources to see those affected in the next round of reboots. The image below shows a sample of this, and the time-frame as to when it will reboot.
3. You will also see a notification when you view an impacted VM.
4. If you don’t have a notification your VM may already be rebooted, you can see this is in the resource health for the VM.
Any VMs in an availability set will be rebooted one at a time to ensure, at least one, is still available.
Please bear in mind any VMs not in an availability set and not on premium disks do not receive an SLA from Microsoft. It is always best practice to ensure your VMs are in an availability set to ensure maintenance such as this does not affect your workloads.