Skip to content

Commit de73e3b

Browse files
authored
Merge pull request #1227 from joshgingras/docs-editor/android-intune-1724760471
Update article clarifying corporate-owned devices with work profile are supported in Android Enterprise
2 parents 133bada + 91f31ff commit de73e3b

File tree

1 file changed

+24
-24
lines changed

1 file changed

+24
-24
lines changed

defender-endpoint/android-intune.md

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ Defender for Endpoint on Android supports Android Enterprise enrolled devices.
9393

9494
For more information on the enrollment options supported by Microsoft Intune, see [Enrollment Options](/mem/intune/enrollment/android-enroll).
9595

96-
**Currently, personally owned devices using a work profile and corporate-owned, fully managed user device enrollments are supported for deployment.**
96+
**Currently, Personally-owned devices with work profile, Corporate-owned devices with work profile, and Corporate-owned fully managed user device enrollments are supported in Android Enterprise.**
9797

9898
## Add Microsoft Defender for Endpoint on Android as a Managed Google Play app
9999

@@ -280,11 +280,11 @@ Android low touch onboarding is disabled by default. Admins can enable it throug
280280

281281
6. Under **Configuration settings**, select `Use Configuration designer`, and then select **Add**.
282282

283-
7. 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`.
284-
285-
>[!div class="mx-imgBorder"]
286-
>![Screenshot showing a low touch onboarding configuration policy.](media/low-touch-user-upn.png)
283+
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`.
287284

285+
> [!div class="mx-imgBorder"]
286+
> ![Screenshot showing a low touch onboarding configuration policy.](media/low-touch-user-upn.png)
287+
288288
8. Assign the policy to the target user group.
289289

290290
9. Review and create the policy.
@@ -297,29 +297,29 @@ Admins can go to the [Microsoft Endpoint Management admin center](https://intune
297297

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

300-
> [!div class="mx-imgBorder"]
301-
> ![Image of adding app configuration policy.](media/addpolicy.png)
302-
303-
2. 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'**.
304-
305-
> [!div class="mx-imgBorder"]
306-
> ![Image of naming configuration policy.](media/selectapp.png)
307-
308-
3. 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'**.
309-
310-
> [!div class="mx-imgBorder"]
311-
> ![Image of configuring personal profile.](media/addconfiguration.png)
312-
313-
4. 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**.
300+
> [!div class="mx-imgBorder"]
301+
> ![Image of adding app configuration policy.](media/addpolicy.png)
302+
303+
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'**.
314304

315-
> [!div class="mx-imgBorder"]
316-
> ![Image of changing config value.](media/changeconfigvalue.png)
305+
> [!div class="mx-imgBorder"]
306+
> ![Image of naming configuration policy.](media/selectapp.png)
307+
308+
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'**.
317309

318-
5. **Assign** the configuration policy to a group of users. **Review and create** the policy.
310+
> [!div class="mx-imgBorder"]
311+
> ![Image of configuring personal profile.](media/addconfiguration.png)
312+
313+
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**.
319314

320-
> [!div class="mx-imgBorder"]
321-
> ![Image of reviewing and creating policy.](media/savepolicy.png)
315+
> [!div class="mx-imgBorder"]
316+
> ![Image of changing config value.](media/changeconfigvalue.png)
317+
318+
1. **Assign** the configuration policy to a group of users. **Review and create** the policy.
322319

320+
> [!div class="mx-imgBorder"]
321+
> ![Image of reviewing and creating policy.](media/savepolicy.png)
322+
323323
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).
324324

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

0 commit comments

Comments
 (0)