Update microsoft-defender-endpoint-android.md

Author: denisebmsft

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

@@ -60,7 +60,6 @@ This article describes how to install, configure, update, and use Defender for E
 
 ### System Requirements
 
-- 
 - Intune Company Portal app should be downloaded from [Google Play](https://play.google.com/store/apps/details?id=com.microsoft.windowsintune.companyportal) and installed for seamless onboarding. Device enrollment is required for Intune device compliance policies to be enforced.
 
 - Mobile phones and tablets running Android 8.0 and above. **(Note: Microsoft Defender is ending support for Android 8, 8.1 and 9 versions on April 30, 2025, after that device running on Android version < 10 won't be supported)**
@@ -103,18 +102,18 @@ To ensure optimal protection for your device, Microsoft Defender requests access
 - **Location Access**: The Microsoft Defender app uses your location to help secure your Wi-Fi network and enhance device protection.
 
 #### How to resolve the non-compliance state due to silent auth failures
-
+:::image type="content" source="media/microsoft-defender-endpoint-android/mfa-not-cong-user-flow.jpeg" alt-text="":::
 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 auto-signs out and starts failing in silent auth (sign-in attempts in background). This results in the devices being shown as non-compliant on Intune portal.  A user can get the device to compliant by signing in again.
 
 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.
 
 **Scenario 1:** The following experience occurs when MFA is configured by the admin through a Conditional Access policy:
 
-:::image type="content" source="media/microsoft-defender-endpoint-android/ca-policy-user-flow.jpeg" alt-text="Series of images showing the user flow when a Conditional Access policy is configured by the security team.":::
+:::image type="content" source="media/microsoft-defender-endpoint-android/ca-policy-user-flow.jpeg" alt-text="Series of images showing the user flow when a Conditional Access policy is configured by the security team." lightbox="media/microsoft-defender-endpoint-android/ca-policy-user-flow.jpeg":::
 
 **Scenario 2:** The following experience occurs when **MFA is not configured** by the admin through a Conditional Access policy:
 
-:::image type="content" source="media/microsoft-defender-endpoint-android/mfa-not-cong-user-flow.jpeg" alt-text="Screenshot showing the user flow when MFA is not configured by your security team.":::
+:::image type="content" source="media/microsoft-defender-endpoint-android/mfa-not-cong-user-flow.jpeg" alt-text="Screenshot showing the user flow when MFA is not configured by your security team." lightbox="media/microsoft-defender-endpoint-android/mfa-not-cong-user-flow.jpeg":::
 
 ## How to Configure Microsoft Defender for Endpoint on Android