If multi-factor authentication is required, the user will get a prompt to complete the authentication. The task will use the existing MDM service configuration from the Azure Active Directory information of the user. When the auto-enrollment Group Policy is enabled, a task is created in the background that initiates the MDM enrollment. For examples, see section 4.3.1 RequestSecurityToken of the MS-MDE2 protocol documentation. For details, see : Mobile Device Enrollment Protocol Version 2. In Windows 10, version 1709, the enrollment protocol was updated to check whether the device is domain-joined. For more information, see How to plan your hybrid Azure Active Directory join implementation. The minimum Windows Server version requirement is based on the Hybrid Azure AD join requirement.The device shouldn't already be enrolled in Intune using the classic agents (devices managed using agents will fail enrollment with error 0x80180026).The on-premises Active Directory must be integrated with Azure AD (via Azure AD Connect).The enterprise has configured a Mobile Device Management (MDM) service.The Active Directory joined device must be running a supported version of Windows.The enrollment process starts in the background once you sign in to the device with your Azure AD account. This cause-and-effect mechanism means you can automatically mass-enroll a large number of domain-joined corporate devices into Microsoft Intune. The enrollment into Intune is triggered by a group policy created on your local AD and happens without any user interaction. You can use a Group Policy to trigger auto-enrollment to Mobile Device Management (MDM) for Active Directory (AD) domain-joined devices.
0 kommentar(er)
