added note

windows/deployment/windows-autopilot/user-driven.md

@@ -9,7 +9,8 @@ ms.mktglfcycl: deploy
 ms.localizationpriority: medium
 ms.sitesec: library
 ms.pagetype: deploy
-audience: itpro
author: greg-lindsay
+audience: itpro
+author: greg-lindsay
 ms.author: greglin
 ms.collection: M365-modern-desktop
 ms.topic: article
@@ -54,6 +55,9 @@ For each device that will be deployed using user-driven deployment, these additi
 
 Also see the [Validation](#validation) section below.
 
+>[!NOTE]
+>If the device reboots during the device enrollment status page (ESP) in the user-driven Azure Active Directoy join scenario, the user will not automatically sign on because the user's credentials cannot be saved across reboots.  In this scenario, the user will need to sign in manually after the device ESP completes.
+
 ### User-driven mode for hybrid Azure Active Directory join
 
 Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be [hybrid Azure Active Directory (AAD) joined](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan).  
@@ -96,4 +100,4 @@ When performing a user-driven deployment using Windows Autopilot, the following
 - Once the device configuration tasks have completed, the user will be signed into Windows 10 using the credentials they previously provided.
 - Once signed in, the enrollment status page will again be displayed for user-targeted configuration tasks.
 
-In case the observed results do not match these expectations, consult the [Windows Autopilot Troubleshooting](troubleshooting.md) documentation.
+If your results do not match these expectations, see the [Windows Autopilot Troubleshooting](troubleshooting.md) documentation.