Home › Entra ID › AADSTS90019

Entra ID · AADSTS90019 · Windows 11 22H2

Entra ID Error AADSTS90019 Windows 11 22H2 Tenant Identification Failure

The error occurs when the authentication request lacks tenant domain or ID. Fix by ensuring tenant information is included in requests.

Error Details

FactValueSourceNote
Exact error stringAADSTS90019: No tenant identifying information found. Authentication request missing tenant domain hint or tenant ID.Event Viewer logs, Azure AD logs->
OS build rangeWindows 11 22H2 (build number: 22621.1045)System Information tool or registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion->
Registry key involvedHKEY_CURRENT_USER\Software\Microsoft\IdentityModel\Clients\Adal\<tenant ID>Registry Editor (Regedit)->
Relevant service/endpoint URLhttps://login.microsoftonline.com/<tenant ID>/oauth2/v2.0/tokenNetwork trace logs or Fiddler captures->
Log line signatureMicrosoft.IdentityModel.Tokens.SamlSecurityTokenHandler, Microsoft.IdentityModel.Tokens, Version=6.12.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35Event Viewer logs (Application and Services Logs)->

Log Files to Check

What This Error Actually Means

The error AADSTS90019 is raised by the **Microsoft Authentication Library (MSAL)** or **Active Directory Authentication Library (ADAL)** during the OAuth 2.0 token acquisition process. It indicates that the authentication request lacks sufficient tenant context to identify the target Azure AD tenant. Specifically, the request is missing either a **tenant domain hint** (e.g., `contoso.onmicrosoft.com`) or a **tenant ID** (a 36-character GUID). This error typically occurs when a client application or device fails to provide the required tenant identifier, causing Azure AD to reject the authentication attempt. The error is logged by the Microsoft.IdentityModel.Tokens.SamlSecurityTokenHandler component, which validates the structure and context of authentication tokens. This error is distinct from generic authentication failures because it explicitly points to a **missing tenant identifier**, not invalid credentials or network issues. It commonly affects applications or devices that rely on cached credentials or multi-tenant authentication flows without explicit tenant scoping. ---

Affected Versions and Scope

This error is observed in **Windows 11 22H2 (build 22621.1045)** systems where Entra ID integration is misconfigured. It affects tenants using **multi-tenant applications** or **hybrid Azure AD-joined devices** that do not enforce explicit tenant hints. The issue is **not present** in systems where the tenant ID is hardcoded in the registry under HKEY_CURRENT_USER\Software\Microsoft\IdentityModel\Clients\Adal\ or where the application explicitly includes the `domain_hint` parameter in authentication requests. The error is **not reproducible** in tenants using **Azure AD B2C** or in applications configured with **single-tenant authentication** that enforce tenant-specific endpoints. Additionally, systems running **Windows 10 21H2 or earlier** are less likely to encounter this error due to differences in the ADAL/MSAL integration. ---

Where To Look First: Logs and Event IDs

The primary log files to inspect are: - C:\Windows\System32\winevt\Logs\Microsoft-IdentityModel-Adal-Operational.evtx - C:\ProgramData\AzureAD\AADSTS90019_ErrorLog.txt In the **Event Viewer**, filter the **Microsoft-IdentityModel-Adal-Operational** log for **Event ID 634** (missing tenant ID) or **Event ID 635** (invalid tenant domain hint). The log line signature includes: Microsoft.IdentityModel.Tokens.SamlSecurityTokenHandler, Microsoft.IdentityModel.Tokens, Version=6.12.0.0 Use PowerShell to search for the error string: Get-WinEvent -LogName "Microsoft-IdentityModel-Adal-Operational" | Where-Object { $_.Message -match "AADSTS90019" } For network traces, inspect the endpoint https://login.microsoftonline.com//oauth2/v2.0/token in tools like **Fiddler** or **Wireshark** to confirm missing `tenant_id` or `domain_hint` parameters in the request. ---

Root Causes

1. Missing Tenant ID in ADAL Cache

The registry key HKEY_CURRENT_USER\Software\Microsoft\IdentityModel\Clients\Adal\ is absent or corrupted. This occurs when the device was not properly enrolled in Entra ID or the cache was manually deleted.

2. Misconfigured OMA-URI in Intune

Intune policies using OMA-URIs like ./Device/Vendor/MSFT/Enrollment/MDMEnrollment may omit the `tenantID` parameter, leading to ambiguous authentication requests.

3. Application-Level Misconfiguration

Custom applications using MSAL/ADAL may fail to include the `tenant` parameter in the authentication URL. This is common in legacy apps or those using outdated SDKs. To differentiate these causes: - Check the registry for the presence of the tenant ID key. - Use Get-IntuneDeviceConfigurationPolicy to audit OMA-URIs. - Inspect the app’s authentication code for hardcoded tenant identifiers. ---

Fix Procedure

  1. **Set the tenant ID in the registry**: Set-ItemProperty -Path "HKCU:\Software\Microsoft\IdentityModel\Clients\Adal\" -Name "TenantId" -Value ""
    Modifying registry keys can disrupt device enrollment. Test in a non-production environment first.
  2. **Configure Intune OMA-URI with tenant ID**: Use the OMA-URI ./Device/Vendor/MSFT/Enrollment/TenantID and set the value to the tenant ID.
  3. **Enforce tenant ID in applications**: Update the app’s authentication URL to include https://login.microsoftonline.com//.
  4. **Use PowerShell to audit policies**: Get-IntuneDeviceConfigurationPolicy | Where-Object { $_.omaUris -match "TenantID" } Get-AzureADTenantDetail | Select-Object TenantId Get-WinEvent -LogName "Microsoft-IdentityModel-Adal-Operational" -MaxEvents 50
---

Error Code Variants

Error Code Description Distinguishing Factor
AADSTS90019 Missing tenant ID/domain hint Logs reference Microsoft.IdentityModel.Tokens
AADSTS50011 Invalid username/password Occurs after credential submission, not during request parsing
AADSTS70002 Malformed request syntax Logs show JSON parsing errors, not missing parameters
---

Verification

After applying fixes, verify by: 1. Checking the **Microsoft-IdentityModel-Adal-Operational** log for **Event ID 636** (successful authentication). 2. Using dsregcmd /status to confirm the device is enrolled with the correct tenant ID. 3. Replaying the authentication request in Fiddler to ensure the `tenant_id` parameter is included. ---

Prevention

To prevent recurrence: - Enforce **Intune baseline policies** that configure OMA-URIs with tenant IDs. - Use **Azure AD Conditional Access** to block authentication attempts without explicit tenant hints. - Deploy **registry-based policies** via Group Policy to populate HKEY_CURRENT_USER\Software\Microsoft\IdentityModel\Clients\Adal with the correct tenant ID.
Use Get-AzureADTenantDetail to programmatically retrieve the tenant ID and automate registry updates.
Navigate to **Intune admin center > Devices > Enrollment** to review device compliance and **Entra admin center > Properties** to verify tenant ID configuration.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.