As of March 1, 2026, Microsoft killed Basic Auth for SMTP — which means the old username-and-password way of connecting a Microsoft 365 inbox to Smartlead no longer works at all. If your connection broke this year, that's why. Getting a Microsoft 365 inbox for Smartlead integration working now means OAuth, and OAuth has its own setup steps that trip people up. This is the current, post-deprecation walkthrough: enabling what Microsoft requires, connecting through OAuth, dialing in the sending settings that keep the inbox healthy, and fixing the connection errors that come up most. No outdated SMTP instructions.
What Changed in March 2026 (Read This First)
Here's the thing that breaks most Microsoft 365 connections in 2026. Microsoft deprecated Basic Auth for SMTP on March 1, 2026. Their servers now reject the old AUTH LOGIN and AUTH PLAIN commands that static username-password credentials relied on.
Translation: if you were connecting Outlook to Smartlead with SMTP credentials, that stopped working. Only OAuth 2.0 — the secure login flow where you authorize the app instead of handing over a password — is accepted now.
🚩 If your Smartlead connection died in 2026
This is almost certainly why. Most sales platforms — Smartlead, Apollo, Instantly, Lemlist — added OAuth support ahead of the deadline, but anyone still on SMTP username-password got cut off. The fix isn't troubleshooting the old connection. It's reconnecting via OAuth. Don't waste an hour debugging a method Microsoft turned off.
So every instruction below assumes OAuth. By the end you'll have a live, stable connection sending from your Microsoft 365 inbox through Smartlead.
Before You Connect: The One-Time Microsoft Setup
OAuth needs one thing enabled on the Microsoft side first, and skipping it is the most common reason the connection fails. You need Microsoft 365 admin access for this — it's a one-time step per tenant.
Enable Authenticated SMTP and IMAP for the inbox in the Microsoft 365 Admin Center. OAuth still rides on these protocols being switched on.
Wait 20 to 30 minutes. Microsoft's changes don't apply instantly. Connect too soon and OAuth fails even though you did everything right.
Confirm you have admin rights. Enabling these settings requires admin access — if you're not the admin, get whoever is to flip them on.
That wait is real. People enable the settings, immediately try to connect, hit an error, and assume the whole thing is broken. It's not — it just hasn't propagated. Give it half an hour.
If you bought your inbox with full admin access, you can do this yourself. Litemail inboxes come with full Microsoft 365 admin credentials, so you're not stuck waiting on a provider to flip a setting. For the broader setup, our Microsoft 365 cold email setup guide covers the base.
Connecting the Inbox via OAuth
With the Microsoft side ready, the Smartlead side takes about three minutes. Here's the flow.
In Smartlead, go to Email Accounts in the left sidebar.
Click Connect Mailbox in the top right.
Choose your infrastructure type, then select Outlook / Microsoft 365 as the provider.
Enter the inbox email, sign in, and on the permissions screen click Accept — accept every permission prompt, or the connection won't complete.
Smartlead confirms the connection. The inbox now appears in your Email Accounts list.
💡 The permission-screen trap
If you miss even one Allow or Accept during the OAuth flow, the connection looks like it worked but silently fails to send. When a fresh connection won't send, the first thing to do is disconnect and reconnect, clicking every permission prompt this time. In practice this fixes the majority of dead OAuth connections.
Litemail Microsoft 365 inboxes connect to Smartlead through this same OAuth flow in under three minutes each, and you get the admin credentials to authorize them. For the Google side of the same process, see our Google Workspace Smartlead OAuth guide.
The Settings That Keep the Inbox Healthy
Connecting is half the job. The sending settings inside Smartlead decide whether the inbox stays healthy or burns out. Here's what to set per inbox.
Setting | Recommended value | Why |
|---|---|---|
Daily sending limit | 40 to 50 | Safe cold volume per warmed inbox |
Delay between sends | 180 to 300 sec | Mimics human pace, dodges rate limits |
Warmup (ongoing) | 15 to 20/day | Keeps reputation topped up |
The delay matters more than people think. Microsoft 365 caps sending at 30 messages a minute, and burst sending is itself a spam signal. A 3-to-5-minute gap keeps you clear of both.
After your first campaign day, check the per-inbox stats in Email Accounts. You want open rate above 25% and bounce rate under 2%. If bounces are high, your list needs cleaning — that's not an inbox problem. For what healthy numbers look like, see our inbox health metrics guide.
When the Connection Won't Cooperate
Even done right, OAuth connections hit snags. Here's the quick diagnostic for the common ones.
"Connected" but not sending. Almost always a missed permission during OAuth. Disconnect, reconnect, accept every prompt. If it persists, confirm Authenticated SMTP and IMAP are enabled and that 20 to 30 minutes have passed since you enabled them.
Connection drops after a while. Some setups need periodic re-authentication as OAuth tokens expire. If an inbox goes quiet, reconnect it. This is normal OAuth behavior, not a fault.
High bounces right after connecting. Not a connection issue — a list issue. The inbox is sending fine; your addresses are bad. Verify the list.
Authentication warnings. If Smartlead or your test emails flag SPF, DKIM, or DMARC problems, the connection works but your DNS doesn't. Confirm all three pass with a Gmail Show original check.
One honest note: managing OAuth connections across dozens of inboxes is ongoing work — tokens expire, permissions need re-granting. Starting with inboxes that arrive authentication-ready reduces how much can break. Litemail inboxes ship with SPF, DKIM, and DMARC pre-configured, so the only thing you're managing is the OAuth link itself. For a platform comparison, see our Smartlead alternative guide.
Connect to Smartlead in 3 minutes, not 3 hours. Litemail pre-warmed Microsoft 365 inboxes connect via OAuth with full admin access — SPF/DKIM/DMARC pre-configured, dedicated US and EU IPs, 4 to 12 weeks of warm-up history, from $4.99/inbox. No Basic Auth headaches, verified Good or High in Postmaster within 48 hours. Get Pre-Warmed Inboxes from $4.99 →
About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach. From $4.99/inbox with automated DNS, dedicated US and EU IPs, and full admin access. View pre-warmed inbox plans →
Related reading: Microsoft 365 Cold Email Complete Setup · Connect Google Workspace to Smartlead · Smartlead Alternative 2026 · Inbox Health Metrics · Microsoft 365 SPF Record Fix · Litemail Pre-Warmed Inboxes — Plans and Pricing
The Bottom Line
Microsoft killed Basic Auth for SMTP on March 1, 2026 — Microsoft 365 to Smartlead now requires OAuth, not username-password.
Enable Authenticated SMTP and IMAP in the Microsoft 365 Admin Center first, then wait 20 to 30 minutes before connecting.
During OAuth, accept every permission prompt — one missed Allow makes the connection look live but silently fail.
Set each inbox to 40 to 50 daily sends, a 180 to 300 second delay, and ongoing warmup at 15 to 20 a day.
A “connected but not sending” inbox is almost always a missed permission — disconnect and reconnect.
High bounces after connecting are a list problem, not a connection problem — verify your addresses.
Frequently Asked Questions
How do I connect a Microsoft 365 inbox to Smartlead in 2026?
Use OAuth — Microsoft deprecated Basic Auth for SMTP on March 1, 2026, so username-password no longer works. First enable Authenticated SMTP and IMAP in the Microsoft 365 Admin Center and wait 20 to 30 minutes. Then in Smartlead go to Email Accounts, Connect Mailbox, select Outlook, sign in, and accept every permission prompt.
Why did my Microsoft 365 Smartlead connection stop working in 2026?
Because Microsoft turned off Basic Auth for SMTP on March 1, 2026. Their servers now reject static username-password credentials and only accept OAuth 2.0. If your connection died this year, don't troubleshoot the old SMTP method — reconnect the inbox through OAuth instead, which is the only supported path now.
What sending settings should I use for a Microsoft 365 inbox in Smartlead?
Set the daily sending limit to 40 to 50, the delay between sends to 180 to 300 seconds, and ongoing warmup to 15 to 20 a day. The delay keeps you under Microsoft's 30-messages-per-minute rate limit and mimics human sending. After day one, confirm open rate is above 25% and bounce rate under 2%.
My inbox shows connected but won't send — what's wrong?
Almost always a missed permission during the OAuth flow. Disconnect the inbox and reconnect, clicking Allow or Accept on every screen this time. If it still fails, verify that Authenticated SMTP and IMAP are enabled in your Microsoft 365 Admin Center and that 20 to 30 minutes have passed since you enabled them.
Do I need admin access to connect Microsoft 365 to Smartlead?
Yes, for the one-time step of enabling Authenticated SMTP and IMAP in the Microsoft 365 Admin Center. Without admin rights you can't flip those settings, and OAuth won't complete. Pre-warmed inboxes that come with full admin credentials let you do this yourself instead of waiting on a provider.
Does Litemail work with Smartlead?
Yes. Litemail pre-warmed Microsoft 365 and Google Workspace inboxes connect to Smartlead via OAuth in under three minutes each, and you receive full admin credentials to authorize them. Inboxes arrive with SPF, DKIM, and DMARC pre-configured, dedicated US and EU IPs, and 4 to 12 weeks of warm-up history from $4.99/inbox.
Buy Pre-Warmed Email Inboxes & Domains | Litemail
Buy pre-warmed email accounts, inboxes and domains from $4.99/inbox. Google Workspace & Microsoft 365. OAuth-ready for Smartlead, automated DNS, US & EU IPs, setup in 5 minutes.
No minimum order · Smartlead OAuth-ready · Full admin access
Related reading: Microsoft 365 Complete Setup · Connect Google Workspace to Smartlead · Smartlead Alternative 2026 · Microsoft 365 SPF Record Fix · Litemail Pre-Warmed Inboxes — Plans and Pricing
