Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | AADSTS50074: The user's sign-in was blocked in accordance with the organization's sign-in policy. | Entra admin center > Monitoring & health > Sign-in logs | -> Authentication requirements tab |
| Affected build range | Microsoft 365 / Entra ID | OS Build | |
| Registry key involved | HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\EnableADAL | Registry Editor | -> Set to 1 for Modern Auth |
| Relevant service/endpoint URL | https://login.microsoftonline.com/common/oauth2/v2.0/token | OAuth endpoint | |
| Log line signature | AADSTS50074: The user's sign-in was blocked in accordance with the organization's sign-in policy. | msal.log or adal.log | -> Confirm client-side error |
Log Files to Check
C:\Users\<username>\AppData\Local\Microsoft\<application>\auth_logs\msal.logC:\Users\<username>\AppData\Local\Microsoft\<application>\auth_logs\adal.log
What This Error Actually Means
AADSTS50074 is an error code raised by Microsoft Entra ID when a user's sign-in attempt is blocked due to the organization's Conditional Access policies or multifactor authentication (MFA) requirements. Specifically, this error occurs when a legacy client application attempts to authenticate using Basic Auth, NTLM, POP3, IMAP4, SMTP AUTH, or other protocols that do not support interactive MFA challenges. The user will see an immediate failure in the sign-in process without any further information, as these clients cannot prompt for additional authentication factors.Affected Versions and Scope
AADSTS50074 is relevant to Microsoft 365 / Entra ID environments where Conditional Access policies or per-user MFA requirements are enforced. This error does not affect modern applications that support OAuth 2.0, such as the Outlook mobile app or web-based email clients like Office 365 Webmail. It also does not apply to users who have been exempted from these security measures through Conditional Access policies.Where To Look First: Logs and Event IDs
To diagnose AADSTS50074, start by examining the sign-in logs in Entra admin center under Monitoring & health > Sign-in logs. Filter for Status=Failure and Error code=50074 to find relevant entries. Expand each entry to view detailed information about the failed authentication attempt. Additionally, check the client machine's application-specific log files:C:\Users\\AppData\Local\Microsoft\ \auth_logs\msal.log C:\Users\\AppData\Local\Microsoft\ \auth_logs\adal.log
AADSTS50074: The user's sign-in was blocked in accordance with the organization's sign-in policy. These logs will provide context about which client application and protocol were used during the failed authentication attempt.
Root Causes
MFA Requirement for Legacy Clients
This occurs when a Conditional Access policy or per-user MFA requirement is enforced, but the user's sign-in attempt uses a legacy client that cannot handle interactive MFA challenges. To identify this cause, check the Entra admin center > Users > Active users to see if multifactor authentication is enabled for the affected account.Conditional Access Policy with MFA Requirement
A Conditional Access policy may mandate MFA for all or specific users but does not exempt legacy clients from this requirement. To investigate, navigate to Entra admin center > Protection > Conditional Access and review policies that enforce 'Require multifactor authentication'.Tenant-Wide Authentication Policies Allowing Basic Auth
If your tenant's authentication policy still permits Basic Auth for certain protocols (e.g., IMAP or SMTP), but MFA is required, this can lead to AADSTS50074. UseGet-AuthenticationPolicy | Select-Object Name,AllowBasicAuth* in Exchange Online PowerShell to check the tenant-wide policy.
Fix Procedure
- Migrate Client Application to Modern Authentication:
- For Outlook desktop clients: Ensure version 2016 or later is installed and enable ADAL by setting
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\EnableADALto DWORD value 1. - For mobile devices, use the official Outlook app which supports OAuth 2.0 for authentication.
- For Apple Mail on macOS: Use Sign in with Microsoft button instead of legacy protocols.
- For Outlook desktop clients: Ensure version 2016 or later is installed and enable ADAL by setting
- Create an App Password:
- Navigate to Microsoft 365 admin center > Users > Active users, select the user, and go to Manage multifactor authentication. Allow users to create app passwords if necessary.
- Users can then generate an app password at
myaccount.microsoft.com. - Note: App passwords are only useful when per-user MFA is enforced (not Conditional Access).
- Exempt Legacy Clients from CA Policy:
- In Entra admin center > Conditional Access, select the policy causing AADSTS50074.
- Go to Conditions > Client apps and uncheck 'Exchange ActiveSync clients' and 'Other clients' to exclude legacy auth clients from MFA requirements.
- Update Service Accounts Using SMTP AUTH:
- In Exchange Online PowerShell, run
Set-CASMailbox -Identity [email protected] -SmtpClientAuthenticationDisabled $false. - Register an app in Entra admin center > App registrations and grant Office 365 Exchange Online > SMTP.Send application permission.
- In Exchange Online PowerShell, run
Exempting legacy clients from Conditional Access policies weakens security. Prefer migrating to Modern Authentication whenever possible.
Error Code Variants
| Code | Description |
|---|---|
| AADSTS50134 | The user's sign-in was blocked due to a Conditional Access policy that requires multi-factor authentication but the client application does not support it. |
| AADSTS65002 | Invalid tenant or domain name specified in the request. |
| AADSTS70001 | The provided access token is expired, revoked, or malformed. |
Verification
After implementing fixes, verify that AADSTS50074 no longer occurs:- In Entra admin center > Monitoring & health > Sign-in logs, check for Status=Success entries with the corrected client application.
- Review
C:\Users\and\AppData\Local\Microsoft\ \auth_logs\msal.log adal.logfor successful authentication attempts without AADSTS50074 errors.
Prevention
To prevent recurrence of AADSTS50074, ensure all client applications are updated to use modern authentication protocols that support MFA. Additionally, regularly review and update Conditional Access policies to exclude legacy clients from MFA requirements where necessary.Use
By following these steps, you can effectively diagnose and resolve AADSTS50074 errors while maintaining a secure environment.Get-MgIdentityConditionalAccessPolicy in PowerShell to list all enabled Conditional Access policies and their conditions for quick reference.