Microsoft Will Turn On Windows Settings Backup by Default in Windows 11 26H2

Microsoft is changing how Windows settings backup works in Windows 11 version 26H2. Starting with the update, the backup policy for Windows settings backup and restore will be enabled by default on eligible Microsoft Entra joined and Microsoft Entra hybrid joined devices.

The change means IT admins will no longer need to configure backup first for supported devices where no policy has already been set. Microsoft says the goal is to make backup a standard resilience baseline, so users can recover settings and Microsoft Store app lists more easily after a reset, replacement, upgrade, or reimage.

The company confirmed the policy shift through the Windows message center, where it said explicit admin settings will still take priority. In other words, if an organization has already turned the policy on or off, Windows 11 26H2 will not override that decision.

What changes in Windows 11 26H2?

The main change affects the backup side of Windows settings backup and restore. Microsoft’s Windows IT Pro Blog describes the move as a new baseline for resilience, with backup enabled automatically when devices meet the requirements and no explicit policy exists.

Windows can preserve user settings, preferences, and the list of installed Microsoft Store apps. This helps users return to a familiar setup when they move to a new PC or recover from a device issue.

Microsoft’s Windows Backup for Organizations overview also notes that the feature is being renamed to Windows settings backup and restore, although older references to Windows Backup for Organizations may still appear during the transition.

Area	Current behavior	Windows 11 26H2 behavior
Backup policy	Disabled by default unless configured by admins	Enabled by default on eligible devices when no admin policy exists
Admin controls	Admins can enable or disable backup	Explicit admin settings still override the default
Restore policy	Disabled by default	Still disabled by default and admin-managed
Backed-up data	User settings and Microsoft Store app list when enabled	User settings and Microsoft Store app list on eligible devices

Restore does not turn on automatically

The most important enterprise detail is that backup and restore are not being treated the same way. Backup becomes default-on in supported situations, but restore remains opt-in.

Microsoft says restore still requires administrator configuration through management tools. That matters because restore can influence what users see during device setup or first sign-in, especially when a user restores a profile from a previous device.

In its Windows Backup for Organizations overview, Microsoft says restore can occur during the out-of-box experience or during first sign-in after enrollment, but only when the required restore policy has been enabled.

Which devices are eligible?

The policy change targets managed business and education environments, not every Windows 11 PC. Microsoft says the backup feature is available to users signed in with Microsoft Entra ID on supported Windows devices.

According to the Windows 11 Insider Experimental Preview Build 26300.8772 release notes, the 26H2 default applies to eligible Microsoft Entra joined or Microsoft Entra hybrid joined devices.

Microsoft also says the feature is not currently available for GCCH, sovereign clouds, or China. Organizations should review regional and cloud availability before assuming the default will apply across every tenant.

• Devices must meet Microsoft’s Windows version and build requirements.
• Users must sign in with a Microsoft Entra ID account.
• Devices must be Microsoft Entra joined or Microsoft Entra hybrid joined.
• Existing admin-configured backup policies still take priority.
• Restore still needs separate admin configuration.

How admins can manage the policy

Microsoft is not removing enterprise control. Admins can still manage backup through Microsoft Intune, Group Policy, or other mobile device management tools.

The Windows message center says default-on backup applies only when admins have not explicitly configured the policy. That gives organizations a clear way to keep backup disabled, enforce it, or control it based on their own compliance requirements.

Admins can also configure restore separately in Intune. Microsoft documents restore options through enrollment policy and device configuration policy, which lets organizations decide whether users should see restore options during setup.

1. Review existing backup and restore policy settings in Intune, Group Policy, or MDM.
2. Decide whether backup should remain enabled by default or be explicitly disabled.
3. Check whether restore should be enabled during OOBE or first sign-in.
4. Validate Conditional Access and authentication requirements for restore flows.
5. Test the experience before broad Windows 11 26H2 deployment.

Why Microsoft is making the change

Microsoft is using Windows 11 26H2 to make device recovery less dependent on manual setup. The change should help organizations refresh PCs, move users to new devices, and recover from resets with less friction.

The Windows IT Pro Blog says the default-on behavior is available for early validation in the Windows Insider Program Experimental channel starting in July 2026. It is expected to take broader effect for eligible devices when Windows 11 26H2 reaches general availability.

The Windows 11 Insider Experimental Preview Build 26300.8772 release notes also frame the change as a way to reduce setup friction and improve recovery consistency.

What organizations should do now

Organizations planning a Windows 11 26H2 rollout should audit their current backup and restore posture before deployment. The default change will matter most for tenants that have not explicitly configured backup policy.

For some organizations, Microsoft’s new default may reduce helpdesk work after device replacement or reset. For others, especially those with strict data handling rules, admins may want to explicitly define the backup policy instead of relying on the default.

The safest approach is to treat the 26H2 change as a deployment checklist item. Confirm eligibility, document policy intent, test backup behavior, and decide separately whether restore should appear for users during device setup.

FAQ