Security Policy Errors

Fix Azure AD Join Error During Windows Device Setup

Maira MehtabMaira Mehtab Nov 3, 2026 871 views

Question details

Users are encountering a "Something went wrong" error when attempting to join Windows devices to Azure AD, even though initial device registration succeeds.

How to Fix Azure AD Join Error During Windows Device Setup
Product
Azure AD (Microsoft Entra ID)
Device & OS
Windows
Scenario
Setting up new Windows devices and joining them to an organization's Microsoft 365 / Azure AD tenant.
Observed behavior
Azure AD device registration succeeds, but the actual Azure AD Join fails with a generic "Something went wrong" error message across multiple devices and user accounts.
Before you start

Ensure you have Global Administrator or Cloud Device Administrator access to the Microsoft Entra admin center, and verify that the affected users have active Microsoft 365 licenses assigned.

Solution 1Recommended

Verify and Update Azure AD Device Join Settings

The most common cause for this error is that the affected users are not permitted to join devices to the directory in the tenant's device settings.

By default, Azure AD (now Microsoft Entra ID) may restrict which users are allowed to join devices to the tenant. If a user is not included in the permitted group, the join process will fail during the Windows setup out-of-box experience (OOBE).

1
Access the Admin Center

Sign in to the Microsoft Entra admin center (or Azure portal) using an administrator account.

2
Navigate to Device Settings

In the left-hand navigation menu, expand 'Identity', go to 'Devices', and click on 'Device settings'.

3
Check Join Permissions

Locate the setting 'Users may join devices to Microsoft Entra'. Ensure this is set to 'All', or if set to 'Selected', verify that the affected users or their security groups are added to the list.

4
Verify Device Limits

On the same page, check the 'Maximum number of devices per user' setting. If affected users have already reached this limit, they will be blocked from joining new devices. Adjust the limit if necessary.

5
Save and Retry

Click 'Save' at the top of the page if you made any changes. Instruct the user to restart the Windows device and attempt the join process again.

Verify and Update Azure AD Device Join Settings
Changes take time to propagate: Tenant-level policy changes may take a few minutes to replicate across Azure AD services. Wait briefly before retrying the device setup.
Free Microsoft Office alternative

Boost Your Organization's Productivity with WPS Office

While resolving Microsoft tenant and Windows deployment issues, you can provide your users with a powerful, lightweight, and highly compatible office suite. WPS Office ensures seamless document collaboration without the heavy licensing costs of Microsoft Office.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Lightweight installation package, ideal for newly provisioned Windows devices.Familiar user interface with zero learning curve for enterprise teams.Built-in PDF editing, document conversion, and cloud collaboration tools.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Azure AD device registration succeed but Azure AD join fail?

Device registration simply records the device in the directory for Bring Your Own Device (BYOD) scenarios, which generally has looser restrictions. Azure AD Join bonds the device's local identity to the organization's tenant, which requires specific 'Join' permissions enabled under the Entra ID device settings.

Does reaching the maximum device limit cause the 'Something went wrong' error?

Yes. If an administrator has set a limit on how many devices a single user can join (for example, 20 devices) and the user reaches that quota, subsequent attempts to join new Windows devices will fail with a generic error.

How can I view detailed error codes for Azure AD Join failures?

On the affected Windows device, you can press Shift + F10 during the setup screen to open Command Prompt, then open the Event Viewer (eventvwr.msc). Navigate to Applications and Services Logs > Microsoft > Windows > User Device Registration > Admin to view specific error codes.