We are testing Azure Update Manager with Customer Managed Schedules for VM patching and would like to validate the following understanding:

Aggarwal, Vivek 0 Reputation points
2026-11-16T16:48:36.27+00:00

We are testing Azure Update Manager with Customer Managed Schedules for VM patching and would like to validate the following understanding:

  1. If a VM is configured with a Customer Managed Schedule, patch deployment will occur only according to the configured schedule and will not be automatically overridden by Microsoft's monthly patch release cycle (Patch Tuesday).
  2. Using a Customer Managed Schedule, patch installation can be deferred for any desired duration by scheduling the deployment at a future date, effectively allowing customers to postpone patching as long as required.

Could Microsoft confirm whether the above understanding is correct?

Azure Update Manager
Azure Update Manager

An Azure service to centrally manages updates and compliance at scale.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Jose Benjamin Solis Nolasco 13,376 Reputation points Volunteer Moderator
    2026-11-16T17:44:04.54+00:00

    Welcome to Microsoft Q&A

    Hello @Aggarwal, Vivek I hope you are doing well,

    Your understanding is generally correct, with a few important considerations.

    1. Will Microsoft automatically patch the VM on Patch Tuesday if it is configured for Customer Managed Schedules?

    Yes, your understanding is correct.

    When a VM's patch orchestration is configured as Customer Managed Schedules, Azure Update Manager uses the maintenance configuration schedule that you define. Microsoft does not automatically install updates according to the monthly Patch Tuesday release cycle simply because updates become available.

    In contrast, Azure Managed / Automatic VM Guest Patching handles patch timing automatically, including the deployment of security and critical updates during Azure-managed maintenance windows.

    2. Can patching be deferred indefinitely by scheduling it at a future date?

    Generally yes, but with operational and security considerations.

    With Customer Managed Schedules, you control when updates are deployed by defining maintenance configurations and recurring schedules. Azure Update Manager doesn't automatically force installation when new updates are released.

    However:

    • Updates remain available until you schedule and install them.
    • Deferring patching for extended periods may leave the VM exposed to unpatched vulnerabilities.
    • Organizational policies, compliance requirements, Azure Policy assignments, or other management tooling could impose additional requirements outside of Azure Update Manager itself.

    Summary

    Scenario Customer Managed Schedules
    Automatic patching on Patch Tuesday No
    -------- --------
    Automatic patching on Patch Tuesday No
    Customer controls deployment timing Yes
    Ability to defer installation using future schedules Yes
    Azure Update Manager forces patch installation outside the defined schedule No (based on documented Customer Managed Schedule behavior)

    Reference

    If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find similar solutions.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-16T16:49:25.08+00:00

    Customer Managed Schedules control when Azure Update Manager installs guest updates, so Patch Tuesday makes updates available but does not itself override the configured maintenance schedule; however, postponement is not an unconditional guarantee if another patching mechanism remains enabled or an update is later superseded.

    1. Patch Tuesday versus the configured schedule

    Your first statement is correct with a configuration caveat:

    • Azure Update Manager installs scheduled updates when the associated Maintenance Configuration runs, within its defined maintenance window.
    • For Azure VMs, Patch orchestration must be set to Customer Managed Schedules for scheduled patching. This mode configures Patch mode = AutomaticByPlatform and BypassPlatformSafetyChecksOnUserSchedule = TRUE.^1^
    • Microsoft's monthly release cycle determines when new updates become available; it does not create an additional Customer Managed Schedule run. Scheduled patching installs updates according to the schedule and update-selection criteria saved in the Maintenance Configuration.^2^

    Validate each Azure VM under:

    Azure portal → Azure Update Manager → Machines → Patch orchestration

    The value should be Customer Managed Schedules, not:

    • Azure Managed – Safe Deployment, which enables automatic VM guest patching.
    • Automatic by OS, which allows the operating system to install updates automatically.
    • An independently configured Windows Update, WSUS, Configuration Manager, Intune, or third-party patching policy.

    In particular, Windows automatic updates are an operating-system setting rather than an Azure Update Manager setting and can install updates outside the Maintenance Configuration.^2^

    For Azure Arc-enabled servers, setting Customer Managed Schedules as the patch-orchestration property is not a prerequisite, but any OS-side or external patching configuration must still be considered.^3^

    2. How long installation can be deferred

    Your second statement is generally correct for installation timing, but “for any desired duration” needs qualification.

    A Maintenance Configuration can specify:

    • A future Start on date and time.
    • A daily, weekly, or monthly recurrence in the portal.
    • An optional end date.
    • The update classifications, KB IDs, or packages to install.^3^

    The guest-scope documentation does not state a maximum number of days for which guest patch installation may be deferred. Its scheduling constraints include:

    • Recurrence of at least six hours.
    • A maintenance window from 1 hour 30 minutes through 3 hours 55 minutes.
    • A start time at least 15 minutes after schedule creation.
    • A recommended 15-minute buffer for schedule or scope changes.^4^

    Nevertheless, delaying a deployment does not guarantee that the exact patches available today will remain installable later. Monthly cumulative updates can supersede previous updates, and applicability can change. At the eventual run, Update Manager evaluates and installs updates that are selected, applicable, and available from the configured update source. If an older KB must be targeted, it can be added under the Maintenance Configuration's Updates settings, but it still needs to remain applicable and available from Windows Update or WSUS.^5^

    Practical conclusion

    • Yes: Patch Tuesday does not independently override a correctly configured Customer Managed Schedule.
    • Yes, with limits: Installation can be scheduled for a later date, and no maximum guest-patching deferral period is documented.
    • No absolute guarantee: Other enabled patch mechanisms may install updates earlier, and delaying may result in older updates being superseded rather than installed as originally released.
    • Update assessment and compliance reporting can continue to identify missing updates without installing them; installation occurs through a scheduled or one-time deployment.^6^

    References

    1. Manage multiple machines with Azure Update Manager
    2. Update options and orchestration in Azure Update Manager
    3. Schedule recurring updates for machines by using the Azure portal and Azure Policy
    4. Managing VM updates with Maintenance Configurations
    5. Azure Update Manager KBIDs inclusions in a maintenance configurations for a VM Patching - Microsoft Q&A
    6. Guidance on migrating virtual machines from Microsoft Configuration Manager to Azure Update Manager
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.