From 47f446904f44d3c3c5f0c9fad0fc38b1a970d225 Mon Sep 17 00:00:00 2001
From: ShrCaJesmo <54860945+ShrCaJesmo@users.noreply.github.com>
Date: Wed, 4 Mar 2020 12:08:51 -0500
Subject: [PATCH] Update troubleshooting.md

Adds a note not to delete the associated azure object, with remediation steps if it's been deleted.
---
 windows/deployment/windows-autopilot/troubleshooting.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/windows/deployment/windows-autopilot/troubleshooting.md b/windows/deployment/windows-autopilot/troubleshooting.md
index b2e13bb564..a03e5fbb55 100644
--- a/windows/deployment/windows-autopilot/troubleshooting.md
+++ b/windows/deployment/windows-autopilot/troubleshooting.md
@@ -128,6 +128,8 @@ On devices running a [supported version](https://docs.microsoft.com/windows/rele
 
 The most common issue joining a device to Azure AD is related to Azure AD permissions.  Ensure [the correct configuration is in place](windows-autopilot-requirements.md) to allow users to join devices to Azure AD.  Errors can also happen if the user has exceeded the number of devices that they are allowed to join, as configured in Azure AD.
 
+An Azure AD device is created upon import - it's important that this object not be deleted. It acts as Autopilot's anchor in AAD for group membership and targeting (including the profile) and can lead to join errors if it's deleted. Once this object has been deleted, to fix the issue, deleting and reimporting this autopilot hash will be necessary so it can recreate the associated object.
+
 Error code 801C0003 will typically be reported on an error page titled "Something went wrong".  This error means that the Azure AD join failed.
 
 ## Troubleshooting Intune enrollment issues