Skip to content

Commit eff68b6

Browse files
committed
Learn Editor: Update android-intune.md
1 parent 3ab52fa commit eff68b6

File tree

1 file changed

+8
-18
lines changed

1 file changed

+8
-18
lines changed

defender-endpoint/android-intune.md

Lines changed: 8 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,8 @@ Learn how to deploy Defender for Endpoint on Android on Microsoft Intune Company
3838
3939
## Deploy on Device Administrator enrolled devices
4040

41+
(Intune and MDE will be ending support for Device Administrator enrolled devices with access to [Google Mobile Services](/mem/intune/apps/manage-without-gms) (GMS), beginning December 31, 2024. Refer to [this article](https://techcommunity.microsoft.com/blog/intunecustomersuccess/intune-ending-support-for-android-device-administrator-on-devices-with-gms-in-de/3915443) for more details.)
42+
4143
Learn how to deploy Defender for Endpoint on Android with Microsoft Intune Company Portal - Device Administrator enrolled devices.
4244

4345
### Add as Android store app
@@ -282,9 +284,7 @@ Android low touch onboarding is disabled by default. Admins can enable it throug
282284

283285
1. Select **Low touch onboarding and User UPN**. For User UPN, change the value type to `Variable`, and set the configuration value to `User Principal Name`. Enable low-touch onboarding by changing its configuration value to `1`.
284286

285-
> [!div class="mx-imgBorder"]
286-
> ![Screenshot showing a low touch onboarding configuration policy.](media/low-touch-user-upn.png)
287-
287+
> [!div class="mx-imgBorder"]
288288
> [!Note]
289289
> Once the policy is created, these value types will show as string.
290290
@@ -300,29 +300,19 @@ Admins can go to the [Microsoft Endpoint Management admin center](https://intune
300300

301301
1. Go to **Apps> App configuration policies** and click on **Add**. Select **Managed Devices**.
302302

303-
> [!div class="mx-imgBorder"]
304-
> ![Image of adding app configuration policy.](media/addpolicy.png)
305-
303+
> [!div class="mx-imgBorder"]
306304
1. Enter **Name** and **Description** to uniquely identify the configuration policy. Select platform as **'Android Enterprise'**, Profile type as **'Personally-owned work profile only'** and Targeted app as **'Microsoft Defender'**.
307305

308-
> [!div class="mx-imgBorder"]
309-
> ![Image of naming configuration policy.](media/selectapp.png)
310-
306+
> [!div class="mx-imgBorder"]
311307
1. On the settings page, in **'Configuration settings format'**, select **'Use configuration designer'** and click on **Add**. From the list of configurations that are displayed, select **'Microsoft Defender in Personal profile'**.
312308

313-
> [!div class="mx-imgBorder"]
314-
> ![Image of configuring personal profile.](media/addconfiguration.png)
315-
309+
> [!div class="mx-imgBorder"]
316310
1. The selected configuration will be listed. Change the **configuration value to 1** to enable Microsoft Defender support personal profiles. A notification will appear informing the admin about the same. Click on **Next**.
317311

318-
> [!div class="mx-imgBorder"]
319-
> ![Image of changing config value.](media/changeconfigvalue.png)
320-
312+
> [!div class="mx-imgBorder"]
321313
1. **Assign** the configuration policy to a group of users. **Review and create** the policy.
322314

323-
> [!div class="mx-imgBorder"]
324-
> ![Image of reviewing and creating policy.](media/savepolicy.png)
325-
315+
> [!div class="mx-imgBorder"]
326316
Admins also can set up **privacy controls** from the Microsoft Intune admin center to control what data can be sent by the Defender mobile client to the security portal. For more information, see [configuring privacy controls](android-configure.md).
327317

328318
Organizations can communicate to their users to protect Personal profile with Microsoft Defender on their enrolled BYOD devices.

0 commit comments

Comments
 (0)