Skip to content

Commit 88f7cfc

Browse files
committed
Update microsoft-defender-endpoint-android.md
1 parent da3f999 commit 88f7cfc

File tree

1 file changed

+12
-6
lines changed

1 file changed

+12
-6
lines changed

defender-endpoint/microsoft-defender-endpoint-android.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: conceptual
1515
ms.subservice: android
1616
search.appverid: met150
17-
ms.date: 02/28/2025
17+
ms.date: 03/21/2025
1818
---
1919

2020
# Microsoft Defender for Endpoint on Android
@@ -81,11 +81,11 @@ Microsoft Defender for Endpoint on Android supports installation on both modes o
8181
- Installation of Microsoft Defender for Endpoint on devices that aren't enrolled using Intune mobile device management (MDM), see [Configure Microsoft Defender for Endpoint risk signals in app protection policy (MAM)](android-configure-mam.md).
8282

8383
> [!NOTE]
84-
> If a user has valid MDE license and registered in Authenticator App or Company Portal App along with sing-in to Defender App, then the device will show up in the Defender Portal.
84+
> If a user has a valid MDE license and is registered in the Authenticator App or Company Portal App, and has signed in to the Defender App, the device appears in the Defender Portal.
8585
8686
> [!NOTE]
8787
> **Microsoft Defender for Endpoint on Android is available on [Google Play](https://play.google.com/store/apps/details?id=com.microsoft.scmx) now.**
88-
> > You can connect to Google Play from Intune to deploy Microsoft Defender for Endpoint app, across Device Administrator and Android Enterprise enrollment modes.
88+
> > You can connect to Google Play from Intune to deploy the Microsoft Defender for Endpoint app across Device Administrator and Android Enterprise enrollment modes.
8989
9090
### Required permissions
9191

@@ -105,17 +105,23 @@ To ensure optimal protection for your device, Microsoft Defender requests access
105105

106106
#### How to resolve the noncompliance state due to silent auth failures
107107

108-
Microsoft Defender for Endpoint has a feature to let the user sign-in according to a set of policies called [Conditional Access policies](/defender-endpoint/configure-conditional-access). If a policy is violated, the Microsoft Defender app autosigns out and starts failing in silent auth (sign-in attempts in background). This process results in the devices being shown as non-compliant in the Intune portal. A user can get the device to compliant status by signing in again.
108+
- Microsoft Defender for Endpoint has a feature to let the user sign-in according to a set of policies called [Conditional Access policies](/defender-endpoint/configure-conditional-access).
109109

110-
The user receives a notification (as shown in the following scenarios) asking them to sign in. The user can tap the notification or open the Microsoft Defender app and sign in. Signing in results in a successful, interactive authentication and causes the Intune portal to show the device as compliant.
110+
- If a policy is violated, the Microsoft Defender app autosigns out and starts failing in silent auth (sign-in attempts in background).
111+
112+
- This process results in the devices being shown as noncompliant in the Intune portal. A user can get the device to compliant status by signing in again.
113+
114+
- Users receive a notification (as shown in the following scenarios) prompting them to sign in.
115+
116+
- They can tap the notification or open the Microsoft Defender app and sign in, which results in a successful, interactive authentication and causes the Intune portal to show the device as compliant.
111117

112118
**Scenario 1:** The following experience occurs when MFA is configured by the admin through a Conditional Access policy:
113119

114120
:::image type="content" source="media/ca-policy-user-flow.png" alt-text="Series of images showing the user flow when a Conditional Access policy is configured by the security team." lightbox="media/ca-policy-user-flow.png":::
115121

116122
**Scenario 2:** The following experience occurs when **MFA is not configured** by the admin through a Conditional Access policy:
117123

118-
:::image type="content" source="media/mfa-not-cong-user-flow.png" alt-text="Screenshot showing the user flow when MFA is not configured by your security team." lightbox="media/mfa-not-cong-user-flow.png":::
124+
:::image type="content" source="media/mfa-not-cong-user-flow.png" alt-text="Screenshot showing the user flow when MFA isn't configured by your security team." lightbox="media/mfa-not-cong-user-flow.png":::
119125

120126
## How to configure Microsoft Defender for Endpoint on Android
121127

0 commit comments

Comments
 (0)