You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node maintenance may affect one or more of your virtual machines in West US
You're receiving this notice because you currently use Azure Virtual Machines.
You've been identified as a customer using virtual machines in West US who may experience connection failures and network latency when attempting to access some virtual machines hosted in the region.
Due to failing hardware, planned maintenance is being scheduled starting at 13 February 2025 23:10 UTC until 14 February 2025 23:10 UTC. To minimize risk to your service, and in case the hardware fails before the system-initiated migration occurs, we recommend that you redeploy your virtual machine(s) prior to 13 February 2025 23:10 UTC.
During this maintenance window, IaaS virtual machines will be migrated to newer network hardware. Please expect each virtual machine to be unavailable for up to 15 minutes after initiating the maintenance. Operating system and data disks will be retained, but temporary disks will be reset.
See a list of your affected virtual machines in the Account Information section of this message.
For more control over when your virtual machines will be affected, migrate your deployments using the Azure portal or PowerShell by following the steps below. You must complete the migration prior to 13 February 2025 23:10 UTC.
Migrate using the Azure portal
For both Classic and Azure Resource Manager Virtual Machines:
I doubt we have many VMs that won't be automatically migrated before this maintenance window. if there are a few known ones, we could be proactive about them
more likely this will have no impact at all. created the issue primarily to remind us in case problems emerge in the given timeframe. won't be great if the First Responders channel lights up but we'll know where to head to remedy the situation based on reports there (if any)
received an email w/ this title on 28 January
Details
Node maintenance may affect one or more of your virtual machines in West US
You're receiving this notice because you currently use Azure Virtual Machines.
You've been identified as a customer using virtual machines in West US who may experience connection failures and network latency when attempting to access some virtual machines hosted in the region.
Due to failing hardware, planned maintenance is being scheduled starting at 13 February 2025 23:10 UTC until 14 February 2025 23:10 UTC. To minimize risk to your service, and in case the hardware fails before the system-initiated migration occurs, we recommend that you redeploy your virtual machine(s) prior to 13 February 2025 23:10 UTC.
During this maintenance window, IaaS virtual machines will be migrated to newer network hardware. Please expect each virtual machine to be unavailable for up to 15 minutes after initiating the maintenance. Operating system and data disks will be retained, but temporary disks will be reset.
See a list of your affected virtual machines in the Account Information section of this message.
For more control over when your virtual machines will be affected, migrate your deployments using the Azure portal or PowerShell by following the steps below. You must complete the migration prior to 13 February 2025 23:10 UTC.
Migrate using the Azure portal
For both Classic and Azure Resource Manager Virtual Machines:
For virtual machine scale sets:
Migrate using PowerShell
In Azure PowerShell, invoke the command to stop an Azure Virtual Machine without a "StayProvisioned" flag.
Example: Stop-AzureVM -ServiceName $cloudServiceName -Name $vmName
Learn more about stopping an Azure Virtual Machine.
More information
• Types of maintenance performed on virtual machines
• Receive a notification in your virtual machine 15 minutes prior to reboot
Support options
• Ask questions in the Azure Virtual Machines forums.
• Request support via @AzureSupport or the Azure portal.
You can view this notification in the Azure portal under event ID: 8MD2-NR8.
Account Information
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_159829
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _windows.10.amd64.open.rt-a-scaleset_401199
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.android.34.open.rt-a-scaleset_219
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _windows.10.amd64.open.rt-a-scaleset_401058
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_159639
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.android.25.open.rt-a-scaleset_3580
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_158885
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_158935
Subscription ID: a6ad62fb-177e-40ef-af51-5c342911ebf5
Subscription name: DNCENGHELIX-02
Resource name: _windows.10.amd64.open.svc-a-scaleset_368796
Release Note Category
Release Note Description
The text was updated successfully, but these errors were encountered: