You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/microsoft-defender-endpoint-android.md
+15-7Lines changed: 15 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: conceptual
15
15
ms.subservice: android
16
16
search.appverid: met150
17
-
ms.date: 02/28/2025
17
+
ms.date: 03/21/2025
18
18
---
19
19
20
20
# Microsoft Defender for Endpoint on Android
@@ -65,7 +65,7 @@ This article describes how to install, configure, update, and use Defender for E
65
65
66
66
**What does it mean devices running on unsupported Android version?**
67
67
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.
69
69
70
70
**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.
71
71
@@ -80,10 +80,12 @@ Microsoft Defender for Endpoint on Android supports installation on both modes o
80
80
81
81
- 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).
82
82
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
+
83
86
> [!NOTE]
84
87
> **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.
87
89
88
90
### Required permissions
89
91
@@ -103,17 +105,23 @@ To ensure optimal protection for your device, Microsoft Defender requests access
103
105
104
106
#### How to resolve the noncompliance state due to silent auth failures
105
107
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.
107
115
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.
109
117
110
118
**Scenario 1:** The following experience occurs when MFA is configured by the admin through a Conditional Access policy:
111
119
112
120
:::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":::
113
121
114
122
**Scenario 2:** The following experience occurs when **MFA is not configured** by the admin through a Conditional Access policy:
115
123
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":::
117
125
118
126
## How to configure Microsoft Defender for Endpoint on Android
0 commit comments