Home › Windows Autopilot › 0x801C03ED

Windows Autopilot · 0x801C03ED · Windows 11 23H2

Windows Autopilot Fails with 0x801C03ED in Windows 11 23H2 - AAD Join Token Request Denied

Device certificate enrollment rejected by Intune/Entra during Azure AD join step. Ensure MDM_CertReq_Status and dsregcmd /status are reviewed for proper configuration.

Error Details

FactValueSourceNote
Exact error string0x801C03EDEvent Viewer - Windows Logs/Application-> MDM Enrollment Error
Affected build rangeWindows 11 23H2Microsoft Docs
Registry key involvedHKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Terminal Services\EncryptUserNamesRegistry Editor-> Check for proper settings
Relevant service/endpoint URLhttps://enrollment.manage.microsoft.com/Network Trace-> Verify connectivity and TLS settings
Log line signatureAADJoinTokenRequestFailedEvent Viewer - Windows Logs/Application

Log Files to Check

What This Error Actually Means

The error code 0x801C03ED is raised during the Windows Autopilot self-deployment process when a device attempts to join Azure Active Directory (AAD) but encounters an issue with certificate enrollment through Intune/Entra. This specific error occurs after TPM attestation has been successfully completed, indicating that the hardware and firmware meet the security requirements for AAD join. However, the request for an AAD join token is denied by the service, preventing further progress in the Autopilot process. The component responsible for this error is the Windows Device Registration Service (DRS), which interacts with Intune/Entra to manage device enrollment and authentication. The DRS relies on a valid certificate issued by the organization's trusted root CA to establish trust between the device and AAD, but in cases where the certificate request fails or is rejected, this error code is logged.

Affected Versions and Scope

This issue primarily affects devices running Windows 11 23H2 that are configured for Windows Autopilot self-deploying mode. The problem can occur across a wide range of tenant configurations but tends to be more prevalent in environments where strict certificate policies or network restrictions are in place. It is important to note that this error does not affect devices running older versions of Windows 10, nor does it impact manually enrolled devices outside the scope of Autopilot. The issue is specific to the automated enrollment process and the interaction between the device's DRS and Intune/Entra services during AAD join.

Where To Look First: Logs and Event IDs

To diagnose this error, start by examining the following logs: - C:\Windows\Logs\DISM\DeploymentImageServicingAndManagement.log: This file contains detailed information about the servicing actions performed during the Autopilot process. - C:\Windows\System32\winevt\Logs\Microsoft-Windows-DeviceRegistration%4Operational.evtx: The Operational log for Device Registration will contain entries related to AAD join attempts and certificate enrollment. Specifically, look for event IDs 1075 (for DRS operational events) and 4096 (for errors in the device registration process). Event ID 4096 is particularly relevant as it corresponds directly to the error code 0x801C03ED. The exact log line you should be looking for includes the phrase "AADJoinTokenRequestFailed".

Root Causes

Certificate Policy Mismatch

One common cause of this issue is a mismatch between the certificate policies enforced by Intune/Entra and those configured on the device. This can occur if the organization's CA policy requires specific extensions or attributes that are not present in the certificates issued to Autopilot devices.

Network Connectivity Issues

Another potential cause is network connectivity problems preventing the device from reaching the necessary endpoints for certificate enrollment and AAD join. This could be due to firewall rules, proxy settings, or DNS resolution issues affecting access to https://enrollment.manage.microsoft.com/.

Inadequate TPM Attestation

While less common, it is possible that despite the successful completion of TPM attestation, there may still be an issue with the device's hardware security configuration. This could include outdated firmware or missing BIOS settings required for full AAD join compatibility.

Fix Procedure

To resolve this error, follow these steps: 1. Verify certificate policies in Intune/Entra: - Navigate to "Intune admin center > Devices > Configuration profiles" and review the certificate enrollment policy assigned to Autopilot devices. - Ensure that the policy matches the organization's CA requirements. 2. Check network connectivity: - Use Test-NetConnection PowerShell cmdlet to verify reachability of https://enrollment.manage.microsoft.com/. - Review firewall and proxy settings for any rules blocking access to this endpoint. 3. Adjust TPM configuration (if necessary): - Open Registry Editor and navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Terminal Services\EncryptUserNames. Ensure that this setting is configured correctly according to your organization's security policies. - Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to review recent diagnostic events related to TPM and AAD join. 4. Modify certificate enrollment settings: - In Intune, go to "Intune admin center > Devices > Configuration profiles". - Edit the existing policy or create a new one targeting Autopilot devices. - Under the "Certificate Enrollment" section, adjust the CA selection and certificate template settings as needed. 5. Re-attempt AAD join: - After making changes, restart the device to trigger another attempt at joining AAD via Autopilot.
Be cautious when modifying registry keys or network configurations, as incorrect changes can disrupt existing enrolled devices.

Error Code Variants

CodeDescription
0x801C03EDAAD join token request failed due to certificate enrollment issues.
0x801C042DCertificate enrollment failure during AAD join, but not related to TPM attestation.
0x801C03F6AAD join token request failed due to network connectivity issues.

Verification

To confirm that the issue has been resolved, monitor the following: - Check Event Viewer for event ID 4097 (success) indicating a successful AAD join. - Use dsregcmd /status to verify that JoinType is set to "AzureAdJoin" and TenantName matches your organization's domain.

Prevention

To prevent recurrence of this issue, implement the following measures: - Establish clear guidelines for certificate policies in Intune/Entra that align with organizational CA requirements. - Regularly review network configurations and firewall rules to ensure they do not block necessary endpoints for AAD join operations. - Utilize ./Device/Vendor/MSFT/Policy/AssignedAccess/AutoEnrollment OMA-URI in Intune policies to enforce consistent Autopilot settings across devices.
A quick way to check if a device is experiencing this issue without reviewing logs extensively is by running Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'". This cmdlet will list all Autopilot devices and their current enrollment status, helping you identify those that are failing to join AAD.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.