diff --git a/intune/intune-service/enrollment/android-dedicated-devices-fully-managed-enroll.md b/intune/intune-service/enrollment/android-dedicated-devices-fully-managed-enroll.md
index 2be5a0094c..ff2210a329 100644
--- a/intune/intune-service/enrollment/android-dedicated-devices-fully-managed-enroll.md
+++ b/intune/intune-service/enrollment/android-dedicated-devices-fully-managed-enroll.md
@@ -37,7 +37,7 @@ ms.collection:
After you've set up your Android Enterprise [dedicated devices](android-kiosk-enroll.md), [fully managed devices](android-fully-managed-enroll.md), or [corporate-owned work profile devices](android-corporate-owned-work-profile-enroll.md) in Intune, you can enroll the devices. Intune enrollment for dedicated devices, fully managed devices, and corporate-owned with a work profile start with a factory reset. How you enroll your Android Enterprise devices depends on the operating system.
-| Enrollment method | Minimum Android OS version for dedicated and fully managed devices |
+| Enrollment method | Minimum Android OS version for dedicated |
| ----- | ----- |
| Near Field Communication | 8.0 |
| Token entry | 8.0 |
@@ -46,7 +46,7 @@ After you've set up your Android Enterprise [dedicated devices](android-kiosk-en
| [Knox Mobile Enrollment](./android-samsung-knox-mobile-enroll.md) | 8.0
On Samsung Knox 2.8 or higher devices only. |
> [!TIP]
-> Corporate-owned work profile (COPE) device management is available on Android version 8.0 and newer.
+> Corporate-owned work profile (COPE), Fully Managed device management (COBO) is available on Android version 10.0 and newer.
> [!NOTE]
> If you have a Microsoft Entra Conditional Access policy defined that uses the *require a device to be marked as compliant* Grant control or a Block policy and applies to **All Cloud apps**, **Android**, and **Browsers**, you must exclude the **Microsoft Intune** cloud app from this policy. This is because the Android setup process uses a Chrome tab to authenticate your users during enrollment. For more information, see [Microsoft Entra Conditional Access documentation](/azure/active-directory/conditional-access/).
@@ -155,7 +155,7 @@ To use Samsung Knox Mobile Enrollment, the device must be running Android OS ver
Create a specially formatted NFC tag to provision NFC-supported devices running Android 8.0 or later. You can use your own app or any NFC tag-creation tool. For more information, see [C-based Android Enterprise device enrollment with Microsoft Intune](/archive/blogs/cbernier/nfc-based-android-enterprise-device-enrollment-with-microsoft-intune) and [Google's Android Management API documentation](https://developers.google.com/android/management/provision-device#nfc_method).
-For corporate-owned work profile (COPE) devices, the NFC enrollment method is only supported on devices running Android versions 8.0 or later. It's not supported with Android 11.0. For more information, see the [Google developer docs](https://developers.google.com/android/management/provision-device#company-owned_devices_for_work_and_personal_use:~:text=Note%3A%20DPC%20identifier%20method%20only%20supports%20full%20device%20management%20provisioning%20and%20cannot%20be%20used%20for%20corporate%2Downed%2C%20personally%20enabled,(COPE)%20provisioning%20on%20Android%2011%20devices.,-Company%2Downed).
+For corporate-owned work profile (COPE) devices, the NFC enrollment method is only supported on devices running Android versions 10.0. It's not supported with Android 11.0. For more information, see the [Google developer docs](https://developers.google.com/android/management/provision-device#company-owned_devices_for_work_and_personal_use:~:text=Note%3A%20DPC%20identifier%20method%20only%20supports%20full%20device%20management%20provisioning%20and%20cannot%20be%20used%20for%20corporate%2Downed%2C%20personally%20enabled,(COPE)%20provisioning%20on%20Android%2011%20devices.,-Company%2Downed).
## Enroll by using a token
We recommend this method for new or factory-reset devices, in scenarios where the QR code or NFC method aren't available. It requires the person provisioning the device to type in the enrollment token string (example: `12345`) that they're provided. When you're ready for enrollment, share the token directly with targeted users or post it to your organization's support site for easy retrieval. The token works for all Intune-licensed users and doesn't expire.