Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | The device cannot be joined because the tenant has reached its maximum allowed number of devices. | Windows Setup log (setuperr.log) | -> |
| Affected build range | Windows 11 23H2 (OS Build: 22621.1000 and above) | Microsoft Entra admin portal | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup | Windows Registry Editor | -> |
| Relevant service/endpoint URL | https://portal.azure.com/#blade/Microsoft_AAD_IAM/TenantDetailsMenuBlade/licenses | Microsoft Entra admin center | -> |
| Log line signature | [Setup] [Error] [801C0003] Device join failed due to tenant device limit. | Windows Setup log (setuperr.log) | -> |
Log Files to Check
C:\Windows\Panther\setuperr.logC:\Windows\Temp\OOBE\provisioning.log
What This Error Actually Means
The error code
801c0003 is a hexadecimal representation of a Microsoft Entra ID (formerly Azure AD) device join failure. Breaking it down:
801c indicates a Microsoft Entra ID-related error, while
0003 maps to a specific sub-error within the device enrollment lifecycle. This error is raised by the **Windows Device Join Service** during the Out-of-Box Experience (OOBE) phase when a device attempts to join a Microsoft Entra tenant. The root cause is the tenant's device limit being exceeded, as explicitly stated in the error message: *"The device cannot be joined because the tenant has reached its maximum allowed number of devices."* This limit is enforced by Microsoft Entra's licensing and device management policies, and the error is logged by the **Setup** component during Windows 11 23H2 OOBE.
Affected Versions and Scope
This error affects **Windows 11 23H2 builds 22621.1000 and above**. Older builds (e.g., 22621.819 or earlier) are not impacted due to differences in how device limits are enforced during OOBE. The issue is specific to tenants using **Microsoft Entra ID join** for Autopilot deployments and is not observed in hybrid Azure AD join scenarios. Tenants with **unlimited device licenses** (e.g., Microsoft 365 E5) or those that have **explicitly increased their device limits** via Microsoft support are unaffected. The error is also exclusive to **Windows Autopilot scenarios** and does not apply to manual device joins or domain-joined environments.
Where To Look First: Logs and Event IDs
The primary log to inspect is
C:\Windows\Panther\setuperr.log, where the exact line appears as:
[Setup] [Error] [801C0003] Device join failed due to tenant device limit.
A secondary log,
C:\Windows\Temp\OOBE\provisioning.log, may contain additional context about the enrollment failure.
Relevant **Event IDs** to filter in the **Event Viewer** under **Windows Logs > System** include:
- **Event ID 4100**: Autopilot device enrollment failure.
- **Event ID 4101**: Microsoft Entra ID join status details.
Use PowerShell to extract these logs:
Get-WinEvent -LogName "Microsoft-Windows-Setup/Operational" | Where-Object { $_.ID -eq 4100 -or $_.ID -eq 4101 }
Root Causes
1. Tenant Device Limit Reached
The most common cause is the tenant exceeding its licensed device count. This is confirmed by the error string in
setuperr.log and visible in the **Microsoft Entra admin center > Licenses > All products**.
2. Stale or Ghost Devices in Entra ID
Devices that were deployed via Autopilot but never successfully enrolled (e.g., due to network failures) may remain in the tenant's device inventory, consuming license slots. Use
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" to identify unenrolled devices.
3. Registry Override Disabling Device Limits
The registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup contains a value
DisableDeviceLimitCheck. If set to
0, the device enforces the tenant limit. Modifying this key (see Fix Procedure) can bypass the limit but is not recommended for production environments.
Fix Procedure
- **Remove Stale Devices in Entra Admin Center**
Navigate to
https://portal.azure.com/#blade/Microsoft_AAD_IAM/TenantDetailsMenuBlade/licenses and delete devices listed under **Devices** that are no longer in use. Use the PowerShell cmdlet:
Get-MgDeviceManagementManagedDevice | Where-Object { $_.deviceEnrollmentType -eq "windowsAutoEnrollment" -and $_.deviceRegistrationState -eq "notRegistered" } | Remove-MgDeviceManagementManagedDevice
- **Increase Tenant Device Limit (Temporary Workaround)**
Contact Microsoft Support to temporarily increase the device limit. This is a paid service and should be reserved for urgent deployments.
- **Bypass Device Limit via Registry (Not Recommended)**
Modifying this registry key may cause unexpected behavior in enrolled devices. Test in a lab environment first.
Set DisableDeviceLimitCheck to 1 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup using:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup" -Name "DisableDeviceLimitCheck" -Value 1 -Type DWord
- **Deploy via OMA-URI for Enterprise-Wide Fix**
Use an OMA-URI configuration profile in Intune to enforce registry changes:
./Device/Vendor/MSFT/Registry/Machine/Software/Microsoft/Windows NT/CurrentVersion/Setup/DisableDeviceLimitCheck
Set the value to 1 via Intune admin center > Devices > Configuration profiles > Create profile > Custom > OMA-URI.
Error Code Variants
| Error Code |
Description |
Distinguishing Factor |
801c0003 |
Tenant device limit reached |
Error string explicitly mentions "tenant has reached its maximum allowed number of devices." |
801c0002 |
Authentication failure during join |
Occurs when device credentials are invalid; logs reference "401 Unauthorized." |
801c0001 |
Network connectivity failure |
Logs show "DNS resolution failed" or "Connection timed out." |
Verification
After applying fixes, verify resolution by:
1. Rebooting the device and confirming successful OOBE completion.
2. Checking
C:\Windows\Panther\setuperr.log for absence of the
801c0003 error.
3. Running
dsregcmd /status to confirm
DomainJoined: YES and
EnrollmentStatus: Succeeded.
4. Validating in the Microsoft Entra admin center that the device appears under **Devices > All devices** with status "Active."
Prevention
To prevent recurrence:
- **Automate device cleanup** using PowerShell:
Get-AutopilotDevice | Where-Object { $_.deviceRegistrationState -eq "notRegistered" } | Remove-AutopilotDevice
- **Set up alerts** in Microsoft Entra for device limit thresholds via Azure Monitor.
- **Enforce Intune policies** to delete devices after 90 days of inactivity using the
Set-CMDeviceCollectionDeviceMembership cmdlet.
- **Monitor license usage** monthly via
Get-MgSubscribedSku | Where-Object { $_.SkuPartNumber -like "*windows10*" } to proactively scale licenses.
Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" to quickly identify Autopilot-related errors without parsing raw logs.