Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | AADSTS90072: Guest user sign-in is blocked by cross-tenant access policy. | AAD sign-in error response | Displayed to user during authentication |
| Affected OS build | Windows 11 22H2 (22621.x) | OS version check | All 22H2 builds |
| Registry key/OMA-URI | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAD\CrossTenantAccessPolicy | Windows Registry | Policy enforcement configuration |
| Service endpoint | https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize | AAD authentication endpoint | Failing request URL |
| Log line signature | CrossTenantAccessPolicyDecision: Deny, Reason: GuestUserRestriction | Azure AD sign-in logs | Audit log correlation |
Log Files to Check
C:\ProgramData\Microsoft\AzureAD\Logs\AADAgent.logC:\Windows\System32\winevt\Logs\Microsoft-Windows-Security-Auditing.evtx
What This Error Actually Means
The error
AADSTS90072: Guest user sign-in is blocked by cross-tenant access policy indicates that Azure Active Directory (Azure AD) has enforced a cross-tenant access policy to deny authentication for a guest user attempting to access a resource in a home tenant. This error is raised by the Azure AD authentication component during the OAuth 2.0 authorization flow, specifically at the
https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize endpoint. The policy in question is designed to restrict guest user access across tenants, often configured to mitigate risks from untrusted or unvetted external identities. The error explicitly ties to the
GuestUserRestriction rule within the cross-tenant access policy framework, which evaluates whether a guest user is permitted to authenticate based on pre-defined trust boundaries.
Affected Versions and Scope
This error affects tenants running **Windows 11 22H2 (OS build 22621.x)** where a cross-tenant access policy explicitly blocks guest users. It is not limited to this OS version but is most commonly observed in environments where Azure AD is tightly integrated with Windows device enrollment and conditional access policies. The issue occurs when the home tenant has configured a **cross-tenant access policy** with
GuestUserRestriction enabled, or when a **device-based policy** (e.g., via Intune or registry) enforces this restriction. Tenants that have not configured cross-tenant policies or have explicitly allowed guest access via the
Allow rule in their Azure AD tenant properties are unaffected. Additionally, tenants using **Azure AD B2B collaboration with trusted domains** are less likely to encounter this error due to implicit trust relationships.
Where To Look First: Logs and Event IDs
To diagnose this error, begin by examining the following logs and event sources:
- **Azure AD Sign-in Logs**: Look for the exact line
CrossTenantAccessPolicyDecision: Deny, Reason: GuestUserRestriction in the
C:\ProgramData\Microsoft\AzureAD\Logs\AADAgent.log file. This log line confirms the policy enforcement.
- **Windows Security Event Logs**: Check the
Microsoft-Windows-Security-Auditing.evtx log (path:
C:\Windows\System32\winevt\Logs\) for **Event ID 4625** (failed logon) and **Event ID 4768** (Kerberos authentication ticket requested). These events often correlate with the
AADSTS90072 error when local device policies interact with Azure AD.
- **Azure AD Audit Logs**: Search for "cross-tenant access policy" in the Azure portal under **Entra ID > Audit logs** to identify when the policy was last modified.
Root Causes
1. Cross-Tenant Policy Enforcement
The primary cause is a misconfigured cross-tenant access policy in the home tenant. This policy can be set via the Azure portal or PowerShell. To differentiate this cause, check the policy's
GuestUserRestriction setting using:
Get-AzADCrossTenantAccessPolicy
If the
GuestUserRestriction property is set to
Enabled, the policy is active.
2. Device-Based Registry Override
A registry key override on the affected device can enforce the restriction. The key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAD\CrossTenantAccessPolicy may contain a
GuestUserRestriction DWORD set to
1. This configuration bypasses tenant-level policies and applies the restriction locally.
3. Intune Device Configuration Profile
An Intune device configuration profile with an OMA-URI of
./Device/Vendor/MSFT/Policy/Config/EntraID/CrossTenantAccessPolicy/GuestUserRestriction might enforce the restriction. This is common in environments with strict device compliance policies.
Fix Procedure
- **Modify the Cross-Tenant Policy via PowerShell**:
Set-AzADCrossTenantAccessPolicy -GuestUserRestriction "Disabled"
This disables the restriction at the tenant level. Verify the change with:
Get-AzADCrossTenantAccessPolicy | Select-Object GuestUserRestriction
- **Adjust the Device Registry Key**:
Open the registry editor and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAD\CrossTenantAccessPolicy. Set the GuestUserRestriction DWORD to 0. Warning: Modifying this key on enrolled devices can break conditional access policies if not aligned with tenant settings.
- **Update Intune Configuration Profile**:
In the **Intune admin center > Devices > Device configuration > Profiles**, locate the profile with the OMA-URI
./Device/Vendor/MSFT/Policy/Config/EntraID/CrossTenantAccessPolicy/GuestUserRestriction. Edit the profile to set the value to 0 and reassign it to the affected devices.
- **Verify Policy Application**:
Use
Get-AzureADUser -ObjectId "[email protected]" to confirm the user's status and Get-WinEvent -LogName "Microsoft-Windows-Security-Auditing" -MaxEvents 50 to check for residual policy enforcement events.
Error Code Variants
| Error Code |
Description |
Component |
Distinguishing Factor |
| AADSTS90072 |
Guest user sign-in blocked by cross-tenant policy |
Azure AD Authentication |
Log line: CrossTenantAccessPolicyDecision: Deny, Reason: GuestUserRestriction |
| AADSTS50146 |
Guest user sign-in blocked by conditional access |
Conditional Access Policies |
Log line: ConditionalAccessPolicyDecision: Deny |
| AADSTS50057 |
User account is disabled |
User Account Status |
Log line: UserAccountDisabled |
Verification
After applying fixes, verify resolution by:
1. Re-attempting the guest user sign-in and confirming no
AADSTS90072 error occurs.
2. Checking
AADAgent.log for the line
CrossTenantAccessPolicyDecision: Allow.
3. Using
dsregcmd /status on the device to confirm Azure AD registration state and policy compliance.
Prevention
To prevent recurrence:
- **Establish a Baseline Policy**: Configure a default cross-tenant access policy in the Azure portal under **Entra ID > Properties > Authentication** that explicitly allows guest users for trusted scenarios.
- **Audit Intune Profiles**: Regularly review Intune device configuration profiles for unintended OMA-URI settings using:
Get-IntuneDeviceConfigurationPolicy | Where-Object { $_.omaUris -like "*CrossTenantAccessPolicy*" }
- **Monitor Policy Changes**: Enable Azure AD audit logging and set alerts for modifications to cross-tenant access policies via:
Get-AzADAuditLogRecord -Filter "activityDisplayName eq 'Update cross-tenant access policy'"
Tip: Use Get-AzureADUser -All $true | Where-Object UserType -eq "Guest" to proactively identify and review guest users in your tenant.