From 19ad2c7ff4f79c408f8baf7b1b56ddd72fe4edb2 Mon Sep 17 00:00:00 2001
From: Shravan Thota <57046359+shthota77@users.noreply.github.com>
Date: Sun, 6 Dec 2020 18:48:49 +0530
Subject: [PATCH] Update android-intune.md

---
 .../microsoft-defender-atp/android-intune.md                  | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/windows/security/threat-protection/microsoft-defender-atp/android-intune.md b/windows/security/threat-protection/microsoft-defender-atp/android-intune.md
index ddba7d596d..27d5a07aae 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/android-intune.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/android-intune.md
@@ -254,9 +254,7 @@ displayed here.
     > ![Image of device installation status](images/900c0197aa59f9b7abd762ab2b32e80c.png)
 
 
-2. On the device, you can confirm the same by going to the **work profile** and
-confirm that Defender for Endpoint is available.
-
+2. On the device, you can validate the onboarding status by going to the **work profile**. Confirm that Defender for Endpoint is available and that you are enrolled to **Personally-owned devices with work profile**.   If you are enrolled to **Corporate-owned, fully managed user device**, you will have a single profile on the device where you can confirm that Defender for Endpoint is available.
     ![Image of app in mobile device](images/c2e647fc8fa31c4f2349c76f2497bc0e.png)
 
 3. When the app is installed, open the app and accept the permissions