Study guide
6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping
Key Takeaways Explain This Topic AI
Azure Update Manager is built directly on Azure Resource Manager and requires no Log Analytics workspace, no Automation account and no Microsoft Monitoring Agent.
Arc-enabled servers are patched through the same control plane as Azure virtual machines, which is what makes on-premises and multicloud patching a single workflow.
A maintenance configuration defines the schedule window, the update classifications, the inclusion and exclusion KB lists and the reboot setting.
Dynamic scoping resolves machines at run time from subscription, resource group, location, OS and tag criteria, so newly onboarded servers join the schedule with no edit; the portal maximum maintenance window is 3 hours 55 minutes.
Azure Update Manager does not abort in-progress updates at the end of a maintenance window; instead an item is skipped unless at least 15 minutes remain (20 for a service pack, 10 for a reboot) on Windows.
Last updated: August 2026
Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping
Maintaining operating system patch compliance and automating routine operational tasks across distributed hybrid environments are fundamental responsibilities of enterprise Windows Server administrators. Historically, managing updates for multi-cloud and on-premises servers required complex on-premises System Center infrastructure, standalone Windows Server Update Services (WSUS) servers, or legacy Azure Automation Update Management linked to Log Analytics workspaces.
Azure Update Manager (AUM) modernizes this operational paradigm by delivering a cloud-native, software-as-a-service (SaaS) update management solution built directly into the Azure Resource Manager control plane. This section covers AUM itself — its architecture, assessment and patch deployment mechanics, maintenance configuration parameters and reboot policies, and dynamic scoping. Azure Automation , runbook authoring, and Hybrid Runbook Workers (HRW) are covered in section 6.4.
1. Azure Update Manager (AUM) Architecture
Azure Update Manager provides a single pane of glass for assessing, scheduling, and deploying operating system updates across Windows Server and Linux machines running in Azure, on-premises datacenters, and other cloud platforms. +-----------------------------------------------------------------------------------------+
- | AZURE UPDATE MANAGER ARCHITECTURE |
- | |
- | [AZURE RESOURCE MANAGER CONTROL PLANE] |
- | +---------------------------------------------------------------------------------+ |
- | | Azure Update Manager (AUM SaaS Engine) | |
- | | - Periodic Assessment (24-Hour Automated Scans) | |
- | | - Scheduled Maintenance Configurations (Patch Tuesday / Recurrence Schedules) | |
- | | - Dynamic Scoping (Azure Resource Graph Queries & Tag Selectors) | |
- | +---------------------------------------------------------------------------------+ |
- | | | |
- | | (Native Fabric APIs) | (Arc Agent 443) |
- | v v |
- | [AZURE IAAS VIRTUAL MACHINES] [AZURE ARC-ENABLED SERVERS] |
- | +---------------------------+ +---------------------------+ |
- | | Zero Additional Agents | | Connected Machine Agent | |
- | | Native VM API Integration | | - Communicates with WUA | |
- | | - Calls Windows Update | | - Reports to AUM via ARM | |
- | | Agent (WUA) / WSUS | | - ZERO Log Analytics/MMA | |
- | +---------------------------+ +---------------------------+ |
- +-----------------------------------------------------------------------------------------+
- Modern AUM vs Legacy Automation Update Management
Understanding the architectural evolution is critical for enterprise deployment planning and the AZ-800 exam:
Architectural Dimension Modern Azure Update Manager (AUM) Legacy Automation Update Management (MMA)
Backend Infrastructure Native Azure Resource Manager (ARM) SaaS service Requires Azure Automation Account & Log Analytics Workspace
Agent Requirements Zero additional agents (Uses native Azure VM fabric or Arc Connected Machine Agent) Requires legacy Microsoft Monitoring Agent (MMA / OMS agent)
Data Ingestion Cost Zero workspace ingestion fees for core update assessment and patch telemetry Billed for Log Analytics data ingestion and retention
Assessment Frequency Automated background periodic assessment every 24 hours Periodic polling every 12 hours via Log Analytics search query
Scoping Model Dynamic Scoping via Azure Resource Graph queries and Tags Static computer groups or Log Analytics saved searches
2. Assessment & Patch Deployment Mechanics
Azure Update Manager separates update management into distinct assessment and deployment workflows: +-----------------------------------------------------------------------------------------+
- | AUM WORKFLOW & PATCHING LIFECYCLE |
- | |
- | [1. PERIODIC ASSESSMENT] |
- | - Background scan runs every 24 hours via Windows Update Agent (WUA) |
- | - Queries local WSUS server or Windows Update catalog |
- | - Uploads pending patch compliance status to Azure (Installs ZERO updates) |
- | | |
- | v |
- | [2. DEPLOYMENT TRIGGER MODES] |
- | +------------------------------------+--------------------------------------------+ |
- | | Mode A: One-Time Updates (Ad-Hoc) | Mode B: Scheduled Maintenance Configuration| |
- | | - Immediate patch installation | - Automated recurring patch windows | |
- | | - Interactive troubleshooting | - Patch Tuesday offsets & dynamic tags | |
- | +------------------------------------+--------------------------------------------+ |
- | | |
- | v |
- | [3. MAINTENANCE WINDOW EXECUTION] |
- | - Evaluates Classification filters (Critical, Security, Rollups) |
- | - Evaluates KB Inclusions and Exclusions |
- | - Applies per-item minimums; window is not a kill switch |
- | - Applies Reboot Policy (RebootIfRequired, NeverReboot, AlwaysReboot) |
- +-----------------------------------------------------------------------------------------+
Core Capabilities:
Periodic Assessment: An automated background scan running every 24 hours. The local Windows Update Agent (WUA) assesses available patches against the server's configured update source (internal WSUS or public Microsoft Update) and posts the summary to Azure. It does not download or install updates.
Check for Updates (On-Demand): An interactive scan initiated via the Azure Portal, CLI, or REST API to retrieve real-time patch status immediately.
One-Time Updates: Immediate, ad-hoc installation of selected updates or classifications with custom reboot parameters, ideal for zero-day vulnerability remediation.
Scheduled Maintenance Configurations: Centralized, declarative schedules that execute unattended patching runs during defined maintenance windows.
3. Maintenance Configuration Parameters & Reboot Policies
When authoring a Maintenance Configuration in Azure Update Manager, administrators define the boundaries and rules of the patching window. +-----------------------------------------------------------------------------------------+
- | MAINTENANCE CONFIGURATION PARAMETER TAXONOMY |
- | |
- | PARAMETER SUPPORTED OPTIONS & EXAM CONSTRAINTS |
- | --------------------+-----------------------------------------------------------------|
- | Recurrence Schedule | - Daily, Weekly, or Monthly |
- | | - Relative Monthly: e.g., 'Second Tuesday of Month' + X days |
- | Maintenance Window | - Duration: 1 hour 30 min to 3 hours 55 min (portal maximum) |
- | | - Updates already in progress are NOT terminated at the limit |
- | Reboot Settings | - RebootIfRequired (Reboots ONLY if patch flags pending reboot) |
- | | - NeverReboot (Suppresses all reboots; leaves pending state) |
- | | - AlwaysReboot (Forces server restart at end of window) |
- | Classifications | - Critical Updates, Security Updates, Update Rollups, |
- | (Windows Server) | Feature Packs, Service Packs, Definition Updates, Updates |
- | Explicit KB Filter | - Include specific KB IDs (e.g., KB5034441) |
- | | - Exclude problematic KB IDs (e.g., KB5034123) |
- | Pre/Post Events | - Azure Event Grid integration (Trigger Functions/Webhooks) |
- +-----------------------------------------------------------------------------------------+
- The Maintenance Window Timeline (Windows)
The maintenance window is a starting boundary, not a kill switch, and Microsoft's documented behaviour is the opposite of what most administrators assume:
Azure Update Manager does not stop starting new updates merely because the window is nearly over, and it does not terminate an in-progress update when the window is exceeded. Only updates it has not yet begun are abandoned.
Instead, each update type has a minimum remaining time requirement, evaluated before that item starts. For a window running 15:00–18:00:
- Item Minimum time that must remain Latest start in this example
- Service pack 20 minutes 17:40
- Any other update 15 minutes 17:45
- Reboot 10 minutes 17:50
After issuing a reboot, Update Manager waits up to 15 minutes for an Azure VM and 25 minutes for an Arc-enabled server before marking the reboot failed.
On Linux , a reboot requires 15 minutes remaining, and that rule applies to Azure VMs only — not to Arc-enabled servers.
Warning
A window that is regularly exceeded is almost always a service pack that installs slowly. The remedy is a longer window or a split schedule, not a shorter update list — and machines in the same availability set are patched within update domain boundaries, so overlapping schedules across one availability set can leave machines unpatched.
Configuring Reboot Policies
Selecting the correct reboot policy prevents unintended service interruptions:
RebootIfRequired (Default): The maintenance engine queries the Windows reboot pending flag (e.g., HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending ). If any installed update demands a restart, the server is rebooted before the maintenance window closes. If no updates require a reboot, the server remains online.
NeverReboot : The maintenance engine completely suppresses the reboot command. Installed updates requiring a reboot remain in a pending state until an administrator manually restarts the host during a separate outage window.
AlwaysReboot : Forces an operating system reboot at the conclusion of the maintenance window regardless of whether the installed patches required one, ensuring a clean memory state.
4. Dynamic Scoping with Azure Resource Graph & Tags
In large enterprises, statically assigning individual servers to maintenance configurations creates severe administrative overhead and risk of unpatched machines. Azure Update Manager resolves this through Dynamic Scoping . +-----------------------------------------------------------------------------------------+
- | DYNAMIC SCOPING ARCHITECTURE IN UPDATE MANAGER |
- | |
- | [MAINTENANCE CONFIGURATION: 'Prod-Wave-1-PatchTuesday'] |
- | - Recurrence: 2nd Tuesday of Month + 2 Days, 02:00 UTC |
- | - Duration: 2 Hours | Reboot: RebootIfRequired |
- | - Dynamic Scope Filter: |
- | * Subscriptions: 'sub-enterprise-prod' |
- | * Resource Types: 'Microsoft.HybridCompute/machines' |
- | * Tag Query: 'Environment == Production' AND 'PatchGroup == Wave1' |
- | | |
- | v (Azure Resource Graph Evaluation) |
- | +---------------------------------------------------------------------------------+ |
- | | MATCHED TARGET MACHINES: | |
- | | - Arc-Server-01 (Tags: Environment=Production, PatchGroup=Wave1) --> ENROLLED | |
- | | - Arc-Server-02 (Tags: Environment=Production, PatchGroup=Wave1) --> ENROLLED | |
- | | | |
- | | UNMATCHED MACHINES: | |
- | | - Arc-Server-03 (Tags: Environment=Production, PatchGroup=Wave2) --> IGNORED | |
- | | - Arc-Server-04 (Tags: Environment=Dev, PatchGroup=Wave1) --> IGNORED | |
- | +---------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
How Dynamic Scoping Operates:
When authoring a dynamic scope, administrators construct criteria based on Subscriptions, Resource Groups, Locations, Resource Types ( Microsoft.HybridCompute/machines or Microsoft.Compute/virtualMachines ), and Resource Tags .
During every scheduled execution run, Azure Update Manager queries Azure Resource Graph in real time to resolve the current list of matching machines.
Zero-Touch Onboarding: When a new on-premises Windows Server is onboarded via Azure Arc and tagged with PatchGroup = Wave1 , it is automatically targeted during the next maintenance run without modifying the Maintenance Configuration.