Skip to content

Commit 402fd25

Browse files
authored
Merge branch 'main' into revert-3204-update-mte-dex
2 parents b8dde21 + e23270a commit 402fd25

File tree

1 file changed

+15
-7
lines changed

1 file changed

+15
-7
lines changed

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

Lines changed: 15 additions & 7 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
@@ -65,7 +65,7 @@ This article describes how to install, configure, update, and use Defender for E
6565

6666
**What does it mean devices running on unsupported Android version?** 
6767

68-
**New users**: The application is longer available for new installations on devices running on unsupported versions. When users with unsupported versions attempt to download the Microsoft Defender app, the Google Play store notifies them that the device is incompatible.
68+
**New users**: The application is no longer available for new installations on devices running on unsupported versions. When users with unsupported versions attempt to download the Microsoft Defender app, the Google Play store notifies them that the device is incompatible.
6969

7070
**Existing users**: The Microsoft Defender app continues to function for existing users on unsupported versions, but they don't receive updates from the Google Play store because they don't meet the minimum SDK version requirements. Therefore, any new updates on the app aren't available to devices running unsupported versions. Microsoft no longer addresses bugs or provides maintenance for unsupported operating system versions. Any issues occurring on devices running on unsupported versions aren't investigated. 
7171

@@ -80,10 +80,12 @@ Microsoft Defender for Endpoint on Android supports installation on both modes o
8080

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

83+
> [!NOTE]
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.
85+
8386
> [!NOTE]
8487
> **Microsoft Defender for Endpoint on Android is available on [Google Play](https://play.google.com/store/apps/details?id=com.microsoft.scmx) now.**
85-
>
86-
> 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.
8789
8890
### Required permissions
8991

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

104106
#### How to resolve the noncompliance state due to silent auth failures
105107

106-
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).
109+
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.
107115

108-
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.
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.
109117

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

112120
:::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":::
113121

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

116-
:::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":::
117125

118126
## How to configure Microsoft Defender for Endpoint on Android
119127

0 commit comments

Comments
 (0)