Skip to content

Commit 2acfe4d

Browse files
Merge pull request #269705 from nehashrowti/patch-1
Minor changes to update and maintenance overview
2 parents 1c19e45 + 02167c4 commit 2acfe4d

File tree

1 file changed

+17
-10
lines changed

1 file changed

+17
-10
lines changed

articles/virtual-machines/updates-maintenance-overview.md

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: Updates and maintenance overview
2+
title: Guest updates and host maintenance overview
33
description: Learn about the updates and maintenance options available with virtual machines in Azure
44
author: mimckitt
55
ms.author: mimckitt
66
ms.service: virtual-machines
77
ms.topic: overview
8-
ms.date: 02/28/2023
8+
ms.date: 03/20/2024
99
ms.reviewer: cynthn
1010
---
1111

@@ -20,31 +20,38 @@ Azure periodically updates its infrastructure to improve reliability, performanc
2020
Azure infrastructure updates can range from upgrading network components, decommissioning hardware on network, patching software components in hosting environment or updating guest OS/ software’s on VMs. Each of these updates are performed using different tools available in Azure.
2121

2222
## Platform maintenance
23-
Platform maintenance comprises of updates applied for networking components like Top of the Rack (TOR) Switch or host environments like Dedicated hosts/Isolated VMs/Shared hosts. Host updates are done on the physical host environment where VMs reside and are transparent to the customers most of the time. However, some updates can require the residing VMs to freeze (non-rebootful updates) or reboot (rebootful updates). When these no-impact updates are performed, Azure chooses the update mechanism that's least impactful to customer VMs.
23+
Platform maintenance comprises of updates applied for networking components like Top of the Rack (TOR) Switch or host environments like Dedicated hosts/Isolated VMs/Shared hosts. Host updates are performed on the physical hosts where VMs are hosted and are usually not noticeable to the customers. But some updates can require the VMs that are allocated on the hosts to freeze (non-rebootful updates) or reboot (rebootful updates). When these no-impact updates are performed, Azure chooses the update mechanism that's least impactful to customer VMs.
2424

2525
### Host maintenance that requires a reboot and that doesn't require a reboot
2626

27-
During Azure host maintenance updates, VMs either freeze, reboot or live migrate to another host. Host maintenance updates that require reboot are called *rebootful updates* while the updates that cause VMs to pause/freeze for >=1 second are called *non-rebootful updates*.
27+
During host maintenance, VMs either freeze, reboot or live migrate to another updated host. Host maintenance updates that require reboot are called *rebootful updates* while the updates that cause VMs to pause/freeze for >=1 second are called *non-rebootful updates*.
2828

2929
### Dedicated hosts/Isolated VMs vs Shared Hosts
3030

31-
Host maintenance and experience are available for Dedicated host, Isolated VMs, and Shared hosts. Dedicated hosts are hosts in which all VMs are owned by one customer. Shared hosts are hosts in which VMs from multiple customers might reside together in one host. Isolated VMs are large machines that are isolated to a specific hardware type and dedicated to a single customer.
31+
Host maintenance experience is available for [Dedicated](dedicated-hosts.md) hosts, [Isolated](isolation.md) VMs, and Shared hosts. Dedicated hosts are hosts in which all VMs are owned by one customer. Shared hosts are hosts in which VMs from multiple end-customers reside together. Isolated VMs are large machines that are isolated to a specific hardware type and dedicated to a single customer.
3232

33-
On Dedicated hosts, customers have host maintenance experience available for impact <1sec or >=1sec. Customers can opt into a maintenance control and schedule maintenance window based on their needs within 35days from last maintenance date. Isolated VMs have maintenance control experience available like Dedicated hosts.
33+
On [Dedicated](dedicated-hosts.md) hosts, customers have host maintenance experience available for impact <1sec or >=1sec. Customers can opt into a maintenance control and schedule maintenance window based on their needs within 35days from last maintenance date. [Isolated](isolation.md) VMs have maintenance control experience available like Dedicated hosts.
3434

35-
On Shared hosts, customers have host maintenance experience available for updates that require reboot updates. For updates that are <30sec maintenance control experience isn't available today. High Risk program is available to get maintenance experience for >30s freeze.
35+
Customer can use [maintenance control](maintenance-configurations.md) to:
3636

37-
### Notification mechanisms
37+
- Apply all (<1 sec or >=1 sec) updates together.
38+
- Wait up to 35 days to apply updates for Host machines.
39+
- Set up a maintenance schedule or use Azure Functions to automate platform updates.
40+
- Maintenance configurations are effective across subscriptions and resource groups.
41+
42+
On Shared hosts, customers have maintenance experience available for rebootful updates or for high impact update. For updates that are <30sec maintenance control experience isn't available today.
43+
44+
### Notifications
3845

3946
Azure provides notifications before, during, and after maintenance operations. Scheduled events provide notifications before an event starts and while it is in progress so your application can react automatically. Flash health events enable you to consume and analyze alerts and trends in VMs availability for reporting and root cause analysis.
4047

4148
#### Scheduled Events
4249
43-
Scheduled events provide advance notification of upcoming availability impacts so you can prepare your application for the impact ahead of time. They are optimized for automated resiliency by being delivered directly to the impacted VM and to all VMs in the same placement group. For information on Scheduled Events, see [Scheduled Events for Windows VMs](./windows/scheduled-events.md) and [Scheduled Events for Linux](./linux/scheduled-events.md).
50+
[Scheduled events](./windows/scheduled-events.md) provide advance notification of upcoming availability impacts so you can prepare your application for the impact ahead of time. They are optimized for automated resiliency by being delivered directly to the impacted VM and to all VMs in the same placement group. For information on Scheduled Events, see [Scheduled Events for Windows VMs](./windows/scheduled-events.md) and [Scheduled Events for Linux](./linux/scheduled-events.md).
4451

4552
#### Flash Health Events
4653
47-
Flash Health Events provide near real-time information about past availability impacts so customers can react to events and easily mitigate incidents. Flash information is available in Azure Monitor, AzureResource Graph, or Event Grid to integrate with your systems and processes.
54+
[Flash Health Events](flash-overview.md) provide near real-time information about past availability impacts so customers can react to events and easily mitigate incidents. Flash information is available in Azure Monitor, AzureResource Graph, or Event Grid to integrate with your systems and processes.
4855

4956
## Guest patches and update flows
5057

0 commit comments

Comments
 (0)