Fix Outlook Error 0x800CCC0E with Gmail and Yahoo
Outlook throws 0x800CCC0E when sending through Gmail or Yahoo after a password change. The OAuth token is stale. Here's how to fix it.
Email configuration, security, and troubleshooting
Outlook throws 0x800CCC0E when sending through Gmail or Yahoo after a password change. The OAuth token is stale. Here's how to fix it.
When users sign into Outlook or other Microsoft 365 apps, they may see "Something went wrong. [4usqa]" followed by "We couldn't sign you in. If
Your emails are being rejected with a 550-5.7.26 error because the receiving server cannot validate your DKIM signature, causing a DMARC policy failure. The Fix First, diagnose the
Your domain is failing SPF authentication, appearing as spf=none in DMARC reports. This means no SPF record was found, causing DMARC to fail and emails to be quarantined or
Outlook or Teams shows error AADSTS50053 with message "Your account is locked" or "Sign-in blocked." Azure AD Smart Lockout has temporarily locked the account after too
Outlook or Teams shows error AADSTS50076 with message "Due to a configuration change made by your administrator, you must use multi-factor authentication." An MFA policy (Security Defaults, per-user
Outlook error 0x80040305 occurs when sending email, generating a non-delivery report with "Submit-Message failed" and diagnostic code 0x80040305-0x00000000-0x00000000. Email typically works in Outlook on the web but fails
You're seeing "We couldn't sign you in" with error codes CAA20003, CAA20002, or CAA2000B in Outlook, Teams, or other Office apps. This is a