What Does 535 5.7.139 Mean, and How Do I Fix It?
On this page
Short answer
535 5.7.139 Authentication unsuccessful means Exchange Online refused an SMTP AUTH login and names the reason after the comma: SMTP AUTH disabled for the tenant or for the mailbox, or security defaults blocking the user, among others. An admin can turn SMTP AUTH on for one mailbox in the Microsoft 365 admin center. Security defaults protect the whole tenant, so changing them is the admin's call.
What the error says
535 5.7.139 Authentication unsuccessful is Exchange Online's reply to a failed SMTP AUTH login on smtp.office365.com. Unlike 535 5.7.3, it gives the reason after the comma. Texts seen in Microsoft's documentation and Q&A:
Text after "Authentication unsuccessful," | What blocks the login | Who can change it |
|---|---|---|
SmtpClientAuthentication is disabled for the Tenant | SMTP AUTH is off for the organization | A tenant admin |
SmtpClientAuthentication is disabled for the Mailbox | SMTP AUTH is off for this mailbox | A tenant admin |
user is locked by your organization's security defaults policy. Contact your administrator. | Security defaults block legacy sign-in | An admin with at least the Conditional Access Administrator role |
the organization configuration doesn't allow this authentication request | A tenant setting; Microsoft's fix on its High Volume Email page is turning off security defaults | A Security or Conditional Access administrator |
federated STS service was unreachable | The on-premises federation server | That server's admin |
The first three texts are from Microsoft Q&A threads (tenant, 2021; mailbox, August 2026; security defaults, May 2025). The organization configuration line is on Microsoft's High Volume Email troubleshooting page, and the federated STS line is on its troubleshooting page for apps and devices. The mailbox text points to aka.ms/smtp_auth_disabled, Microsoft's SMTP AUTH page.
Disabled for the Tenant or the Mailbox
Exchange Online has an organization-wide SMTP AUTH setting and a per-mailbox one, and "the mailbox setting takes precedence over the organization setting" (SMTP AUTH page). SMTP AUTH is off in organizations created after January 2020, per Microsoft's setup guide. Microsoft recommends keeping it off for the organization and on only for mailboxes that need it.
To turn it on for one mailbox in the Microsoft 365 admin center:
Go to Users > Active users and select the user.
In the flyout, select Mail, then Manage email apps.
Check Authenticated SMTP, then select Save changes.
In Exchange Online PowerShell: Set-CASMailbox -Identity <MailboxIdentity> -SmtpClientAuthenticationDisabled $false. The value $null hands the mailbox back to the organization setting. Get-TransportConfig | Format-List SmtpClientAuthenticationDisabled shows the organization switch; True means off.
OAuth logins use the same protocol: SMTP AUTH "supports modern authentication (Modern Auth) through OAuth in addition to basic authentication", and the setup guide says to use a different sending method if SMTP AUTH is intentionally disabled for the organization or the mailbox. The SMTP AUTH page adds that if an authentication policy disables Basic authentication for SMTP, clients can't use SMTP AUTH even with these settings on.
Locked by security defaults
Security defaults are Microsoft Entra ID's baseline protection: MFA registration for every user and a block on legacy authentication, which covers "any client that uses older mail protocols such as IMAP, SMTP, or POP3" (security defaults). They are on in new tenants from creation and may be on in any tenant created on or after October 22, 2019. With them on, "SMTP AUTH is already disabled in Exchange Online," says the SMTP AUTH page.
The setting is in the Microsoft Entra admin center under Entra ID > Overview > Properties > Manage security defaults, where the off option reads "Disabled (not recommended)". Organizations that turn it off "should immediately enable Conditional Access policies", which need Microsoft Entra ID P1. The change affects every user in the tenant, so it is the admin's decision.
Personal Outlook.com accounts
Q&A threads from May and August 2026 report "disabled for the Mailbox" on newly created personal Outlook.com and Hotmail accounts, OAuth included. A personal account has no admin center, and we found no Microsoft document that names a setting or a cause.
After December 2026
At the end of December 2026, password logins over SMTP AUTH go off by default in existing tenants, and admins can turn them back on (Exchange Team Blog, January 27, 2026). Microsoft hasn't said which reply tools will see then. The SMTP AUTH clients report shows Basic Auth or Modern Auth for each sender.
Free guide19 min read
Send 100,000 cold emails a month
Domains and mailboxes you need, DNS, warmup, lists, copy and follow-ups, with a launch checklist, sent to your inbox.
What it means for cold email
A tenant-wide block stops every mailbox at once. A new tenant can start with SMTP AUTH off and security defaults on, so its first sequencer connection fails until an admin changes that.
A vendor's tenant. If a vendor runs the tenant, as with some Azure inboxes, only an admin of that tenant can change these settings.
Limits after the fix. The tenant's external quota still applies: see 550 5.7.233.
Questions
How do I fix "SmtpClientAuthentication is disabled for the Tenant"?
An admin turns on Authenticated SMTP for the sending mailbox in the Microsoft 365 admin center; the rest of the tenant can stay off. Wait before reconnecting: Smartlead suggests 20 to 30 minutes, Instantly an hour.
Can I keep security defaults on and still use SMTP AUTH?
Microsoft's pages differ. The SMTP AUTH page says SMTP AUTH is already disabled under security defaults; the setup guide calls password-based submission incompatible and recommends OAuth. Try OAuth first. If that fails, what's left is Conditional Access in place of security defaults, or another sending method.
What we recommend at Outreach2day
We don't sell Microsoft 365 mailboxes: Outreach2day mailboxes are standard SMTP/IMAP on our own infrastructure, outside any Microsoft tenant, so the SMTP AUTH switches and security defaults above don't apply to them. We recommend up to 25 cold emails per mailbox a day after 14 days of warmup.
Sources
- Microsoft Learn: Enable or disable SMTP AUTH in Exchange Online: learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission
- Microsoft Learn: Security defaults in Microsoft Entra ID: learn.microsoft.com/en-us/entra/fundamentals/security-defaults
- Microsoft Learn: How to set up a multifunction device or application to send email using Microsoft 365: learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365
- Microsoft Learn: Fix issues with printers, scanners, and LOB apps that send email using Microsoft 365: learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/fix-issues-with-printers-scanners-and-lob-applications-that-send-email-using-off
- Microsoft Learn: Troubleshoot High Volume Email for Microsoft 365: learn.microsoft.com/en-us/exchange/mail-flow-best-practices/troubleshoot-high-volume-email-m365
- Microsoft Learn: SMTP AUTH clients report in the new EAC: learn.microsoft.com/en-us/exchange/monitoring/mail-flow-reports/mfr-smtp-auth-clients-report
- Exchange Team Blog: Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline: techcommunity.microsoft.com/blog/exchange/updated-exchange-online-smtp-auth-basic-authentication-deprecation-timeline/4489835
- Microsoft Q&A: 535 5.7.139, SmtpClientAuthentication is disabled for the Tenant: learn.microsoft.com/en-us/answers/questions/637253/nodemailer-throw-error-of-auth-535-5-7-139-authent
Related answers
- What Does 535 5.7.3 Mean, and How Do I Fix It?Outlook and Microsoft
- What Does 550 5.7.233 Mean, and How Do I Fix It?Bounces and errors
- Why Is Outlook Blocking or Junking My Cold Emails?Outlook and Microsoft
- How Many Cold Emails Should One Mailbox Send per Day?Volume and setup
In depth on the blog
- Microsoft 365 Cold Email After MC1454397: New-Tenant Limits8 min read
- Azure Inboxes for Cold Email: What You Buy in 20269 min read
- Microsoft 365 and Outlook Sending Limits9 min read

