# Plan the Autopilot identity handoff before motherboard repair

> Who will restore the repaired device’s Autopilot identity before it returns to its user?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-002-plan-the-autopilot-identity-handoff-before-motherboard-repair/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:31:54+00:00
- Modified: 2026-09-10T00:31:59+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Who will restore the repaired device’s Autopilot identity before it returns to its user?

## Potentially affected

Use this review for a motherboard repair on an Autopilot-registered device. Match the specific hardware scenario to the source’s supported repair guidance; do not assume that every combination of reused components behaves alike.

## DSE recommendation

Agree on the handoff between the original registration owner, repair facility, and receiving administrator before shipment.

## Article

## Source facts

Microsoft recommends deregistering an Autopilot device before motherboard replacement, then capturing a new hardware hash, registering the repaired device again, and returning it to its out-of-box state. A repaired device registered through Partner Center needs its new 4K hardware hash; a product key identifier or serial/manufacturer/model tuple is insufficient. Microsoft also warns that motherboard-repair scenarios often lose data. [Microsoft Learn](https://learn.microsoft.com/en-us/autopilot/autopilot-motherboard-replacement).

## Applicability

Use this review for a motherboard repair on an Autopilot-registered device. Match the specific hardware scenario to the source’s supported repair guidance; do not assume that every combination of reused components behaves alike.

## DSE recommendation

Agree on the handoff between the original registration owner, repair facility, and receiving administrator before shipment. Protect required user data through the approved recovery process. Record who will handle deregistration, verify the repaired firmware information, capture the replacement identity, and confirm registration. Give the facility the approved operating-system requirement and a clear return-state acceptance record, without supplying user passwords.

## Verification

Before returning the device to normal use, reconcile the repaired physical unit with the newly registered identity and intended tenant. Check that the unit reaches the expected out-of-box experience rather than an inaccessible previous installation. Perform an authorized enrollment and sign-in test. Hold the return if the tenant, hardware identity, or repair evidence is inconsistent, and route the discrepancy to the responsible registration owner.

## Official references

[Microsoft Learn: Windows Autopilot motherboard replacement](https://learn.microsoft.com/en-us/autopilot/autopilot-motherboard-replacement).

## Primary reference

- Name: Windows Autopilot motherboard replacement | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/autopilot/autopilot-motherboard-replacement
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Plan the Autopilot identity handoff before motherboard repair,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-002-plan-the-autopilot-identity-handoff-before-motherboard-repair/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.