A cloud-based identity and access management service for securing user authentication and resource access
Use the built-in troubleshooting tools and logs to identify why the join flow is closing and not completing.
- Run the Windows device troubleshooter for Entra ID
- Sign in to the Microsoft Entra admin center with at least the Reports Reader role.
- Go to Entra ID → Devices → All devices → Diagnose and solve problems.
- Under Windows 10+ related issue, select Troubleshoot.
- Select instructions and follow the steps to download and run the troubleshooter on the Windows 11 device.
- Collect and zip the
authlogsfolder as instructed and upload it back in the same Diagnose and solve problems pane. - Review the suggested next steps provided by the troubleshooter (it will surface configuration or connectivity issues that cause silent failures).
- Check for hybrid-join or device-object issues
If the device is domain-joined or intended to be hybrid joined, verify there is no hybrid-join misconfiguration or device-object problem that could cause the join UI to fail:
- Confirm the device has line-of-sight to a domain controller if hybrid join is in use.
- Ensure the service connection point (SCP) is correctly configured with the right tenant ID and verified domain if hybrid join is configured.
- If the device object was deleted and the device is already Entra-joined, run
dsregcmd /forcerecoveryfrom an elevated PowerShell session and sign in again when prompted.
- Collect deeper logs if the issue persists
If the basic troubleshooter does not resolve the issue, collect detailed auth logs for support:
- Download the Auth.zip from https://aka.ms/authscripts.
- Extract to a folder (for example,
C:\temp). - Open an elevated PowerShell session and run:
.\start-auth.ps1 -vAuth -accepteula - Switch to a normal user session, reproduce the Join this device to Microsoft Entra ID flow until it fails/vanishes.
- Switch back to the admin session and run:
.\stop-auth.ps1 - Zip the generated
Authlogsfolder and provide it to Microsoft Support for analysis.
These steps will surface any hidden error codes (network, authentication, or configuration) that are causing the join window to close without an on-screen error.
References: