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: memdocs/intune/enrollment/android-enroll.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,9 +37,9 @@ ms.collection:
37
37
38
38
As an Intune administrator, you can enroll Android devices in the following ways:
39
39
- Android Enterprise (offering a set of enrollment options that provide users with the most up-to-date and secure features):
40
-
-[**Android Enterprise personally-owned with a work profile**](android-work-profile-enroll.md): For personal devices granted permission to access corporate data. Admins can manage work accounts, apps, and data. Personal data on the device is kept separate from work data and admins don't control personal settings or data.
40
+
-[**Android Enterprise personallyowned with a work profile**](android-work-profile-enroll.md): For personal devices granted permission to access corporate data. Admins can manage work accounts, apps, and data. Personal data on the device is kept separate from work data and admins don't control personal settings or data.
41
41
-[**Android Enterprise dedicated**](android-kiosk-enroll.md): For corporate-owned, single use devices, such as digital signage, ticket printing, or inventory management. Admins lock down the usage of a device for a limited set of apps and web links. It also prevents users from adding other apps or taking other actions on the device.
42
-
-[**Android Enterprise fully managed**](android-fully-managed-enroll.md): For corporate-owned, single user devices used exclusively for work and not personal use. Admins can manage the entire device and enforce policy controls unavailable to personally-owned/corporate-owned work profiles.
42
+
-[**Android Enterprise fully managed**](android-fully-managed-enroll.md): For corporate-owned, single user devices used exclusively for work and not personal use. Admins can manage the entire device and enforce policy controls unavailable to personallyowned/corporate-owned work profiles.
43
43
-[**Android Enterprise corporate-owned with a work profile**](android-corporate-owned-work-profile-enroll.md): For corporate-owned, single user devices intended for corporate and personal use.
44
44
-[**Android device administrator**](android-enroll-device-administrator.md), including Samsung Knox Standard devices and [Zebra devices](../configuration/android-zebra-mx-overview.md). Device administrator should be used in areas where Android Enterprise or Google Mobile Services (GMS) is unavailable. Google has decreased support for device administrator (DA) management in areas where Android Enterprise is available, and encourages organizations to migrate to Android Enterprise device management. For a list of countries that support Android Enterprise, see [Is Android Enterprise available in my country](https://support.google.com/work/android/answer/6270910)?
45
45
- Android (AOSP) offers a set of enrollment options for devices that aren't integrated with Google Mobile services.
@@ -61,7 +61,7 @@ For Samsung Knox Standard devices, there are [more prerequisites](android-samsun
61
61
62
62
## Next steps
63
63
64
-
-[Set up Android Enterprise personally-owned work profile enrollment](android-work-profile-enroll.md)
64
+
-[Set up Android Enterprise personallyowned work profile enrollment](android-work-profile-enroll.md)
65
65
-[Set up Android Enterprise dedicated device enrollment](android-kiosk-enroll.md)
66
66
-[Set up Android Enterprise fully managed enrollment](android-fully-managed-enroll.md)
67
67
-[Set up Android device administrator enrollment](android-enroll-device-administrator.md)
0 commit comments