535 5.7.139 Authentication unsuccessful is Microsoft 365 refusing your SMTP login, before any message is sent. It is not a bounce and no recipient is involved. The words after the comma name the cause: SMTP AUTH turned off for the tenant or mailbox, security defaults or a Conditional Access policy blocking legacy sign-in, wrong credentials, or Basic authentication disabled. An admin fixes each one in a different place, and from the end of December 2026 Microsoft turns Basic authentication for SMTP AUTH off by default in existing tenants.
Codes from Microsoft's own outbound protection, such as 550 5.7.708, are a separate problem that starts after login succeeds. Both are listed in our SMTP error codes guide for cold email.
Every variant, its cause and the setting behind it
The enhanced code 5.7.139 is Microsoft's own; it is not in the IANA registry. The variants below are the ones reported on Microsoft Q&A and in application vendors' knowledge bases.
Text after 535 5.7.139 Authentication unsuccessful, | Likely cause | Where to fix it |
|---|---|---|
| "SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information." | SMTP AUTH is off for the organisation and the mailbox has no override | Enable Authenticated SMTP for the sending mailbox |
| "user is locked by your organization's security defaults policy. Contact your administrator." | Security defaults are on, which disable SMTP AUTH | Entra ID security defaults, or move to OAuth |
| "the request did not meet the criteria to be authenticated successfully. Contact your administrator." | A policy refused a valid login: security defaults, Conditional Access blocking legacy authentication, per-user MFA set to Enforced, or a blocked location | Entra ID Conditional Access and MFA settings, sign-in logs |
| "basic authentication is disabled" | An authentication policy blocks Basic authentication for SMTP | Exchange Online authentication policies |
| "the user credentials were incorrect" | Wrong or expired password, username not the full email address, or Basic auth blocked upstream | Check credentials first, then the settings above |
| "account has an issue" | No Exchange Online licence, mailbox still provisioning, account disabled or locked out | User licence and account status |
A generic 535 5.7.3 Authentication unsuccessful usually means the username or password was rejected outright. Shared mailboxes cannot sign in to SMTP by themselves: the account needs its own licensed mailbox.
Enable SMTP AUTH per mailbox, not per tenant
Microsoft's guidance is to keep SMTP AUTH off for the organisation and "enable it only for the accounts (mailboxes) that still require it". The mailbox setting wins: "The mailbox setting takes precedence over the organization setting."
In the Microsoft 365 admin centre:
- Go to Users > Active users.
- Select the sending user and, in the flyout, select Mail.
- Under Email apps, select Manage email apps.
- Tick Authenticated SMTP and select Save changes.
In Exchange Online PowerShell:
# See the tenant-wide setting (True means SMTP AUTH is off for the organisation)
Get-TransportConfig | Format-List SmtpClientAuthenticationDisabled
# See one mailbox ($null means "follow the organisation setting")
Get-CASMailbox -Identity outreach@northfield-consulting.example | Format-List SmtpClientAuthenticationDisabled
# Enable SMTP AUTH for this mailbox only
Set-CASMailbox -Identity outreach@northfield-consulting.example -SmtpClientAuthenticationDisabled $false
Only if every mailbox genuinely needs it would you change the tenant setting with Set-TransportConfig -SmtpClientAuthenticationDisabled $false, or clear Turn off SMTP AUTH protocol for your organization under Settings > Mail flow in the Exchange admin centre. That is rarely the right answer for a business that sends cold email from one or two mailboxes.
Settings can take some time to apply. If the error persists straight after a change, wait and test again before changing something else.
Security defaults, Conditional Access and authentication policies
Microsoft is explicit on two points that catch most people:
If security defaults is enabled in your organization, SMTP AUTH is already disabled in Exchange Online. To use SMTP AUTH, you need to disable security defaults.
If your authentication policy disables basic authentication for SMTP, clients cannot use the SMTP AUTH protocol even if you enable the settings outlined in this article.
So the order of checks is:
- Security defaults (Microsoft Entra admin centre, tenant properties). If on, SMTP AUTH with a password will not work for anyone.
- Authentication policies in Exchange Online.
Get-AuthenticationPolicyshows whetherAllowBasicAuthSmtpis false in the policy that applies to the user. - Conditional Access. A policy that blocks legacy authentication applies to SMTP AUTH. In the Microsoft Q&A thread, the accepted answer points to security defaults or Conditional Access, and one administrator reports having to exclude the account from several baseline policies.
- Per-user MFA. Several administrators on the same thread report that per-user MFA set to Enforced produced the "did not meet the criteria" variant.
- Sign-in logs. In Entra ID, the failed sign-in for the user shows which policy blocked it. This is faster than guessing.
Turning off security defaults or excluding an account from Conditional Access weakens your tenant's protection. If you must do it, limit it to one dedicated sending mailbox with a long unique password, and replace security defaults with Conditional Access policies that still protect every other account. A compromised mailbox with SMTP AUTH enabled is a common route into the outbound spam blocks described in the 5.7.708 guide.
App passwords and OAuth
App passwords are a legacy workaround: they exist only where per-user MFA is used and your admin allows them. Q&A contributors report they can clear "did not meet the criteria" errors, and that the account needs a licensed mailbox and MFA enabled to create one. They are still Basic authentication, so they are caught by the same retirement plan.
OAuth is the supported future. Microsoft's SMTP AUTH article says the protocol "supports modern authentication (Modern Auth) through OAuth in addition to basic authentication", and recommends OAuth where the client supports it.
The Basic authentication timeline
Microsoft's message centre post MC786329 (last updated 27 January 2026) sets the current plan:
| Period | Basic authentication for SMTP AUTH |
|---|---|
| Through December 2026 | Behaviour unchanged |
| End of December 2026, existing tenants | Turned off by default; admins can re-enable it |
| Tenants created after December 2026 | Not available by default; OAuth is the supported method |
| Second half of 2027 | Microsoft will announce the final removal date |
If your campaigns rely on a username and password login to smtp.office365.com, check now whether your sending software supports OAuth, and plan what to do if it does not.
Test the login before a campaign
Test authentication on its own, with nothing queued, so you know a failure is about login and not content.
- Use the application's connection test if it has one. It should report success against
smtp.office365.com, port 587, with STARTTLS. - Or test by hand with openssl:
openssl s_client -starttls smtp -crlf -connect smtp.office365.com:587
EHLO test.northfield-consulting.example
AUTH LOGIN
The server answers with base64 prompts for the username and password. A good login ends with 235 2.7.0 Authentication successful; a refusal returns one of the 535 lines above. Type QUIT to close. Do not paste production passwords into shared terminals or logs.
- Send one message to an external mailbox you control and check it arrives with DKIM passing.
If login works but the server then refuses to send for another domain, paste the bounce into the SMTP error code lookup for a plain reading.
Alternatives if SMTP AUTH must stay off
Many organisations will keep SMTP AUTH off, and they are right to. Options:
| Option | Good for | Watch out for |
|---|---|---|
| OAuth-capable sending application | Keeping Microsoft 365 as the sender | The application must support Microsoft's OAuth flow for SMTP |
| Separate email service with your domain | Campaign volume to external recipients | Set up SPF, DKIM and DMARC for that service; it has its own rules |
| Relay through on-premises Exchange (hybrid) | Organisations that already run Exchange | More infrastructure to secure |
| Microsoft 365 High Volume Email | Internal mail only, currently in preview | Not for external recipients |
How Map Extract helps
Map Extract's bulk email sender connects to the SMTP routes you configure, using the host, port, security setting and credentials you enter; credentials are stored in Windows Credential Manager.
- Test before you send. The SMTP routes screen is where you configure and test each sender and inspect its authentication and connection result. A 535 5.7.139 shows up there, before any campaign is affected.
- Failover between your own routes. If several eligible SMTP routes are configured, a send can fail over to another one, so one mailbox losing SMTP AUTH does not have to stop a reviewed campaign. Fix or remove the failing route rather than leaving it in rotation.
- No blind retries. A send whose outcome is uncertain is marked Uncertain and not resent automatically.
Be aware of the limits. Map Extract's documentation describes username and password SMTP credentials; it does not describe OAuth sign-in for Microsoft 365. If your tenant keeps SMTP AUTH off, or once Basic authentication is off by default at the end of December 2026, plan to use an SMTP route that supports password authentication legitimately, such as a dedicated email service set up for your domain. Map Extract does not change Microsoft 365 settings for you.
Key takeaways
- 535 5.7.139 is a refused login, not a bounce; read the words after the comma.
- Enable Authenticated SMTP per mailbox; the mailbox setting overrides the tenant.
- Security defaults and authentication policies block SMTP AUTH even when the mailbox allows it.
- Check Entra ID sign-in logs to see which policy refused the login.
- Basic authentication for SMTP AUTH is off by default in existing tenants from the end of December 2026; plan for OAuth or another route.
Frequently asked questions
How do I fix 535 5.7.139 SmtpClientAuthentication is disabled for the Tenant?
An admin needs to allow SMTP AUTH for the mailbox that sends. In the Microsoft 365 admin centre, open Users, Active users, select the user, choose Mail, then Manage email apps, tick Authenticated SMTP and save. Microsoft recommends enabling it only for mailboxes that need it rather than for the whole tenant. Changes can take a while to apply.
Why does 535 5.7.139 still appear after I enabled Authenticated SMTP?
Something else is still blocking the sign-in. Microsoft says SMTP AUTH is disabled whenever security defaults are on, and that an authentication policy blocking Basic authentication for SMTP overrides the mailbox setting. Conditional Access policies that block legacy authentication, per-user MFA set to Enforced, or a wrong password can all produce the same code with different wording.
Is Microsoft turning off Basic authentication for SMTP AUTH?
Yes, in stages. Microsoft's message centre post MC786329, last updated in January 2026, says behaviour is unchanged through December 2026. At the end of December 2026 Basic authentication for SMTP AUTH is turned off by default for existing tenants, though admins can re-enable it, and new tenants will not have it. A final removal date is due in the second half of 2027.
Can I send through Microsoft 365 without SMTP AUTH?
Yes, but not with a plain username and password client. Options include an application that signs in with OAuth, sending through a separate email service configured with your domain's SPF and DKIM, or relaying through an on-premises Exchange server in a hybrid setup. Microsoft's High Volume Email option is limited to internal recipients, so it is not a route for external outreach.
Sources
- Microsoft: Enable or disable SMTP AUTH in Exchange Online
- Microsoft message center MC786329: Exchange Online to retire Basic auth for Client Submission (SMTP AUTH)
- Microsoft Q&A: 535 5.7.139 Authentication unsuccessful
- MIDAS knowledge base: Fix 5.7.139 Authentication unsuccessful errors
- Microsoft: Fix NDR error 550 5.7.700 through 550 5.7.750 in Exchange Online
Written by the Map Extract editorial team. Found an error? Email support@mapextract.uk and we will check and correct it. How we research guides: editorial policy.