Windows out-of-box enrollment with Hexnode using Microsoft Entra ID and AutopilotSolved

Hi @boris,

For a true Windows out-of-box enrollment experience with Hexnode, Microsoft Entra ID integration alone is not enough. The supported flow relies on Windows Autopilot together with Microsoft Entra ID.

In this setup:

1. The Windows device must be registered with your organization’s Windows Autopilot service.
2. The device must be assigned to the appropriate Autopilot deployment profile.
3. Hexnode must be configured as the MDM authority for enrollment.
4. The end user must sign in during the Windows out-of-box experience using valid Microsoft Entra credentials.
5. The enrolling user must have the required Microsoft Entra ID licensing, such as Entra ID P1, for the Autopilot/MDM enrollment flow.

Once these conditions are met, the device can be directed to enroll into Hexnode during initial setup. The user will still authenticate with Microsoft credentials, but they do not need to manually download or run the Hexnode installer.

Regards,
Sienna Carter
Hexnode UEM

That helps, but we were hoping to avoid Autopilot completely. If the reseller links the device to our Entra tenant, would that not be enough to trigger Hexnode enrollment automatically?

Hi @boris,

Linking the device to the Microsoft Entra tenant by itself does not provide the same zero-touch Windows setup experience.

Hexnode’s Microsoft Entra ID integration is used for identity-related functions such as user/group sync and authentication. The Windows out-of-box provisioning mechanism is handled by Windows Autopilot. Autopilot is what tells the new Windows device which organization it belongs to and which MDM enrollment flow to follow during first setup.

Without Autopilot, the device would generally need to be enrolled after setup using another supported Windows enrollment method, which involves some level of user or admin action.

Regards,
Sienna Carter
Hexnode UEM