What Microsoft announced
The announcement appeared on Microsoft's Azure Arc blog. The new policy is named Configure Quick Machine Recovery (QMR) on Windows machines (preview). It enables WinRE and QMR for your 2025 Arc-enabled Windows servers. Because it is delivered through Azure Policy, Microsoft says you can turn on recovery protection across your entire fleet at once, without touching individual machines.
The portal side is just as important. The new Windows Recovery (preview) tab under Machine configuration in the Azure portal lets you enable WinRE and QMR on eligible machines, see which servers have it enabled, and spot machines currently recovering.
To get started, Microsoft's instruction is to deploy and assign the following Azure Policy to Azure Arc-enabled servers in your existing subscription: Configure Quick Machine Recovery (QMR) on Windows machines (preview). Microsoft points to a separate Arc enablement document for prerequisites and detailed steps. That document was not available for review here, so this piece does not guess at its assignment parameters.
Section summary: The release has two parts. One preview policy turns on WinRE and QMR for Windows Server 2025 machines managed through Arc, and a new portal tab shows their recovery status.
How this builds on last year's WinRE preview
This is the second step, not the first. Microsoft notes that previously, Azure Arc offered two separate Azure policies: one to audit whether WinRE is enabled and one to configure it. Those policies came out earlier as a public preview. In a walkthrough from roughly a year ago, Microsoft's Thomas Maurer described the ability to audit and enable WinRE across your Arc-connected Windows Server machines directly from Azure.
The new policy goes further. Earlier, Arc could make sure the recovery environment existed. Now it can also configure the cloud-connected repair process that runs inside that environment. Microsoft's Azure Policy reference lists the QMR definition as a DeployIfNotExists policy that creates a Guest Configuration assignment, at version 1.0.0-preview. The same reference shows it as disabled by default. Connecting a server to Arc does nothing on its own. You still have to assign the policy at the scope you want.
What Quick Machine Recovery does
According to Microsoft Learn, QMR builds on Startup Repair and adds network access. It uses a secure, connected WinRE to search Windows Update for a fix. Microsoft's QMR overview describes this sequence:
- Device crash: the machine fails to boot several times in a row, and recovery starts automatically.
- Boot to recovery: the machine boots into WinRE.
- Network connection: WinRE connects to the network and checks Windows Update for a remediation.
- Remediation: if Windows Update has a fix, QMR downloads and applies it. If it doesn't, the next step depends on configuration. With the default single scan, the machine falls back to other recovery options. If retry intervals are set, it keeps checking.
- Restart: if the fix works, Windows boots normally. If it fails, the machine goes back to WinRE and the cycle repeats.
Microsoft stresses one limit in the Arc announcement: QMR is a best-effort feature, and an automated fix might not exist for every failure. It is designed for widespread boot problems where Microsoft can publish one targeted fix through Windows Update. Think of a bad update or a faulty driver that knocks over thousands of machines at once. It will not fix your unique bootloader problem or a failed RAID controller.
Prerequisites and boundaries to check before rollout
Microsoft's Windows Server QMR documentation sets several requirements. Ignore them and your rollout may look finished without actually working.
- OS and update level: QMR requires a Windows Server 2025 edition with the October 2026 security update or later. Microsoft's Group Policy guidance says it does not apply to other Windows Server versions. Analysis from WindowsForum's Ignite coverage also notes that one Azure Policy enables Windows Recovery Environment and Quick Machine Recovery on eligible Windows Server 2025 Arc-enabled servers.
- Off by default on Server: Microsoft Learn says QMR is disabled by default on Windows Server 2025, as it is on other enterprise-managed systems. An administrator has to turn it on.
- Working WinRE: QMR runs inside WinRE. If the recovery environment is broken or missing, there is nothing to boot into.
- Supported networks: Microsoft says only wired networks and WPA/WPA2 password-based Wi-Fi are currently supported during recovery. Most racked servers use Ethernet anyway. If your environment needs 802.1X or proxies to reach Windows Update, test before you count on QMR.
- No WSUS shortcut: Microsoft's server troubleshooting guidance warns against assuming WSUS or offline update sources will supply QMR fixes. The design depends on Windows Update. Disconnected or WSUS-only sites will likely get little benefit.
Section summary: The policy only helps on fully patched Windows Server 2025 machines that have a working WinRE and a supported network path to Windows Update. If any of those is missing, the protection is mostly nominal.
Pricing: who pays for Machine Configuration
According to the Arc blog, the Azure Policy has no additional charge for servers covered by any of these:
| Coverage | Extra charge for the QMR policy |
|---|---|
| Windows Server 2016 Extended Security Updates | None |
| Microsoft Defender for Servers Plan 2 | None |
| Windows Server Software Assurance attestation | None |
| Windows Server pay-as-you-go licensing | None |
| Anything else | Machine Configuration charges apply |
The first row looks odd, since the policy itself targets Windows Server 2025. It reflects how Microsoft groups Arc coverage entitlements. It does not mean QMR runs on 2016. If you have uncovered servers, check Machine Configuration pricing before you assign the policy across your whole tenant.
A cautious rollout plan
The steps below are an editorial summary built from Microsoft's documented requirements. They are not an official Azure-specific procedure.
- Inventory first. Find Arc-enabled machines that run Windows Server 2025 and have the October 2026 security update or later.
- Check WinRE locally on a few machines. Microsoft's server guidance recommends running
reagentc /getrecoverysettingsfrom an elevated prompt to see the current QMR configuration. - Confirm network reachability from the recovery environment. Use wired or WPA/WPA2 connections, with access to Windows Update.
- Pilot the policy assignment on a small resource group or management group scope, then watch the Windows Recovery (preview) tab to confirm those machines show as enabled.
- Expand gradually. Microsoft's Group Policy guidance recommends this same pilot-first approach, and it applies equally to Azure Policy.
Using Group Policy instead
Some servers aren't Arc-enabled, and some shops prefer GPOs. Microsoft documents a Group Policy method for Windows Server 2025 under Computer Configuration > Administrative Templates > System > Quick Machine Recovery. Microsoft's tested configuration enables both Enable Cloud Remediation and Enable Auto Remediation.
The same folder also contains Set Recovery Retry Interval (0–4,320 minutes, where 0 means one attempt and no retries) and Set Total Recovery Wait Time (1–4,320 minutes, default 180). Microsoft specifically suggests a retry interval above zero for headless servers. Otherwise you get only one remediation attempt per wait period.
To verify, run gpresult /scope computer /r to confirm the GPO applied and reagentc /getrecoverysettings to see the effective settings. One warning from Microsoft's documentation: Not Configured is not an off switch. If you need QMR disabled, set both policies to Disabled.
These are Group Policy details. Don't assume the Arc policy exposes the same settings in the same form.
Analysis: worth trying, but don't retire your recovery plan
The value here is real. Servers in branch offices, retail locations and edge sites often have nobody on site with admin skills. Being able to see "these 40 machines are protected, and these 3 are recovering right now" from Azure saves hours of phone calls. And if a bad update causes a fleet-wide boot loop, servers that can pull Microsoft's fix on their own are worth a lot.
There are also reasons for caution. This is a preview, it only covers Windows Server 2025, and QMR is best-effort by design. It depends on Microsoft publishing a fix and on your network letting WinRE reach that fix. Microsoft is upfront about these limits, but the "back online faster" headline is the optimistic version. A realistic description is that some machines, in some failure scenarios, will recover without anyone touching them.
Keep your backups, out-of-band management, and documented bare-metal recovery steps. Treat QMR as an additional safety net that may catch some failures, not a replacement for those plans.
Bottom line: If you run Windows Server 2025 on Arc, assign the policy to a pilot group, confirm the portal shows what you expect, and check that your networks can reach Windows Update during recovery.
References
- Get your Arc-enabled Windows servers back online faster with Windows Recovery Environment (preview) Azure Arc Blog · 2026-11-17T18:52:31+00:00
- Get your Arc-enabled Windows servers back online faster with Windows Recovery Environment (preview) | Microsoft Community Hub techcommunity.microsoft.com
- Configure quick machine recovery by using Group Policy - Windows Server | Microsoft Learn learn.microsoft.com