During the Intune Autopilot process, the enrollment profile is not loading as expected. Instead, the system is bypassing this step and going directly to the Hello for Business setup. Could you please advise on how to resolve this issue?

Question

During the Intune Autopilot process, the enrollment profile is not loading as expected. Instead, the system is bypassing this step and going directly to the Hello for Business setup. Could someone please advise on how to resolve this issue or what further could be checked?

Here are the checks and steps I have already performed:

1. Verified that the enrollment profile is correctly assigned.
2. Removed the device from Autopilot enrollment completely, cleared the device from Azure, and re-attempted the process, but the issue persists.
3. Confirmed that the deployment profile is being picked up, as evidenced by the custom hostname being correctly set by the device.

Despite these steps, the following issues remain:

• The step for configuring applications does not appear.
• Although the device gets Azure joined, it shows the error: "deviceauthstatus failed 0xd000023c."
• The device does not appear in the Intune list of devices.

Answer 1

2 things -

1. Are you expecting ESP to load? If yes, then is it setup and assigned?
2. If the device is not enrolling in Intune, then have you checked if the MDM enrollment policy is assigned or not? Also, any device or platform restrictions configured that may interfere with the Intune enrollment process?

Answer 2

@Shawn T Daniel,Thanks for posting in Q&A.

From your description, I know you want to do Autopilot enrollment, but the profile did not load as expected.

To clarify this issue, please check the following.

1.Check whether the device meet the requirements below.

https://learn.microsoft.com/en-us/autopilot/requirements?tabs=configuration

2.Check whether Autopilot profile has been successfully downloaded in the targeted device.

https://www.techtarget.com/searchenterprisedesktop/tip/2-methods-to-tackle-Windows-Autopilot-troubleshooting

Non-official, just for reference

3.Follow the link below to find if there exist some error in IME log that may block applications downloading.

https://www.niallbrady.com/2020/06/10/troubleshooting-application-deployment-failures-during-the-enrollment-status-page-for-windows-autopilot/

Non-official, just for reference

4.As for the error code, it may relate to Hybrid AAD joined and means device is either disabled or deleted. Could you please share with us the Autopilot deployment profile settings and what kind of enrollment you are using? Azure AD join or Hybrid Azure Ad join?

If it is Hybrid Azure Ad join, you can try to delete the device both in Azure Ad and Intune and some registry key in targeted device, then re-enroll again.

https://www.itpromentor.com/troubleshooting-weird-azure-ad-join-issues/

https://ulyssesneves.com/2022/06/02/device-registration-investigating-error-message-deviceauthstatus-failed-device-is-either-disabled-or-deleted/

Non-official, just for reference

5.You can configure ESP stage during Autopilot process to get more useful information.

Please check above information, if there is any update, feel free to let me know.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.