
For years, many tools sent mail through Microsoft 365 with just a username and password. That's ending. Microsoft is turning off Basic authentication for SMTP AUTH by default, and OAuth is the supported path for apps and devices that send through Exchange Online. This guide covers Microsoft 365 OAuth setup: the current timeline, how OAuth works for mailboxes, connecting sending tools, registering your own app, the mailbox settings that still matter, tokens, and fixes for the most common errors.
Basic Auth for SMTP Is Being Switched Off — Here's the Current Timeline
💡 TL;DR
Complete your Microsoft 365 OAuth setup before Basic authentication for SMTP AUTH is turned off by default. Under Microsoft's January 2026 update, Basic auth is disabled by default for existing tenants at the end of December 2026 (admins can still re-enable it for now), new tenants created after December 2026 won't have it by default, and a final removal date is due in the second half of 2027. Connect sending tools by OAuth, grant admin consent where needed, and keep SMTP AUTH enabled per mailbox only if a tool submits via SMTP with OAuth.
Microsoft's original plan was to start rejecting Basic auth for SMTP AUTH in March 2026. In January 2026 it revised the timeline: Basic auth behavior stays unchanged until December 2026; at the end of December 2026 it's disabled by default for existing tenants, though administrators can still turn it back on; tenants created after December 2026 won't have it by default; and Microsoft will announce the final removal date in the second half of 2027.
Many guides still quote the older March 2026 date. Either way, the direction is clear: Basic auth for sending is on its way out, and OAuth is the supported method. SMTP AUTH itself isn't going away — only the Basic auth way of using it.
By the end of this, you'll know exactly how to complete Microsoft 365 OAuth setup for your mailboxes and sending tools before the default changes reach your tenant.
How OAuth Works for Microsoft 365 Mailboxes
An app is registered in Microsoft Entra ID — either the sending tool's own app or one you register.
Consent is granted — by the user, or by an admin for the whole tenant — for specific permissions.
The user signs in through Microsoft's sign-in page, completing MFA if required.
The app receives tokens — a short-lived access token and a longer-lived refresh token.
The app sends mail using the access token, via SMTP AUTH with OAuth, IMAP/POP with OAuth, or Microsoft Graph.
Tokens refresh automatically until they're revoked or expire.
The password never goes to the app. That's the core security improvement — and it's why OAuth works smoothly with MFA, as covered in Microsoft 365 MFA setup.
Delegated vs Application Permissions
Type | Acts as | Typical use | Example permissions |
|---|---|---|---|
Delegated | A signed-in user | Sending tools connecting individual mailboxes | SMTP.Send, IMAP.AccessAsUser.All, Mail.Send (Graph), offline_access |
Application | The app itself, without a user | Background services sending from many mailboxes | Mail.Send (Graph) with admin consent — scope it carefully |
Most cold email tools use delegated permissions: each mailbox is connected by a user signing in once. Application permissions are powerful — an app with tenant-wide Mail.Send can send as any mailbox — so limit them with policies where you use them, and grant them only to apps you control.
Connecting Sending Tools by OAuth
For most teams, Microsoft 365 OAuth setup simply means connecting mailboxes to tools like Instantly, Smartlead, or Lemlist.
Check consent settings. If users can't consent to apps in your tenant, an admin needs to grant consent for the tool's app first — or approve it through the admin consent workflow.
In the tool, choose Microsoft / Outlook / OAuth when adding a mailbox — not SMTP with a password.
Sign in as the mailbox on Microsoft's page and complete MFA.
Approve the requested permissions and finish the connection.
Send a test message and confirm it appears in the mailbox's Sent Items.
Record the connection in your inventory, with who connected it and when.
Here's the advice we'd push back on: "If OAuth gives an error, just switch the tool to SMTP with a password." That works today and may stop working when Basic auth is turned off by default. Fix the OAuth problem instead — usually consent or a mailbox setting.
Litemail Microsoft 365 inboxes support one-click OAuth export to common sending tools, with full admin access so you can manage consent yourself.
Registering Your Own App
If you're building your own sending service or integration, register an app.
In the Microsoft Entra admin center, go to App registrations and create a new registration.
Choose supported account types — single tenant for internal use, multi-tenant if customers will connect their tenants.
Add a redirect URI for your sign-in flow.
Add API permissions — for SMTP with OAuth, the SMTP.Send permission; for Graph, Mail.Send — plus offline_access for refresh tokens.
Create credentials — prefer a certificate over a client secret, and rotate them.
Grant admin consent if your permissions require it.
Implement token handling — store refresh tokens encrypted, refresh before expiry, and handle revocation.
For platforms provisioning mailboxes at scale, the broader steps are in Microsoft 365 mailbox provisioning.
Mailbox Settings That Still Matter
🔌SMTP AUTH per mailbox
If a tool submits mail via SMTP AUTH — even with OAuth — SMTP AUTH must be enabled for that mailbox (and not disabled tenant-wide). Tools sending through Graph don't need it.
🛡️Security defaults / Conditional Access
These block legacy authentication, which is fine once tools use OAuth.
🔐MFA
Completed once during connection; tokens continue afterwards.
📛Send-as permissions
Only needed if a tool sends as a different address than the signed-in mailbox.
In Exchange Online PowerShell, Set-CASMailbox with -SmtpClientAuthenticationDisabled controls SMTP AUTH per mailbox. Leave it disabled for mailboxes that don't need SMTP submission — that's a smaller attack surface.
A Pre-December Checklist
Use this to finish your Microsoft 365 OAuth setup before the default change reaches your tenant.
Find Basic auth senders. The SMTP AUTH Clients Submission report in the Exchange admin center shows whether Basic auth or OAuth is used.
List every tool and device that sends through Exchange Online — sending tools, CRMs, scanners, apps.
Switch each to OAuth where supported, or move it to a supported alternative.
Reconnect outreach mailboxes by OAuth and remove stored passwords from tools.
Disable SMTP AUTH on mailboxes that no longer need it.
Re-run the report and confirm no Basic auth submissions remain.
Done early, this is a calm afternoon's work. Done after the default changes, it's an outage. Teams that finish their Microsoft 365 OAuth setup ahead of time simply notice nothing in January.
Tokens and Common Errors
Symptom | Likely cause | Fix |
|---|---|---|
Consent error during connection (for example AADSTS65001) | User or admin hasn't consented to the app | Grant admin consent or use the admin consent workflow |
535 5.7.139 SmtpClientAuthentication is disabled | SMTP AUTH disabled for the tenant or mailbox | Enable SMTP AUTH for that mailbox, if the tool needs it |
Tool disconnected after a password reset | Refresh token revoked | Reconnect the mailbox by OAuth |
Repeated sign-in prompts | Conditional Access requiring frequent re-authentication | Review policy session settings for the tool |
Mail sends but isn't in Sent Items | Tool sending a different way than expected | Check the tool's Microsoft connection mode |
OAuth handles sign-in; authentication of the messages themselves still depends on SPF, DKIM, and DMARC — see SPF for Google Workspace and Microsoft 365 and the DKIM guide. Keep complaints under 0.1%, per Google's email sender guidelines.
Microsoft 365 mailboxes ready for OAuth — Litemail Microsoft 365 inboxes come with full admin access, one-click OAuth export to Instantly and Smartlead, SPF/DKIM/DMARC pre-configured, dedicated US and EU IPs, and pre-warmed options. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: Microsoft 365 MFA Setup · Microsoft 365 Mailbox Providers · Microsoft 365 Mailbox Provisioning · Microsoft 365 Pre-Warmed Accounts
Key Takeaways
Complete Microsoft 365 OAuth setup now: Basic auth for SMTP AUTH is disabled by default for existing tenants at the end of December 2026.
New tenants created after December 2026 won't have Basic auth for SMTP AUTH by default; final removal is due to be announced in the second half of 2027.
Connect sending tools by OAuth with delegated permissions, granting admin consent where required.
If a tool sends via SMTP AUTH with OAuth, SMTP AUTH must still be enabled for that mailbox.
Prefer certificates over client secrets for your own apps, and store refresh tokens encrypted.
Fix OAuth errors rather than falling back to passwords.
Frequently Asked Questions
When does Microsoft turn off Basic auth for SMTP AUTH?
Under Microsoft's January 2026 update, it's disabled by default for existing tenants at the end of December 2026 (admins can still re-enable it for now), unavailable by default for new tenants created after December 2026, with a final removal date to be announced in the second half of 2027.
How do I do Microsoft 365 OAuth setup for a cold email tool?
Choose the tool's Microsoft OAuth option, sign in as the mailbox, complete MFA, and approve permissions. If users can't consent to apps, an admin must grant consent first.
Is SMTP AUTH being removed from Microsoft 365?
No. Only Basic authentication for SMTP AUTH is being retired. SMTP AUTH with OAuth remains supported.
Why do I get a 5.7.139 SmtpClientAuthentication error?
SMTP AUTH is disabled for the tenant or mailbox. Enable it for mailboxes whose tools submit via SMTP AUTH.
What's the difference between delegated and application permissions?
Delegated permissions act as a signed-in user; application permissions act as the app itself, often across many mailboxes, and need careful scoping.
Does OAuth work with MFA?
Yes. The user completes MFA once when connecting, and the app then uses tokens without further prompts.
Do Litemail Microsoft 365 inboxes support OAuth?
Yes. Litemail Microsoft 365 inboxes support one-click OAuth export to common sending tools and include full admin access.
OAuth-Ready Microsoft 365 Mailboxes
Litemail Microsoft 365 inboxes come with full admin access, one-click OAuth export, SPF/DKIM/DMARC configured, dedicated US and EU IPs, and free domain replacement on pre-warmed plans.
Plans from $39/month · Microsoft 365 and Google Workspace · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Microsoft 365 Inboxes · Instantly.ai Review 2026 · Microsoft Cold Email Policy 2026 · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


