A cloud-based identity and access management service for securing user authentication and resource access
Hello Doddabasappa K,
Greetings! Thanks for raising this question in the Q&A forum
The screenshot appears to show a Windows Access work or school Microsoft Entra join failure, rather than adding a DNS domain. Error 0x80190190 is a generic HTTP 400 response, so the underlying reason must be obtained from the device-registration logs.
Confirm the Windows edition
Microsoft Entra join is supported on Windows 10/11 Pro, Enterprise, and Education, but not Home editions. Check Settings > System > About > Windows specifications. See Microsoft Entra joined devices.
Use the correct join option and identity
Navigate to:
Settings > Accounts > Access work or school > Connect > Join this device to Microsoft Entra ID
Sign in with a member work or school account from the target tenant. Do not use a personal Microsoft account or an account belonging to another tenant. The documented enrollment flow is available at MDM enrollment of Windows devices.
Check the tenant’s device settings
In the Microsoft Entra admin center, open Entra ID > Devices > Overview > Device settings and verify:
Users may join devices to Microsoft Entra ID includes this user.
The user has not reached **Maximum number of devices**.
The account is enabled and is a member of the tenant.
Conditional Access does not block device registration from this location or device.
See [Manage device identities in Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity/devices/manage-device-identities).
**Check Intune enrollment when enabled**
If the tenant automatically enrolls joined devices into Intune, verify that the user has an appropriate Intune license, is included in the MDM user scope, and is not blocked by a Windows enrollment restriction. Otherwise, authentication can succeed while the management-enrollment portion fails.
**Inspect the current device state**
Open Command Prompt and run:
```
dsregcmd /status
```
Review `AzureAdJoined`, `DomainJoined`, `WorkplaceJoined`, `TenantId`, and the diagnostic section. If the device is already joined or registered, determine its existing ownership before disconnecting it. Do not run `dsregcmd /leave` until the current state is understood.
**Collect the actual server error**
Open Event Viewer and navigate to:
`Applications and Services Logs > Microsoft > Windows > User Device Registration > Admin`
Review events recorded around `2026-09-03 09:49:40 UTC`. If Intune enrollment was triggered, also check:
`Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider > Admin`
Microsoft’s [Windows device troubleshooting guidance](https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-device-windows-joined) explains how to collect and analyze these logs.
**Escalate with the diagnostic evidence**
If the settings are correct, open a Microsoft Entra support request and include error `0x80190190`, timestamp `2026-09-03T09:49:40Z`, Windows edition and build, tenant ID, the relevant Event Viewer event, server message, request ID, and sanitized `dsregcmd /status` output. Avoid posting the user principal name, device ID, or tenant-specific identifiers publicly.
If this answer helps you kindly accept the answer which will help others who have similar questions.
Best Regards,
Jerald Felix.