Skip to content

Commit 8656a7a

Browse files
Merge pull request #231750 from pruphil/pphillips-maintenance-config-changes
added information for shutdown machines
2 parents b3589e5 + b15aa8e commit 8656a7a

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/virtual-machines/maintenance-configurations.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,14 +50,18 @@ Using this scope with maintenance configurations lets you decide when to apply u
5050

5151
### Guest
5252

53-
This scope is integrated with [update management center](../update-center/overview.md) which allows you to save recurring deployment schedules to install updates for your Windows Server and Linux machines in Azure, in on-premises environments, and in other cloud environments connected using Azure Arc-enabled servers. Some features and limitations unique to this scope include:
53+
This scope is integrated with [update management center](../update-center/overview.md), which allows you to save recurring deployment schedules to install updates for your Windows Server and Linux machines in Azure, in on-premises environments, and in other cloud environments connected using Azure Arc-enabled servers. Some features and limitations unique to this scope include:
5454

5555
- [Patch orchestration](automatic-vm-guest-patching.md#patch-orchestration-modes) for virtual machines need to be set to AutomaticByPlatform
5656
- A minimum of 1 hour and 10 minutes is required for the maintenance window.
5757
- There is no limit to the recurrence of your schedule.
5858

5959
To learn more about this topic, checkout [update management center and scheduled patching](../update-center/scheduled-patching.md)
6060

61+
## Shut Down Machines
62+
63+
We are unable to apply maintenance updates to any shut down machines. You need to ensure that your machine is turned on at least 15 minutes before a scheduled update or your update may not be applied. If your machine is in a shutdown state at the time of your scheduled update, it may appear that the maintenance configuration has been disassociated on the Azure portal, and this is only a display issue that the team is currently working to fix it. The maintenance configuration has not been completely disassociated and you can check it via CLI using [check configuration](maintenance-configurations-cli.md#check-configuration).
64+
6165
## Management options
6266

6367
You can create and manage maintenance configurations using any of the following options:

0 commit comments

Comments
 (0)