...
Dear Azure customer, One or more Azure Virtual Machines (VMs) associated with your subscription require a maintenance update to migrate these VMs to newer hardware. While the vast majority of platform maintenance causes no interruption to your services, this update will require a reboot . This maintenance has two phases: the self-service phase and a scheduled maintenance phase. Azure Service Health provides you with the current status of each VM that requires maintenance and allows you to initiate the self-service maintenance proactively – any time between now and March 13, 2024 (23:59 UTC). If self-service maintenance has not been completed by then, Azure will automatically initiate maintenance on any VM that still requires it, sometime between March 14, 2024 (00:00 UTC) to March 20, 2024 (23:59 UTC). This scheduled maintenance will be performed one update domain at a time, to limit impact to environments configured for high availability. You can view a list of Affected Resources for this event under the ServiceHealth/PlannedMaintenance tab in the Azure portal You should expect each VM to be unavailable for up to 15 minutes after initiating the maintenance and note that operating system and data disks will be retained, but temporary storage will be lost during this maintenance. If you are using Dv1 or DSv1 VM sizes, please refer to the documentation here to understand performance changes if any. If you are using Proximity Placement Groups, please refer to the documentation here to understand how to verify the alignment of your resources and to take appropriate action if some resources are not aligned. We apologize for any impact that this maintenance may have. We strive to minimize the impact of platform maintenance, and to provide you with as much visibility and control as possible. | |
IMPACTED SERVICE(S) AND REGION(S) Service Name Region Virtual Machines Region South India Service Name Virtual Machine Scale Sets Region South India |
...