Skip to content

Commit a80fabd

Browse files
authored
Merge pull request #6679 from MicrosoftDocs/lenewsad-patch-4
Update android-fully-managed-enroll.md
2 parents 481d7dd + d2e0ae7 commit a80fabd

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

memdocs/intune/enrollment/android-fully-managed-enroll.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ You must have an Intune standalone tenant to manage Android Enterprise fully man
4646

4747
Devices must meet these requirements to be managed as an Android Enterprise fully managed device:
4848

49-
- Android OS version 6.0 and above.
49+
- Android OS version 8.0 and above.
5050
- Devices must run a build of Android that has Google Mobile Services (GMS) connectivity. Devices must have GMS available and must be able to connect to GMS.
5151

5252
There is no restriction on device manufacturer/OEM if the above requirements are met.
@@ -75,4 +75,4 @@ You can now [enroll your fully managed devices](android-dedicated-devices-fully-
7575

7676
## Next steps
7777
- [Add Android Enterprise fully managed device configuration policies](../configuration/device-restrictions-android-for-work.md#fully-managed-dedicated-and-corporate-owned-work-profile)
78-
- [Configure app configuration policies for Android Enterprise fully managed devices](../apps/app-configuration-policies-use-android.md)
78+
- [Configure app configuration policies for Android Enterprise fully managed devices](../apps/app-configuration-policies-use-android.md)

0 commit comments

Comments
 (0)