Windows Server 2025 Hotpatch with Azure Arc: requirements and limits
Test bench: October 21, 2026.Microsoft has made Hotpatch available for Azure Arc-Connected Server 2025 Standard and Datacenter since May 19, 2026, with no additional Hotpatch fee. This makes the feature more interesting for existing hybrid environments, but does not mean “updates without maintenance planning”: baseline and unscheduled updates can still require restarts.
Short conclusion
Hotpatch is a supplemental update path for certain Windows security updates. Microsoft updates the base regularly as a cumulative baseline update; these baselines require a restart. Hotpatches in between can be imported without restarting. .NET, non-security, driver and firmware updates remain their own maintenance points. For Server 2025 Standard or on-site data center, Azure Arc is also required; Azure Edition has different deployment requirements.
Requirements at a glance
| Checkpoint | What Microsoft requires | Practice sequence |
|---|---|---|
| Operating system | Windows Server 2025, Build 26100.1742 or newer; Standard or data center | Determine build and edition first; Pre-release versions are excluded. |
| Security features | VBS/VSM must be running; at least UEFI and Secure Boot. Hyper-V VMs require Generation 2. | Validate firmware, VM and security configuration before Azure step. |
| Administration | Azure Subscription and Arc Connection; Azure Connected Machine Agent | Clarify network access, identity and responsibility for hybrid management. |
| Update cycle | Baselines approximately every three months; Hotpatches may appear in between | Restart windows remain required for baselines and special cases. |
| cover | Windows security updates; .NET, other Windows updates, drivers and firmware are excluded | Continue separate update rings and maintenance windows. |
How the cycle works
Before activation, Microsoft checks the supported edition, minimum build, VBS/VSM and Arc binding. For a Hyper-V VM, Generation 2 is one of the minimum requirements. If VSM is not running, powering on Hotpatch may fail; Subsequent activation of VSM may itself require a restart. Therefore, plan the platform requirements first, then the enrollment.
After the baseline update, Microsoft distributes Hotpatches in the designated interim months. A Hotpatch issue is not guaranteed every month. An important unplanned change can also trigger a new baseline. The team should therefore not only monitor the successful Hotpatch status, but also document update assessment, installation history and the next restart date. Azure Update Manager supports assessment and scheduling; Hotpatch does not replace monitoring or a complete recovery concept.
Advantages and limitations
- Advantage:The required restart between certain security updates can be omitted - helpful for systems with narrow availability windows.
- Advantage:Microsoft does not quote an additional Hotpatch fee for eligible Arc-connected Server 2025 systems; Arc and other Azure costs must be assessed separately.
- Border:Baseline updates, unscheduled baselines, and exempt update types still require maintenance planning.
- Border:Azure Arc brings an additional layer of management and connectivity. Check responsibilities, access and connection status before rollout.
Recommendation: first run a pilot server through the entire cycle
Start with a non-critical server of the same hardware and VM configuration. Capture edition and build, confirm VBS/VSM, UEFI/Secure Boot and Arc status, turn on Hotpatch, and check update rating and installation history in Azure Update Manager. Also test handling a baseline and an update that requires a restart. Only then should the function be transferred to other maintenance groups.
When you first select Windows Server 2025, check the edition, workload, virtualization, and desired management together. The active PE offer can be found atWindows Server 2025; theWindows Server Overviewlists the available versions.
Video: Hotpatch briefly explained
The official introduction of Microsoft Azure explains the basic principle. It is not a step-by-step guide for current Azure Arc management.
Source:Microsoft Azure, “Windows Server 2025 Hotpatching: Quick Introduction”· Channel:Microsoft Azure on YouTube. Embed checked on October 21, 2026.
Sources and test date
- Requirements to activate Hotpatch with Azure Arc— accessed October 21, 2026.
- Hotpatch cycle and covered updates— accessed October 21, 2026.
- Hotpatch management for Arc-connected servers— accessed October 21, 2026.
- Microsoft fee change announcement— accessed October 21, 2026.
Author: TechDesk PE Digital.Networks.