ANAVEM
Languagefr
How to Perform Windows Autopilot Reset in Microsoft Intune

How to Perform Windows Autopilot Reset in Microsoft Intune

Reset Windows devices to business-ready state using Autopilot Reset via Intune admin center or local device. Removes personal data while preserving management enrollment.

Evan MaelEvan Mael
March 27, 2026 12 min
mediumintune 6 steps 12 min

What is Windows Autopilot Reset and Why Use It?

Windows Autopilot Reset provides a streamlined method to return Windows devices to a business-ready state without the complexity of traditional imaging or manual reinstallation. This feature removes personal files, applications, and user settings while preserving critical enterprise configurations including Microsoft Entra ID join status, Intune management enrollment, and regional settings like language and keyboard preferences.

The reset process leverages the automaticRedeployment Configuration Service Provider (CSP) and Windows Recovery Environment (WinRE) to perform a controlled device refresh. Unlike a complete Windows reinstall, Autopilot Reset maintains the device's identity within your organization's Azure AD tenant and Intune management infrastructure, significantly reducing the time and effort required to redeploy devices.

When Should You Perform an Autopilot Reset?

Autopilot Reset is particularly valuable in several scenarios: preparing devices for new users when employees leave the organization, resolving persistent software issues that resist traditional troubleshooting, removing personal data from corporate devices, and standardizing device configurations across your fleet. The feature supports both remote execution through the Intune admin center and local execution directly from the device lock screen, providing flexibility for different operational requirements.

This tutorial will guide you through both reset methods, covering the prerequisites, step-by-step procedures, and troubleshooting techniques you need to successfully implement Autopilot Reset in your environment. You'll learn to configure the necessary policies, execute resets remotely and locally, and handle common issues that may arise during the process.

Implementation Guide

Full Procedure

01

Verify Device Prerequisites and WinRE Status

Before performing an Autopilot Reset, confirm your device meets the requirements and has Windows Recovery Environment enabled. This is crucial because the reset process relies on WinRE to function properly.

Open Command Prompt as administrator on the target device and run:

reagentc /info

Look for "Windows RE status: Enabled" in the output. If WinRE is disabled, enable it with:

reagentc /enable

Next, verify the device's Intune enrollment status by running:

dsregcmd /status

Confirm these values in the output:

  • AzureAdJoined : YES
  • DomainJoined : NO (for pure Azure AD joined devices)
  • MDMUrl : https://enrollment.manage.microsoft.com/
Warning: If WinRE is disabled, the Autopilot Reset will fail. Always verify and enable WinRE before proceeding with any reset operations.

Verification: The reagentc command should show "Windows RE status: Enabled" and dsregcmd should confirm Azure AD join and Intune enrollment.

02

Configure Autopilot Reset Policy in Intune

To enable local Autopilot Reset from the device lock screen, you need to create and deploy a device restrictions policy. This step is only required if you plan to use the local reset method.

Sign in to the Microsoft Intune admin center at endpoint.microsoft.com and navigate to:

DevicesConfiguration profilesCreate profile

Configure the profile with these settings:

  • Platform: Windows 10 and later
  • Profile type: Device restrictions
  • Name: "Allow Autopilot Reset"

In the configuration settings, navigate to:

GeneralAutopilot Reset: Allow

Assign the profile to your target device groups. If the UI option is unavailable, create a custom OMA-URI policy instead:

OMA-URI: ./Vendor/MSFT/Policy/Config/AutomaticRedeployment/AllowAutomaticRedeployment
Data type: Integer
Value: 1
Pro tip: Create a dedicated Azure AD group for devices that need local reset capability. This gives you granular control over which devices can perform local resets.

Verification: Check the policy deployment status in Intune and confirm it shows "Succeeded" for your target devices.

03

Perform Remote Autopilot Reset via Intune Admin Center

The remote reset method is the most common approach for IT administrators. This allows you to reset devices from the Intune console without physical access to the device.

In the Microsoft Intune admin center, navigate to:

DevicesAll devices

Locate your target device using the search function or by browsing the device list. Click on the device name to open its details page.

From the device overview page, click More in the top menu, then select Autopilot Reset from the dropdown menu.

A confirmation dialog will appear. Review the device information and click Yes to confirm the reset operation.

Monitor the reset progress by checking the device's status. You'll see:

  • Initial status: "Pending"
  • During reset: "In progress"
  • Completion: "Completed"

The reset process typically takes 30-60 minutes depending on the device specifications and network connectivity.

Warning: Remote Autopilot Reset will immediately begin removing user data and applications. Ensure users have backed up any important local files before initiating the reset.

Verification: The device status in Intune will show "Completed" and the device will automatically restart and begin the out-of-box experience (OOBE) process.

04

Execute Local Autopilot Reset from Device Lock Screen

Local reset is useful when you have physical access to the device and need to reset it immediately. This method requires the device restrictions policy configured in Step 2.

Ensure the device is at the Windows lock screen. If a user is currently signed in, sign them out first.

At the lock screen, press the key combination:

Ctrl + Windows + R

This opens the Autopilot Reset sign-in screen. You'll see a specialized login interface specifically for the reset process.

Sign in using local administrator credentials. These must be credentials for an account with local admin rights on the device, not regular user credentials.

After successful authentication, the reset process begins automatically. The device will display progress information and restart multiple times during the process.

If you have a provisioning package on a USB drive (created with Windows Configuration Designer), insert it before starting the reset. The system will automatically detect and apply the package during the reset process.

Pro tip: Create a provisioning package with Windows Configuration Designer to pre-configure Wi-Fi settings, certificates, and other configurations. This speeds up the post-reset setup process significantly.

Verification: The device will restart and show the Windows OOBE screen. Check that the device maintains its Azure AD join status by running dsregcmd /status after the reset completes.

05

Monitor Reset Progress and Handle Common Issues

During the Autopilot Reset process, several issues can occur. Understanding how to monitor progress and troubleshoot problems ensures successful completion.

Monitor the reset progress through multiple channels:

  • Intune admin center: Device status updates in real-time
  • Device screen: Progress indicators and restart notifications
  • Event logs: Windows Event Viewer for detailed troubleshooting

Common issues and their solutions:

Issue: Reset fails with "WinRE not available" error

reagentc /enable
reagentc /info

Issue: Device stuck at "Getting ready" screen

Wait 2-3 hours before considering the reset failed. Network connectivity issues can cause extended delays.

Issue: Primary user not updated after reset

Manually update the primary user in Intune:

DevicesAll devicesSelect devicePropertiesChange primary user

Issue: Local reset option not available

Verify the device restrictions policy is deployed and the automaticRedeployment CSP value is set to 1.

Warning: If a reset appears stuck for more than 4 hours, do not force restart the device. Contact Microsoft support as forced interruption can cause boot issues.

Verification: A successful reset results in a device at the OOBE screen with preserved Azure AD join, Intune enrollment, and regional settings, but with all user data and applications removed.

06

Verify Reset Completion and Re-provision Device

After the Autopilot Reset completes, verify that the device is properly reset and ready for re-provisioning. This final step ensures the device is in the expected business-ready state.

Check the device status in Intune admin center:

DevicesAll devicesSelect your device

Verify these key indicators:

  • Last check-in: Should be recent (within last hour)
  • Compliance status: May show "Not evaluated" initially
  • Enrollment status: Should remain "MDM"

On the device itself, confirm the reset was successful by checking:

Get-ComputerInfo | Select-Object WindowsProductName, TotalPhysicalMemory
dsregcmd /status | findstr "AzureAdJoined\|MDMUrl"

The device should show:

  • Clean OOBE experience with no previous user profiles
  • Preserved Azure AD join status
  • Active Intune enrollment
  • Original regional and language settings

Complete the device setup by:

  1. Proceeding through OOBE with the intended user account
  2. Allowing Intune policies to sync and apply
  3. Installing required applications through Intune app deployment
  4. Verifying compliance policy evaluation
Pro tip: Use Intune's Enrollment Status Page (ESP) to provide users with a guided setup experience that shows policy and application installation progress during the initial sign-in.

Verification: Run Get-AppxPackage -AllUsers to confirm only system apps remain, and check Intune compliance reports to ensure the device meets your organization's security requirements.

Frequently Asked Questions

What's the difference between Windows Autopilot Reset and a factory reset?+
Windows Autopilot Reset preserves the device's Azure AD join status, Intune enrollment, and regional settings while removing user data and applications. A factory reset completely wipes the device and requires full re-enrollment in Azure AD and Intune. Autopilot Reset is faster and maintains enterprise connectivity, while factory reset returns the device to its original out-of-box state requiring complete reconfiguration.
Can I perform Autopilot Reset on devices that are not connected to the internet?+
Local Autopilot Reset can be initiated on offline devices using the Ctrl+Win+R key combination, but the device must connect to the internet during the reset process to complete Azure AD authentication and Intune policy synchronization. Remote Autopilot Reset requires internet connectivity throughout the entire process since it's initiated from the cloud-based Intune admin center.
How long does a Windows Autopilot Reset typically take to complete?+
Autopilot Reset duration varies based on device specifications, network speed, and the number of policies to apply. Typically, the process takes 30-60 minutes for most devices. High-end devices with fast SSDs and good network connectivity may complete in 20-30 minutes, while older devices or those with slower internet connections may take up to 90 minutes. The reset includes multiple automatic restarts during the process.
What happens to BitLocker encryption during an Autopilot Reset?+
BitLocker encryption is temporarily suspended during the Autopilot Reset process to allow the system to access and modify the drive contents. After the reset completes and the device rejoins Azure AD, BitLocker encryption is automatically re-enabled based on your organization's Intune encryption policies. The BitLocker recovery key is regenerated and stored in Azure AD, ensuring continued data protection without manual intervention.
Why might the Autopilot Reset option be grayed out in Intune admin center?+
The Autopilot Reset option may be unavailable if the device doesn't meet prerequisites: the device must be Azure AD joined (not hybrid), enrolled in Intune MDM, running Windows 10 or later, and have WinRE enabled. Additionally, your account needs Intune Service Administrator permissions or equivalent roles. Devices that are only Azure AD registered or domain-joined without Intune enrollment won't show the reset option.
Evan Mael
Written by

Evan Mael

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

Sign in to join the discussion