From f72e87b94942c844dbded6d2172e5bbabb8965c7 Mon Sep 17 00:00:00 2001
From: amirsc3 <42802974+amirsc3@users.noreply.github.com>
Date: Tue, 17 Mar 2020 10:24:28 +0200
Subject: [PATCH] Update troubleshoot-onboarding.md

Adding some test to better explain why the manual application deployment is needed.
---
 .../microsoft-defender-atp/troubleshoot-onboarding.md          | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md
index b09ed0ab89..db55660b65 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-onboarding.md
@@ -295,10 +295,11 @@ You might also need to check the following:
 ## Confirming onboarding of newly built machines 
 There may be instances when onboarding is deployed on a newly built machine but not completed. 
 
-The following steps provide guidance for the following scenario:
+The steps below provide guidance for the following scenario:
 - Onboarding package is deployed to newly built machines
 - Sensor does not start because the Out-of-box experience (OOBE) or first user logon has not been completed
 - Machine is turned off and shipped to the end user
+- In this scenario, the SENSE service will not start automatically even though onboarding package was deployed
 
 >[!NOTE]
 >The following steps are only relevant when using Microsoft Endpoint Configuration Manager (current branch)