Skip to content

Commit 618cb29

Browse files
author
Angela Fleischmann
authored
Update android-enroll.md
Lines 40, 42, and 64: personally-owned > personally owned
1 parent 9e17ff2 commit 618cb29

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

memdocs/intune/enrollment/android-enroll.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,9 @@ ms.collection:
3737

3838
As an Intune administrator, you can enroll Android devices in the following ways:
3939
- 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 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.
4141
- [**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 personally owned/corporate-owned work profiles.
4343
- [**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.
4444
- [**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)?
4545
- 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
6161

6262
## Next steps
6363

64-
- [Set up Android Enterprise personally-owned work profile enrollment](android-work-profile-enroll.md)
64+
- [Set up Android Enterprise personally owned work profile enrollment](android-work-profile-enroll.md)
6565
- [Set up Android Enterprise dedicated device enrollment](android-kiosk-enroll.md)
6666
- [Set up Android Enterprise fully managed enrollment](android-fully-managed-enroll.md)
6767
- [Set up Android device administrator enrollment](android-enroll-device-administrator.md)

0 commit comments

Comments
 (0)