Daily Intune News
Aboutmerill.net
Windows Autopilot
Device enrollment

General

30 October 2026Doc update+171 / −173 lines

In brief

The page updates metadata and links and clarifies guidance for requirement categories, proxy and OOBE conditions, and Intune Connector installation, permissions, and scaling.

What Intune admins need to know

Administrators can use the clearer guidance when reviewing hybrid join deployments and connector setup.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diffView on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Requirements

The list of requirements for performing Microsoft Entra hybrid join during Windows Autopilot is organized into three different categories:

  • General -: general requirements.requirements
  • Device enrollment -: device enrollment requirements.requirements
  • Intune connector -: Intune Connector for Active Directory requirements.requirements

Select the appropriate tab to see the relevant requirements:

General

Device enrollment

The device to be enrolledyou enroll must followmeet these requirements:

  • Use a currently supported version of Windows.
  • Have access to the internet following Windows Autopilot network requirements.
  • Have access to an Active Directory domain controller.
  • Successfully ping the domain controller of the domain being joined.
  • If using Proxy,a proxy, enable and configure the Web Proxy Auto-Discovery Protocol (WPAD) Proxyproxy settings option must be enabled and configured.option.
  • UndergoBe in the out-of-box experience (OOBE). when starting the Windows Autopilot deployment.
  • Use an authorization type that Microsoft Entra ID supports in OOBE.

Although not required, configuring Microsoft Entra hybrid join for Active Directory Federated Services (ADFS) enables a faster Windows Autopilot Microsoft Entra registration process during deployments. Federated customers that arenuse ADFS and don't supporting the use ofsupport passwords and using ADFS need to follow the steps in the article Active Directory Federation Services prompt=login parameter support to properly configure the authentication experience.authentication.

Intune connector

  • TheInstall the Intune Connector for Active Directory, also known as the Offline Domain Join (ODJ) connector, must be installed on a computer that's running runs Windows Server 2016 or later with .NET Framework version 4.7.2 or later.

  • The server hosting the Intune Connector for Active Directory must have access to the Internet and Active Directory.

    Note

  • To increase scale and availability, install multiple connectors can be installed in a domain. Each connector must be able to create computer objects in the domain that it supports.

  • The administrator installingwho installs the Intune Connector for Active Directory must be a local administrator on the server where the Intune Connector for Active Directory is being installed.

  • For the updated Intune Connector for Active Directory, installation needs to be done withuse an account that has the following domain rights:

    • Required -: Create msDs-ManagedServiceAccount objects in the Managed Service Accounts container

    • Optional -: Modify permissions in OUs in Active Directory - ifDirectory. If the administrator installingwho installs the updated Intune Connector for Active Directory doesn't have this right, additional configuration steps are required by an administrator who has these rights.rights must complete additional configuration steps. For more information, see the section Increase the computer account limit in the Organizational Unit (OU) in this article..

      These rights allow the Intune Connector for Active Directory install to properly create Managed Service Accounts (MSAs) and set permissions correctly for the OUs that the MSA is adding computers to.

Set up Windows automatic MDM enrollment

  1. Sign in to the Azure portal and select Microsoft Entra ID.
  2. In the left hand pane, select Manage |> Mobility (MDM and WIP) >, and then select Microsoft Intune.
  3. Make sureEnsure users who deploy Microsoft Entra Entra–joined devices by using Intune and Windows are members of a group included in MDM User scope.
  4. Use the default values in thefor MDM Terms of use URL, MDM Discovery URL, and MDM Compliance URL boxes,, and then select Save.

Install the Intune Connector for Active Directory

Important

The Intune Connector for Active Directory versions older than 6.2501.2000.5 are deprecated and can no longer process enrollment requests. For more information, see the Intune Connector for Active Directory with low-privileged account for Windows Autopilot Hybrid Microsoft Entra join deployments blog post.

To update the connector, you must:

  1. Manually uninstall the legacy connector. There isn't an automatic option.
  2. Download and install the updated connector (describedconnector, as described in this article).article.

Tip

If usingyou use multiple domains to enroll Autopilot devices:

  • You'd need a separate connector instance for each domain. A connector can only process enrollment requests for the same domain as the server it was installed on.
  • There can be at most 1one connector per server (VMserver, whether virtual machine or physical). Additionalphysical. You can set up more servers per domain can be set up for redundancy, each with its own connector installed. In that setup, if one connector fails, the requests will go to another connector on another server withinin the same domain.

Select the tab that corresponds to the version of the Intune Connector for Active Directory that is being installed:you want to install:

Updated Connector

Before you begin

Turn off Internet Explorer Enhanced Security Configuration

Starting with version 6.2504.2001.8, the updated Intune Connector for Active Directory switched to using WebView2, built on Microsoft Edge, instead of WebBrowser, built on Microsoft Internet Explorer. This change means that you no longer need to turn off the Internet Explorer Enhanced Security Configuration setting in Windows Server no longer needs to be turned off.Server. Make sure to install version 6.2504.2001.8 or later of the Intune Connector for Active Directory to avoid issues with the Internet Explorer Enhanced Security Configuration setting.

Download the Intune Connector for Active Directory

  1. On the server where you're installing the Intune Connector for Active Directory is being installed,Directory, sign in to the Microsoft Intune admin center.
  2. In the Home screen, select Devicesin the left hand pane.pane, select Devices.
  3. In the Devices | Overview screen, under By platform, select Windows.
  4. In the Windows | Windows devices screen, under Device onboarding, select Enrollment.
  5. In the Windows | Windows enrollment screen, under Windows Autopilot, select Intune Connector for Active Directory.
  6. In the Intune Connector for Active Directory screen, select Add.
  7. In the Add connector window that opens,window, under Configuring the Intune Connector for Active Directory, select Download the on-premises Intune Connector for Active Directory. The link downloads a file called ODJConnectorBootstrapper.exe.

Install the Intune Connector for Active Directory on the server

Important

TheYou need to install the Intune Connector for Active Directory installation needs to be done with an account that has the following domain rights:

  • Required -: Create msDs-ManagedServiceAccount objects in the Managed Service Accounts container.
  • Optional -: Modify permissions in OUs in Active Directory - ifDirectory. If the administrator installingwho installs the updated Intune Connector for Active Directory doesn't have this right, additional configuration steps are required by an administrator who has these rights.rights needs to perform additional configuration steps. For more information, see the step/section Increase the computer account limit in the Organizational Unit.

  1. Sign in to the server where you're installing the Intune Connector for Active Directory is being installed with an account that has local administrator rights.

  2. If the previous legacy Intune Connector for Active Directory is installed, uninstall it first before installingyou install the updated Intune Connector for Active Directory. For more information, see Uninstall the Intune Connector for Active Directory.

    Important

    When uninstallingyou uninstall the previous legacy Intune Connector for Active Directory, make sure toensure you run the legacy Intune Connector for Active Directory installer as part of the uninstall process. If the legacy Intune Connector for Active Directory installer prompts to Uninstall it when it's run, runs, select to uninstall it. This step ensures that the previous legacy Intune Connector for Active Directory is fully uninstalled. TheYou can download the legacy Intune Connector for Active Directory installer can be downloaded from Intune Connector for Active Directory.

    Tip

    In domains with only a single Intune Connector for Active Directory, Microsoft recommends first installing the updated Intune Connector for Active Directory on another server. InstallingYou should install the updated Intune Connector for Active Directory on another server should be done before uninstallingyou uninstall the legacy Intune Connector for Active Directory on the current server. InstallingBy installing the Intune Connector for Active Directory on another first avoidsserver first, you avoid any downtime while the Intune Connector for Active Directory is being updatedupdating on the current server.

  3. Open the ODJConnectorBootstrapper.exe file that you downloaded to launch the Intune Connector for Active Directory Setup install.

  4. Step through the Intune Connector for Active Directory Setup install.

  5. At the end of the install, select the checkbox Launch Intune Connector for Active Directory.

    Note

    If you accidentally close Intune Connector for Active Directory Setup install is accidentally closed without selecting the checkbox Launch Intune Connector for Active Directory, you can reopen the Intune Connector for Active Directory configuration can be reopened by selecting Intune Connector for Active Directory > Intune Connector for Active Directory from the Start menu.

Sign in to the Intune Connector for Active Directory

  1. In the Intune Connector for Active Directory window,, under the Enrollment tab, select Sign In.

  2. UnderIn the Sign In tab, sign in with the Microsoft Entra ID credentials of an Intune administrator role. The user account must have an assigned Intune license. The sign in process might take a few minutes to complete.

    Note

    The account usedyou use to enroll the Intune Connector for Active Directory is only a temporary requirement at the time of installation. The account isn't used going forward after the server is enrolled.

  3. OnceAfter the sign in process completes:

    1. The Intune Connector for Active Directory successfully enrolled confirmation window appears. Select OK to close the window.
    2. A Managed Service Account with name "<MSA_name>" was successfully set up confirmation window appears. The name of the MSA is in the format msaODJ#####, where ##### are five random characters. NotateNote the name of the MSA that was created, and then select OK to close the window. TheYou might need the name of the MSA might be needed later to configure the MSA to allow creating computer objects in OUs.

  4. The Enrollment tab shows Intune Connector for Active Directory is enrolled. The Sign In button is greyed out and Configure Managed Service Account is enabled.

  5. Close the Intune Connector for Active Directory window.

Verify the Intune Connector for Active Directory is active

After authenticating,you authenticate, the Intune Connector for Active Directory finishes installing. Once it finishes installing,When the installation finishes, verify that it's active in Intune by following these steps:

  1. Go to the Microsoft Intune admin center if it's still open. If the Add connector window is still displayed, close it.

    If the Microsoft Intune admin center isn't still open:

    1. Sign in to the Microsoft Intune admin center.
    2. In the Home screen, select Devicesin the left hand pane.pane, select Devices.
    3. In the Devices | Overview screen, under By platform, select Windows.
    4. In the Windows | Windows devices screen, under Device onboarding, select Enrollment.
    5. In the Windows | Windows enrollment screen, under Windows Autopilot, select Intune Connector for Active Directory.

  2. In the Intune Connector for Active Directory page:

    • Confirm that the server is displayed under Connector name and shows as Active under Status.
    • For the updated Intune Connector for Active Directory, make sure the version is greater than or equal to 6.2501.2000.5.

    If the server isn't displayed, select Refresh or navigate away from the page, and then navigatego back to the Intune Connector for Active Directory page.

Note

  • It can take several minutes for the newly enrolled server to appear in the Intune Connector for Active Directory page of the Microsoft Intune admin center. The enrolled server only appears if it can successfully communicate with the Intune service.
  • Inactive Intune Connectors for Active Directory still appear in the Intune Connector for Active Directory page and willis automatically be cleaned up after 30 days.

After you install the Intune Connector for Active Directory is installed,Directory, it will startstarts logging in the Event Viewer under the path Applications and Services Logs > Microsoft > Intune > ODJConnectorService. Under this path, you can find Admin and Operational logs can be found.logs.

Configure the MSA to allow creating objects in OUs (optional)

By default, MSAs only have access to create computer objects in the Computers container. MSAs don't have access to create computer objects in Organizational Units (OUs). To allow the MSA to create objects in OUs, the OUsyou need to be addedadd the OUs to the ODJConnectorEnrollmentWizard.exe.config XML file found in ODJConnectorEnrollmentWizard directory where theyou installed Intune Connector for Active Directory was installed,Directory, normally C:\Program Files\Microsoft Intune\ODJConnector\.

To configure the MSA to allow creating objects in OUs, follow these steps:

  1. On the server where the Intune Connector for Active Directory is installed, navigate to the ODJConnectorEnrollmentWizard directory where the Intune Connector for Active Directory wasis installed, normally C:\Program Files\Microsoft Intune\ODJConnector\.

  2. In the ODJConnectorEnrollmentWizard directory, open the existing ODJConnectorEnrollmentWizard.exe.config XML file in a text editor, for example,such as Notepad.

  3. In the add key element of the ODJConnectorEnrollmentWizard.exe.config XML file:

    • Next to value=, add in any desired OUs that the MSA should have access to create computer objects in.
    • The OU name needs to be in the LDAP distinguished name format and if applicable, needs to be escaped.
    • MultipleSeparate multiple OUs are supported by separating each OU with a semicolon (;).
    • Make sure to retainRetain the quotes (") next to value=. All of the OU values need to be withinin one pair of quotes.
    • Don't change the name of the key element OrganizationalUnitsUsedForOfflineDomainJoin.

    The following example is an example XML entry with multiple OUs in LDAP distinguished name format:

    Tip

    In the following example, replace the example red text next to value= with theyour organization's OUs in LDAP distinguished name format. As shown in the example, make sureensure all OU entries are within the quotes (") and that each OU is separated with a semicolon (;).

  4. OnceAfter you add all desired OUs are added,OUs, save the ODJConnectorEnrollmentWizard.exe.config XML file.

  5. As an administrator that haswith appropriate permissions to modify OU permissions, open the Intune Connector for Active Directory by navigatinggoing to Intune Connector for Active Directory > Intune Connector for Active Directory from the Start menu.

    Important

    If the administrator installing and configuring the Intune Connector for Active Directory doesn't have permissions to modify OU permissions, thenan administrator who has permissions to modify OU permissions needs to follow the section/steps in Increase the computer account limit in the Organizational Unit need to be followed instead by an administrator that does have permissions to modify OU permissions..

  6. UnderIn the Enrollment tab in the Intune Connector for Active Directory window, select Configure Managed Service Account.

  7. An A Managed Service Account with name "<MSA_name>" was successfully set up confirmation window appears. Select OK to close the window.

Use a custom Managed Service Account (optional)

- If using sMSA, the account can only be linked to a single machine.
- If using a gMSA, the server you’re installing the gMSA on needs to have access to the password.
How to set up
Disable OU updates

UsingIf you use your own MSA will disableMSA, the connector from makingdoesn't make any OU updates, regardless of any configured in OrganizationalUnitsUsedForOfflineDomainJoin.even if you configure OrganizationalUnitsUsedForOfflineDomainJoin. To prevent errors, disable OU updates by updating ODJConnectorEnrollmentWizard.exe.config. ItsThe default location is C:\Program Files\Microsoft Intune\ODJConnector\ODJConnectorEnrollmentWizard.

  1. In the appSettings section of the file, add the following line:

Legacy Connector

Important

The legacy Intune Connector for Active Directory is deprecated. These instructions assume that the legacy Intune Connector for Active Directory is already installed or is already downloaded. If you don't have the legacy Intune Connector for Active Directory installer isn't already downloaded,installer, you can download it can be downloaded from Intune Connector for Active Directory.

However, best practice is to download and install the updated Intune Connector for Active Directory. For more information, select the Updated Connector tab instead.

Before beginningyou begin the installation, make sure that you meet all of the Intune connector for Active Directory server requirements are met..

Disable Internet Explorer Enhanced Security Configuration

By defaultdefault, Windows Server has Internet Explorer Enhanced Security Configuration turned on. Internet Explorer Enhanced Security Configuration might cause problems signing in to the Intune Connector for Active Directory. SinceBecause Internet Explorer is deprecated and in most instances, not even installed on Windows Server, Microsoft recommends turning off Internet Explorer Enhanced Security Configuration. To turn off Internet Explorer Enhanced Security Configuration:

  1. Sign in to the server where you're installing the Intune Connector for Active Directory is being installed with an account that has local administrator rights and domain admin rights. DomainYou need domain admin rights are required so that the Intune Connector for Active Directory installer can properly create an MSA.

  2. Open Server Manager.

  3. In the left pane of Server Manager, select Local Server.

  4. In the right PROPERTIES pane of Server Manager, select the On or Off link next to IE Enhanced Security Configuration.

    Note

    If anyou want to install in a location other than the default of C:\Program Files\Microsoft Intune\ODJConnector is desired,, select Options and specify the desired install location.

  5. When the install completes,finishes, select Configure Now in the Intune Connector for Active Directory Setup installer window.

    Note

    If you accidentally select Close is accidentally selected or close the Intune Connector for Active Directory Setup installer window is accidentally closed,window, you can access the Intune Connector for Active Directory configuration can be accessed by selecting Intune Connector for Active Directory > Intune Connector for Active Directory from the Start menu.

Sign in to the legacy Intune Connector

  1. In the Intune Connector for Active Directory window, under the Enrollment tab,, select Sign In.

  2. UnderIn the Sign In tab, sign in with the credentials of an Intune administrator role. The user account must have an assigned Intune license. The sign in process might take a few minutes to complete.

    Note

    The account used to enroll the Intune Connector for Active Directory is only a temporary requirement at the time of installation. The account isn't used going forward after the server is enrolled.

  3. Once theAfter you sign in process is complete,in, a The Intune Connector for Active Directory successfully enrolled confirmation window appears. Select OK to close the window.

  4. The Enrollment tab shows Intune Connector for Active Directory is enrolled and the Sign In button is greyed out.

  5. Close the Intune Connector for Active Directory window.

Verify the legacy Intune Connector for Active Directory is active

After authenticating, the Intune Connector for Active Directory finishes installing. OnceAfter it finishes installing, verify that it's active in Intune by following these steps:

  1. Go to the Microsoft Intune admin center if it's still open. If the Add connector window is still displayed, close it.

    If the Microsoft Intune admin center isn't still open:

    1. Sign in to the Microsoft Intune admin center.
    2. In the Home screen, select Devicesin the left hand pane.pane, select Devices.
    3. In the Devices | Overview screen, under By platform, select Windows.
    4. In the Windows | Windows devices screen, under Device onboarding, select Enrollment.
    5. In the Windows | Windows enrollment screen, under Windows Autopilot, select Intune Connector for Active Directory.

  2. In the Intune Connector for Active Directory page, confirm that the server is displayed under Connector name and shows as Active under Status. If the server isn't displayed, select Refresh or navigate away from the page, and then navigatego back to the Intune Connector for Active Directory page.

Note

  • It can take several minutes for the newly enrolled server to appear in the Intune Connector for Active Directory page of the Microsoft Intune admin center. The enrolled server only appears if it can successfully communicate with the Intune service.
  • Inactive Intune Connectors for Active Directory still appear in the Intune Connector for Active Directory page and willare automatically be cleaned up after 30 days.

After the Intune Connector for Active Directory is installed, it will startstarts logging in the Event Viewer under the path Applications and Services Logs > Microsoft > Intune > ODJConnectorService. Under this path, you can find Admin and Operational logs can be found.logs.

This step is only needed under one of the following conditions:

The purpose of Intune Connector for Active Directory is to join computers to a domain and add them to an OU. For this reason, the Managed Service Account being used for the Intune Connector for Active Directory needs to have permissions to create computer accounts in the OU where the computers are joined to the on-premises domain.

With default permissions in Active Directory, domain joins by the Intune Connector for Active Directory might initially work without any permission modifications to the OU in Active Directory. However afterAfter MSA attempts to join more than 10 computers to the on-premises domain, it would stop working becausebecause, by default, Active Directory only allows any single account to join up to 10 computers to the on-premises domain.

The following users aren't restricted by the 10 computer domain join limitation:

  • The administrator installing the Intune Connector for Active Directory has the necessary permissions to set permissions on the OUs.
  • The administrator configuring the Intune Connector for Active Directory has the necessary permissions to set permissions on the OUs.

If the administrator installingwho installs or configuringconfigures the Intune Connector for Active Directory doesn't have the necessary permissions to set permissions on the OUs, then use the following steps need to be followed:steps:

  1. Sign in to a computer that has access to the Active Directory Users and Computers console with an account that ashas the necessary permissions to set permissions on OUs.

  2. Open the Active Directory Users and Computers console by running DSA.msc.

  3. Expand the desired domain and navigate to the organizational unit (OU) that computers are joiningjoin to during Windows Autopilot.

    Note

    TheYou specify the OU that computers join during the Windows Autopilot deployment is specified later duringin the Configure and assign domain join profile step.

  4. Right-click on the OU and select Properties.

    Note

    If computers are joining the default Computers container instead of an OU, right-click on the Computers container and select Delegate Control.

  5. In the OU Properties windows that opens,windows, select the Security tab.

  6. In the Security tab, select Advanced.

  7. In the Advanced Security Settings window, select Add.

  8. In the Permission Entry windows, next to Principal, select the Select a principal link.

  9. In the Select User, Computer, Service Account, or Group window, select the Object Types... button.

  10. In the Object Types window, select the Service Accounts check box,, and then select OK.

  11. In the Select User, Computer, Service Account, or Group window, under Enter the object name to select, enter the name of the MSA being used for the Intune Connector for Active Directory.

    Tip

    The MSA was created during the Install the Intune Connector for Active Directory step/section andsection. It has the name format of msaODJ#####, where ##### are five random characters. If you don't know the MSA name isn't known,name, follow these steps to find the MSA name:it:

    1. On the server runningthat runs the Intune Connector for Active Directory, right-click on the Start menu and then select Computer Management.
    2. In the Computer Management window, expand Services and Applications and then select Services.
    3. In the results pane, locate the service with the name Intune ODJConnector for Active Service. The name of the MSA is listed in the Log On As column.

  12. Select Check Names to validate the MSA name entry. OnceAfter the entry is validated,validates, select OK.

  13. In the Permission Entry windows, select the Applies to: drop-down menu and then select This object only.

  14. Under Permissions, unselectclear all items, and then only select theonly Create Computer objects check box..

  15. Select OK to close the Permission Entry window.

  16. In the Advanced Security Settings window, select either Apply or OK to apply the changes.

Legacy Connector

The purpose of Intune Connector for Active Directory is to join computers to a domain and add them to an OU. For this reason, the server running the Intune Connector for Active Directory needs to have permissions to create computer accounts in the OU where the computers are joined to the on-premises domain.

With default permissions in Active Directory, domain joins by the Intune Connector for Active Directory might initially work without any permission modifications to the OU in Active Directory. However afterAfter the server runningthat runs the Intune Connector for Active Directory attempts to join more than 10 computers to the on-premises domain, it would stopstops working because by default, Active Directory only allows any single account to join up to 10 computers to the on-premises domain.

The following users aren't restricted by the 10 computer domain join limitation:

  • Users in the Administrators or Domain Administrators groups -groups: in order to comply with the least privilege principles model, Microsoft doesn't recommend making the computer account runningthat runs the Intune Connector for Active Directory an administrator or domain administrator.
  • Users with delegated permissions on Organizational Unit (OUs) and containers in Active Directory to create computer accounts -accounts: this method is recommended sincebecause it follows the least privilege principles model.

To fix this limitation, the server running the Intune Connector for Active Directory needs the Create computer accounts permission in the Organizational Unit (OU) where the computers are joined to in the on-premises domain:domain

To increase the computer account limit in the Organizational Unit (OU) that computers are joining to during Windows Autopilot, follow these steps on a computer that has access to the Active Directory Users and Computers console:

  1. In the Welcome to the Delegation of Control Wizard window of the Delegation of Control Wizard, select Next.

  2. In the Users or Groups window, under Selected users and groups, select Add.

  3. Next to Select this object type: in the Select Users, Computers, or Groups window, select Object Types.

  4. In the Object Types window, select the Computers check box,, and then select OK. TheLeave the other items in this window can be left at their default.

  5. In the Select Users, Computers, or Groups window, under the Enter the object names to select box,, enter the name of the computer where you installed the Intune Connector for Active Directory was installed during the Install the Intune Connector for Active Directory step.

  6. Select Check Names to validate the entry. OnceAfter the entry is validated,validates, select OK.

  7. In the Users or Groups window, verify that the correct computer is shown under Selected users and groups:, and then select Next.

  8. In the Tasks to Delegate window, select Create a custom task to delegate, and then select Next.

  9. In the Active Directory Object Type window:

    1. Under Only the following objects in the folder, select Computer objects.
    2. Select the Create selected objects in this folder checkbox.
    3. Select Next.

  10. In the Permissions window, under Permissions:, select the Full Control check box,, and then select Next.

    Note

    After selecting the Full Control check box,checkbox, all other options under Permissions: are automatically selected. TheThis automatic selection of the checkboxes is normal and expected. Don't unselect any of the check boxescheckboxes after they're automatically selected.

  11. In the Completing the Delegation of Control Wizard window,, select Finish.

1. For **Group type**, select **Security**.
2. Enter a **Group name** and **Group description**.
3. Select a **Membership type**.

  1. If you select Dynamic Devices is selected for the membership type, in the Group pane, select Dynamic device members.

  2. SelectIn rule syntax select Edit in the Rule syntax box and enter one of the following code lines:

    • To create a group that includes all Windows Autopilot devices, enter:

      (device.devicePhysicalIDs -any _ -startsWith "[ZTDId]")

    • Intune's Group Tag field maps to the OrderID attribute on Microsoft Entra devices. To create a group that includes all of Windows Autopilot devices with a specific Group Tag (OrderID)(OrderID), enter:

      (device.devicePhysicalIds -any _ -eq "[OrderID]:179887111881")

    • To create a group that includes all Windows Autopilot devices with a specific Purchase Order ID, enter:

Register Windows Autopilot devices

Select one of the following waysmethods to enroll Windows Autopilot devices.

Register Windows Autopilot devices that are already enrolled

  1. Create a Windows Autopilot deployment profile with the setting Convert all targeted devices to Autopilot set to Yes.
  2. Assign the profile to a group that contains the members that needyou want to be automatically registeredregister with Windows Autopilot.

For more information, see Configure Windows Autopilot profiles.

Register Windows Autopilot devices that aren't enrolled

DevicesYou can manually register devices that aren't yet enrolled intoin Windows Autopilot can be manually registered.Autopilot. For more information, see Manual registration.

Register devices from an OEM

If you're purchasing new devices, some OEMs can register the devices on behalf of theyour organization. For more information, see OEM registration.

Display registered Windows Autopilot device

Before devices enroll in Intune, registered Windows Autopilot devices are displayedappear in three places (withplaces, with names set to their serial numbers):numbers:

  • The Windows Autopilot Devices pane in the Microsoft Intune admin center. Select Devices > By platform | Windows > Device onboarding | Enrollment. Under Windows Autopilot, select Devices.
  • The Devices | All devices pane in the Azure portal. Select Devices > All Devices.
  • The Autopilot pane in Microsoft 365 admin center. Select Devices > Autopilot.

After the Windows Autopilot devices are enrolled, the devices are displayedappear in four places:

Note

After devices are enrolled, the devices are still displayedappear in the Windows Autopilot Devices pane in the Microsoft Intune admin center and in the Autopilot pane in Microsoft 365 admin center, but those. Those objects are the Windows Autopilot registered objects.

A device object is pre-createdprecreated in Microsoft Entra ID oncewhen you register a device is registered in Windows Autopilot. When a device goes through a hybrid Microsoft Entra deployment, by design, another device object is created resulting in duplicate entries.

VPNs

  • SonicWall (Win32 client)
  • FortiClient VPN (Win32 client)

When usingIf you use VPNs, select Yes for the Skip AD connectivity check option in the Windows Autopilot deployment profile. Always-On VPNs shouldn't require this option since it connectsthey connect automatically.

Note

Note

Omission of a specific VPN client from this list doesn't automatically mean it's supported or that it works with Windows Autopilot. This list only lists the VPN clients that are known not to work with Windows Autopilot.

Create and assign a Windows Autopilot deployment profile

Use Windows Autopilot deployment profiles are used to configure the Windows Autopilot devices.

  1. Sign in to the Microsoft Intune admin center.

  2. In the Home screen,, select Devices in the left hand pane..

  3. In the Devices | Overview screen,, under By platform, select Windows.

  4. In the Windows | Windows devices screen,, under Device onboarding, select Enrollment.

  5. In the Windows | Windows enrollment screen,, under Windows Autopilot, select Deployment Profiles.

  6. In the Windows Autopilot deployment profiles screen,, select the Create Profile drop down menu and then select Windows PC.

  7. In the Create profile screen,, on the Basics page,, enter a Name and optional Description.

  8. If

    To automatically register all devices in the assigned groups should automatically register to Windows Autopilot, set Convert all targeted devices to Autopilot to Yes.

    All corporate corporate-owned, non-Windows Autopilot devices in assigned groups register with the Windows Autopilot deployment service. Personally owned devices aren't registered to Windows Autopilot. Allow 48 hours for the registration to be processed.process. When you unenroll and reset the device is unenrolled and reset,device, Windows Autopilot enrolls it again. After a device is registered in this way, disabling this setting or removing the profile assignment wondoesn't remove the device from the Windows Autopilot deployment service. Instead the devicesInstead, you need to be directly deleted.delete the devices. For more information, see Delete Windows Autopilot devices.

  9. Select Next.

  10. On the Out-of-box experience (OOBE) page,, for Deployment mode, select User-driven.

  11. In the Join to Microsoft Entra ID as box,, select Microsoft Entra hybrid joined.

  12. If deploying

    To deploy devices off of the organization's network by using VPN support, set the Skip Domain Connectivity Check option to Yes. For more information, see User-driven mode for Microsoft Entra hybrid join with VPN support.

  13. Configure the remaining options on the Out-of-box experience (OOBE) page as needed.

  14. Select Next.

  15. On the Scope tags page,, select scope tags for this profile.

  16. Select Next.

  17. On the Assignments page,, select Select groups to include > search for and select the device group > Select.

  18. Select Next > Create.

Note

Intune periodically checks for new devices in the assigned groups, and then beginbegins the process of assigning profiles to those devices. Due to several different factors involved in the process of Windows Autopilot profile assignment, an estimated time for the assignment can vary from scenario to scenario. These factors can include Microsoft Entra groups, membership rules, hash of a device, Intune and Windows Autopilot service, and internet connection. The assignment time varies depending on all the factors and variables involved in a specific scenario.

(Optional) Turn on the enrollment status page

  1. Sign in to the Microsoft Intune admin center.

  2. In the Home screen, select Devicesin the left hand pane.pane, select Devices.

  3. In the Devices | Overview screen, under By platform, select Windows.

  4. In the Windows | Windows devices screen, under Device onboarding, select Enrollment.

  5. In the Windows | Windows enrollment screen, under Windows Autopilot, select Enrollment Status Page.

    • Description: Enter a description for the profile.
    • Platform: Select Windows 10 and later.
    • Profile type: Select Templates, select the template name Domain Join, and select Create.

  6. Enter the Name and Description, and then select Next.

  7. Provide a Computer name prefix and Domain name.

  8. (Optional) Provide an Organizational unit (OU) in DN format. The options include:

    • Provide an OU in which control is delegated to the Windows device that is runningruns the Intune Connector for Active Directory.

    • Provide an OU in which control is delegated to the root computers in organization's on-premises Active Directory.

    • If this field is left blank, the computer object is created in the Active Directory default container. The default container is normally the CN=Computers container. For more information, see Redirect the users and computers containers in Active Directory domains.

    Valid examples:

    • OU=SubOU,OU=TopLevelOU,DC=contoso,DC=com
    • OU=Mine,DC=contoso,DC=com

    Invalid examples:

    • CN=Computers,DC=contoso,DC=com - a container. You can't be specified.specify a container. Instead, leave the value blank to use the default for the domain.
    • OU=Mine - the. The domain must be specified viaby using the DC= attributes.

    9. Make sure not toDon't use quotation marks around the value in Organizational unit.

  9. Select OK > Create. The profile is created and displayed in the list.

  10. Assign a device profile to the same group used at the step Create a device group. Different groups can be used if there's a need to join devices to different domains or OUs.

Uninstall the Intune Connector for Active Directory

The Intune Connector for Active Directory is installed locally on a computer via an executable file. IfYou install the Intune Connector for Active Directory needs to be uninstalled from a computer, it needs to also be done locally on a computer by using an executable file. To uninstall the computer. The Intune Connector for Active Directory from a computer, you also need to uninstall it locally on the computer. You can't be removedremove the Intune Connector for Active Directory through the Intune portal or through a graphGraph API call.

To uninstall the Intune Connector for Active Directory from the server, select the appropriate tab for the version of the Windows Server OS and then follow the steps:

Windows Server 2025

  1. Sign in to the computer hostingthat hosts the Intune Connector for Active Directory.

  2. Right-click on the Start menu and then select Settings > Apps > Installed apps.

    Or

    Select select the following Apps > Installed apps shortcut:

  3. In the Apps > Installed apps window, find Intune Connector for Active Directory.

  4. Next to Intune Connector for Active Directory, select ... > Uninstall, and then select the Uninstall button..

  5. The Intune Connector for Active Directory proceedsstarts to uninstall.

  6. In some cases, the Intune Connector for Active Directory might notdoesn't fully uninstall until the original Intune Connector for Active Directory installer ODJConnectorBootstrapper.exe is runruns again. To verify that the Intune Connector for Active Directory is fully uninstalled, run the ODJConnectorBootstrapper.exe installer again. If it prompts to Uninstall, select to uninstall it. Otherwise, close the ODJConnectorBootstrapper.exe installer.

    Note

    TheYou can download the legacy Intune Connector for Active Directory installer can be downloaded from the Intune Connector for Active Directory and should. Use it only be used for uninstalls. For new installs, use the updated Intune Connector for Active Directory.

Windows Server 2019/2022

  1. Sign in to the computer hostingthat hosts the Intune Connector for Active Directory.

  2. Right-click the Start menu and then select Settings > Apps.

    Or

    Select select the following Apps shortcut:

  3. Under Apps & features, find and select Intune Connector for Active Directory.

  4. Under Intune Connector for Active Directory, select the Uninstall button,, and then select the Uninstall button again.

  5. The Intune Connector for Active Directory proceeds to uninstall.starts uninstalling.

  6. In some cases, the Intune Connector for Active Directory might not fully uninstall until the original Intune Connector for Active Directory installer ODJConnectorBootstrapper.exe is runruns again. To verify that the Intune Connector for Active Directory is fully uninstalled, run the ODJConnectorBootstrapper.exe installer again. If it prompts to Uninstall, select to uninstall it. Otherwise, close the ODJConnectorBootstrapper.exe installer.

    Note

    TheYou can download the legacy Intune Connector for Active Directory installer can be downloaded from the Intune Connector for Active Directory and shouldpage. Use this installer only be used for uninstalls. For new installs, use the updated Intune Connector for Active Directory.

Windows Server 2016

  1. Sign in to the computer hosting the Intune Connector for Active Directory.

  2. Right-click the Start menu and then select Settings > System > Apps & features.

    Or

    Select select the following Apps shortcut:

  3. Under Apps & features, find and select Intune Connector for Active Directory.

  4. Under Intune Connector for Active Directory, select the Uninstall button,, and then select the Uninstall button again.

  5. The Intune Connector for Active Directory proceeds to uninstall.

  6. In some cases, the Intune Connector for Active Directory might not fully uninstall until the original Intune Connector for Active Directory installer ODJConnectorBootstrapper.exe is runruns again. To verify that the Intune Connector for Active Directory is fully uninstalled, run the ODJConnectorBootstrapper.exe installer again. If it prompts to Uninstall, select to uninstall it. Otherwise, close the ODJConnectorBootstrapper.exe installer.

    Note

    TheYou can download the legacy Intune Connector for Active Directory installer can be downloaded from the Intune Connector for Active Directory and shouldpage. Use it only be used for uninstalls. For new installs, use the updated Intune Connector for Active Directory.

\ No newline at end of file

Daily Intune.Admin.News

Get daily email updates

Get a concise summary of the latest Microsoft Intune updates delivered straight to your inbox.

Loading the secure signup form…