Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Something went wrong. Try again. Code: 0x801C044D | Windows Hello for Business provisioning screen | -> |
| OS build affected | Windows 10 / Windows 11 | Microsoft documentation | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\HybridAzureADJoin | Registry Editor | -> |
| Relevant service/endpoint URL | https://login.microsoftonline.com | Network logs | -> |
| Log line signature | NGC_E_DEVICE_NOT_PRESENT_IN_TENANT | Event Viewer logs | -> |
Log Files to Check
Microsoft-Windows-User Device Registration/Admindsreg.txt (generated by dsregcmd /status)
What This Error Actually Means
The error code0x801C044D (NGC_E_DEVICE_NOT_PRESENT_IN_TENANT) indicates that the device attempting Windows Hello for Business (WHfB) provisioning is not recognized as Azure AD joined or Hybrid-joined at the time of provisioning. This error originates from the Microsoft.Ngc.DeviceRegistration component, which manages device registration and authentication with Azure Active Directory (Azure AD). The error occurs because the device's identity is missing in the tenant directory, preventing WHfB from completing its provisioning process.
Affected Versions and Scope
This issue affects Windows 10 and Windows 11 devices enrolled in Azure AD or Hybrid Azure AD environments. It specifically impacts devices that have not completed the synchronization process between on-premises Active Directory (AD) and Azure AD via Azure AD Connect. Devices using other authentication methods, such as Microsoft Account or local accounts, are not affected.Where To Look First: Logs and Event IDs
To diagnose this issue, examine the following logs: 1. **Event Viewer**: - Navigate toApplications and Services Logs > Microsoft > Windows > User Device Registration > Admin.
- Search for Event ID 360 (NGC provisioning failure) and Event ID 304 with sub-error 0x801C044D.
2. **Azure AD Operational Logs**:
- Go to Applications and Services Logs > Microsoft > Windows > AAD > Operational.
- Look for Event ID 1098 (Device not found in tenant) around the time of WHfB provisioning.
3. **Device Registration Log**:
- Run an elevated Command Prompt and execute dsregcmd /status > dsreg.txt.
- Open dsreg.txt to review sections like "Device State," "SSO State," and "Ngc Prerequisite Check."
Root Causes
1. Hybrid Azure AD Join Synchronization Delay
The device may have joined the on-premises AD, but Azure AD Connect (AADSync) has not yet synchronized this information to Entra ID. This delay can take 30 minutes to several hours.2. Incorrect UserCertificate Attribute in Hybrid Join
In SCP-based hybrid joins, the device'sUserCertificate attribute may not have been issued correctly by Active Directory Certificate Services (AD CS), preventing Azure AD from recognizing the device.
3. Premature WHfB Provisioning Attempt
The device might be attempting WHfB provisioning before completing Hybrid Join synchronization, which typically takes 30 minutes to 2 hours.4. Network Connectivity or Sync Issues
If the Azure AD Connect server is offline, paused, or experiencing network issues, synchronization may fail, leaving the device unregistered in Entra ID.Fix Procedure
- Verify Device State:
Open an elevated Command Prompt and run:
dsregcmd /statusCheck "Device State" forAzureAdJoined = YESand a populatedDeviceId. Under "Ngc Prerequisite Check," ensure all items (AadJoined, MdmEnrolled, NgcDpApiOk) showYES. - Force Hybrid Join Sync:
On the Azure AD Connect server:
- Open Azure AD Connect and navigate to Synchronization Service Manager.
- Execute a Delta Sync using PowerShell:
Start-ADSyncSyncCycle -PolicyType DeltaAfter syncing, rundsregcmd /debugon the device and wait 30 minutes. Recheck withdsregcmd /status. - Validate Device in Entra ID:
Navigate to the Entra admin center:
Identity > Devices > All devices. Search for the device name fromdsreg.txt. If absent, AD sync hasn't propagated. - Check AAD Connect Sync Status:
Use Azure AD Connect Health or PowerShell:
Get-ADSyncConnectorStatisticsEnsure the last sync time is within 30 minutes. - Re-trigger WHfB Provisioning: Sign out and back in, or lock and unlock the device. WHfB provisioning re-triggers at next sign-in after Azure AD sync completes.
Error Code Variants
| Code | Description |
|---|---|
| 0x801C044D | Device not present in tenant (NGC_E_DEVICE_NOT_PRESENT_IN_TENANT) |
| 0x801C0450 | Device registration failed due to invalid credentials (NGC_E_REGISTRATION_FAILED) |
| 0x801C0453 | Device not enrolled in MDM (NGC_E_DEVICE_NOT_ENROLLED_IN_MDM) |
Verification
After applying fixes: - The device should appear in Entra ID underIdentity > Devices > All devices.
- Event Viewer logs should show successful provisioning without error codes.
- Running dsregcmd /status should confirm all prerequisites as YES.
Prevention
To prevent recurrence: - Monitor Azure AD Connect sync schedules and ensure they run at least every 30 minutes. - Ensure devices have network access tohttps://login.microsoftonline.com during initial sign-in.
- Use Intune policies to enforce re-provisioning after device restarts or sync events.
Warning: Forcing a Delta Sync on Azure AD Connect can impact performance. Only perform this step if you're certain synchronization is delayed and no other sync activities are running.
Tip: Use the OMA-URI to check device registration status via Intune or PowerShell:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"