Enroll a Windows 10 device automatically using Group Policy

Starting in Windows 10, version 1709, you can use a Group Policy to trigger auto-enrollment to MDM for Active Directory (AD) domain-joined devices.


  • AD-joined PC running Windows 10, version 1709 or later
  • The enterprise has configured a mobile device management (MDM) service
  • The enterprise AD must be registered with Azure Active Directory (Azure AD)
  • The device should not already be enrolled in Intune using the classic agents (devices managed using agents will fail enrollment with error 0x80180026)

To verify if the device is Azure AD registered, run dsregcmd /status from the command line.

Here is a partial screenshot of the result:

device status result

The auto-enrollment relies of the presence of an MDM service and the Azure Active Directory registration for the PC. Starting in Windows 10, version 1607, once the enterprise has registered its AD with Azure AD, a Windows PC that is domain joined is automatically AAD registered.


In Windows 10, version 1709, the enrollment protocol was updated to check whether the device is domain-joined. For details, see [MS-MDE2]: Mobile Device Enrollment Protocol Version 2. For examples, see section 4.3.1 RequestSecurityToken of the MS-MDE2 protocol documentation.

When the auto-enrollment Group Policy is enabled, a task is created in the background that initiates the MDM enrollment. The task will use the existing MDM service configuration from the Azure Active Directory information of the user. If multi-factor authentication is required, the user will get a prompt to complete the authentication. Once the enrollment is configured, the user can check the status in the Settings page.

In Windows 10, version 1709, when the same policy is configured in GP and MDM, the GP policy wins (GP policy is take precedence over MDM). In the future release of Windows 10, we are considering a feature that allows the admin to control which policy takes precedence.

For this policy to work, you must verify that the MDM service provider allows the GP triggered MDM enrollment for domain joined devices.

Configure the auto-enrollment Group Policy for a single PC

This procedure is only for illustration purposes to show how the new auto-enrollment policy works. It is not recommended for the production environment in the enterprise. For bulk deployment, you should use the Group Policy Management Console process.


  • AD-joined PC running Windows 10, version 1709
  • Enterprise has MDM service already configured
  • Enterprise AD must be registered with Azure AD
  1. Run GPEdit.msc

    Click Start, then in the text box type gpedit.

    GPEdit desktop app search result

  2. Under Best match, click Edit group policy to launch it.

  3. In Local Computer Policy, click Administrative Templates > Windows Components > MDM.

    MDM policies

  4. Double-click Auto MDM Enrollment with AAD Token.

    MDM autoenrollment policy

  5. Click Enable, then click OK.

    A task is created and scheduled to run every 5 minutes for the duration of 1 day. The task is called " Schedule created by enrollment client for automatically enrolling in MDM from AAD."

    To see the scheduled task, launch the Task Scheduler app.

    If two-factor authentication is required, you will be prompted to complete the process. Here is an example screenshot.

    Two-factor authentication notification

  6. To verify successful enrollment to MDM , click Start > Settings > Accounts > Access work or school, then select your domain account.

  7. Click Info to see the MDM enrollment information.

    Work School Settings

    If you do not see the Info button or the enrollment information, it is possible that the enrollment failed. Check the status in Task Scheduler app.

Task Scheduler app

  1. Click Start, then in the text box type task scheduler.

    Task Scheduler search result

  2. Under Best match, click Task Scheduler to launch it.

  3. In Task Scheduler Library, open Microsoft > Windows , then click EnterpriseMgmt.

    Auto-enrollment scheduled task

    To see the result of the task, move the scroll bar to the right to see the Last Run Result. Note that 0x80180026 is a failure message (MENROLL_E_DEVICE_MANAGEMENT_BLOCKED). You can see the logs in the History tab.

    If the device enrollment is blocked, your IT admin may have enabled the Disable MDM Enrollment policy. Note that the GPEdit console does not reflect the status of policies set by your IT admin on your device. It is only used by the user to set policies.

Configure the auto-enrollment for a group of devices


  • AD-joined PC running Windows 10, version 1709
  • Enterprise has MDM service already configured (with Intune or a third party service provider)
  • Enterprise AD must be integrated with Azure AD.
  • Ensure that PCs belong to same computer group.


If you do not see the policy, it may be because you don’t have the ADMX installed for Windows 10, version 1803 or version 1809. To fix the issue, follow these steps:

  1. Download:
    1803 -->Administrative Templates (.admx) for Windows 10 April 2018 Update (1803) or
    1809 --> Administrative Templates for Windows 10 October 2018 Update (1809).
  2. Install the package on the Primary Domain Controller (PDC).
  3. Navigate, depending on the version to the folder: 1803 --> C:\Program Files (x86)\Microsoft Group Policy\Windows 10 April 2018 Update (1803) v2, or
    1809 --> C:\Program Files (x86)\Microsoft Group Policy\Windows 10 October 2018 Update (1809) v2
  4. Copy policy definitions folder to C:\Windows\SYSVOL\domain\Policies.
  5. Restart the Primary Domain Controller for the policy to be available. This procedure will work for any future version as well.
  1. Create a Group Policy Object (GPO) and enable the Group Policy Computer Configuration > Policies > Administrative Templates > Windows Components > MDM > Enable automatic MDM enrollment using default Azure AD credentials.
  2. Create a Security Group for the PCs.
  3. Link the GPO.
  4. Filter using Security Groups.
  5. Enforce a GPO link.


Version 1903 (March 2019) is actually on the Insider program and doesn't yet contain a downloadable version of Templates (version 1903).