Skip to content

Commit a2272b8

Browse files
authored
Update device-enrollment-manager-enroll.md
Deleted outdated reference to remove clutter. Do we really need to point out limitations in Windows 1709 which was EoS several years ago? We're not supporting Windows 10 1709 management in Intune anyway so it makes no sense in explicitly calling out an unsupported feature in an unsupported OS.
1 parent af52b92 commit a2272b8

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

memdocs/intune/enrollment/device-enrollment-manager-enroll.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,6 @@ DEM user accounts and devices that are enrolled with a DEM user account have the
4545
- DEM user accounts cannot use Apple Volume Purchase Program (VPP) apps with Apple VPP user licenses because of per-user Apple ID requirements for app management.
4646
- DEM accounts cannot be used when enrolling devices via Apple's Automated Device Enrollment (ADE).
4747
- Devices can install VPP apps if they have Apple VPP device licenses.
48-
- On Windows 10 1709 and older, conditional access isn't available for Windows devices enrolled using bulk enrollment.
4948
- Every device enrolled with DEM accounts needs to be properly licensed to be managed by Intune. The license could be an Intune user license or an Intune device license.
5049
- If you're [enrolling Android Enterprise personally-owned devices with work profile](android-work-profile-enroll.md) using a DEM account, there is a limit of 10 devices that can be enrolled per account.
5150
- [Enrolling Android Enterprise fully managed devices](android-fully-managed-enroll.md) with DEM accounts isn't supported.

0 commit comments

Comments
 (0)