On March 1, 2026, a lot of Quickmail campaigns running on Outlook accounts died overnight. No warning beyond a bounce most people didn't read: 550 5.7.30. Microsoft had finally switched off Basic Authentication for SMTP, and every Microsoft 365 inbox for Quickmail connected with a username and password stopped sending. App passwords stopped working too. If you set up your inbox the old way, it's not throttled — it's locked out.
That single change rewrote how you connect Microsoft 365 to Quickmail. SMTP-with-a-password is gone. OAuth is the only path now.
My take: this is actually good for deliverability, because it forces the cleaner setup you should have been running anyway — proper authentication, real inbox ownership, no fragile passwords.
By the end, you'll have a working OAuth connection, safe sending limits, correct DNS, and a fix for the 550 5.7.30 error if you're staring at one right now.
TL;DR
💡 The short version
Connecting a Microsoft 365 inbox for Quickmail in 2026 means OAuth, not SMTP — Microsoft disabled Basic Auth for SMTP on March 1, 2026, so username/password and app passwords no longer work (you'll see 550 5.7.30). In Quickmail, add the account via the Microsoft/OAuth flow, sign in with the specific inbox, grant send and read permissions, then send a test and confirm SPF, DKIM, and DMARC all show PASS. Keep cold volume to 20–30 sends per inbox a day and 3–4 inboxes per domain. Fresh inboxes still need 4–8 weeks of warm-up; pre-warmed inboxes connect via OAuth and send on day one at 94%+ placement.
What Microsoft 365 Needs Before You Connect
Don't touch Quickmail until three things are true. Skipping any of them is why connections fail or land in spam.
A licensed Microsoft 365 mailbox on your own domain. Not a free Outlook.com address — you need a Workspace-grade mailbox to sign DKIM with your domain and see reputation.
SPF, DKIM, and DMARC live on the sending domain. All three, aligned, before the first send. A missing DKIM record means authentication fails no matter how the inbox connects. See the SPF, DKIM, DMARC setup.
Modern Auth (OAuth) enabled at the tenant. Since Basic Auth is off, the tenant must allow OAuth connections — which it does by default in 2026, but verify if you're on an older tenant.
And the rule that saves you later: never use your company's primary domain for cold outreach. Register separate sending domains so a reputation problem can't reach your real mail.
Connecting Microsoft 365 to Quickmail via OAuth
Quickmail supports Microsoft 365, Outlook, and Exchange over OAuth. The flow takes a couple of minutes per inbox.
In Quickmail, go to your inbox settings and choose to add an email account.
Select the Microsoft / Office 365 option — this triggers the OAuth flow, not an SMTP form.
You'll be redirected to Microsoft's OAuth consent screen. Sign in with the specific inbox you're connecting — not your admin account.
Grant the requested permissions — typically send mail, read mail, and manage settings. These let Quickmail send and sync replies.
Quickmail confirms the connection. Send a test email to a Gmail address you control.
Open the test, view the original/headers, and confirm SPF: PASS, DKIM: PASS, DMARC: PASS. Any FAIL means stop and fix DNS before sending campaigns.
💡 OAuth over SMTP, always
Even where a platform still offers an SMTP option, use OAuth. OAuth connections are more stable, more secure, and far less likely to drop mid-campaign. SMTP with app passwords is exactly what Microsoft just disabled — building on it now is building on something already deprecated.
Safe Sending Limits on Microsoft 365
Microsoft 365 publishes generous limits. They are not cold-email limits. Here's the gap that matters.
Limit | Microsoft's number | Safe for cold outreach |
|---|---|---|
Recipients per day | 10,000 | 20–30 per inbox |
Recipients per message | 500 | 1 (personalised) |
Messages per minute | 30 | Well below |
New (non-relationship) contacts/day | ~1,000 | Your real ceiling |
The number that bites cold senders first is the roughly 1,000 brand-new contacts a day — cold outreach is all new contacts. Stay far under it: cap each inbox at 20–30 cold sends a day and run 3–4 inboxes per domain. Need more volume? Add inboxes, don't push one harder. For the full picture, see the Microsoft 365 cold email troubleshooting guide.
Warm-Up: Quickmail MailFlow vs Pre-Warmed Inboxes
A freshly connected Microsoft 365 inbox has no sending history, and OAuth doesn't change that. You still need reputation before you send cold. Two ways to get it.
Quickmail includes MailFlow, an auto-warmer that sends and replies between accounts to build engagement signals. It works, with two caveats: warm-up now takes 4–8 weeks to do properly, and shared-pool warmup signals are discounted more than they used to be, so mix in real sends as reputation builds. The alternative is to start with inboxes that already have weeks of genuine history — no warm-up wait at all.
✅ The shortcut
Litemail pre-warmed Microsoft 365 inboxes arrive with 4–12 weeks of real sending history, SPF/DKIM/DMARC automated, Microsoft SNDS Green, and Postmaster reputation Good or High within 48 hours. Connect them to Quickmail via OAuth and start campaigns on day one — from $4.99/inbox with dedicated US and EU IPs. See how the warm-up history works.
Fixing the 550 5.7.30 Error
If your Quickmail sends started bouncing with 550 5.7.30, the cause is almost always the same, and the fix is quick.
That error means Basic Authentication is not supported for client submission — Microsoft turned it off. Your inbox is connected the old way, over SMTP with a password or app password. Reconnecting over OAuth fixes it: remove the old SMTP connection in Quickmail, add the account again through the Microsoft/OAuth flow, and re-authenticate. Sends resume once the token is in place.
🚩 If OAuth still fails
A 535 5.7.3 or an authentication error after OAuth usually means the tenant is blocking the connection or the inbox lacks send permission. Confirm Modern Auth is enabled at the tenant, that you signed in with the inbox itself (not the admin account), and that send permissions were granted. If DKIM shows FAIL on a test send, the problem is DNS, not auth — fix the record first.
Use Instantly Smarter — Replace Instantly Accounts With Owned Inboxes
Quickmail and Instantly both connect via OAuth — but if you're on Instantly Accounts, those inboxes are rented and SMTP-locked, and the warm-up history leaves when you do. Owned inboxes move with you between platforms.
Keep your workflow, own the inboxes. Replace rented accounts with Litemail pre-warmed inboxes — full admin access, dedicated US and EU IPs, $4.99/inbox. Connect to Quickmail or Instantly via OAuth in 3 minutes. Lower cost, better deliverability, no lock-in. Get Pre-Warmed Inboxes from $4.99 →
Works with Quickmail and Instantly via OAuth · Full admin access · Dedicated US and EU IPs · No minimum order.
Related reading: Microsoft 365 Cold Email Troubleshooting for B2B Sales · Outlook Cold Email Troubleshooting — 9 Fixes · Pre-Warmed Inbox for Quickmail Campaigns 2026 · Microsoft 365 Cold Email for Startups · Litemail Pre-Warmed Inboxes — Plans and Pricing
The Bottom Line
A Microsoft 365 inbox for Quickmail must connect via OAuth in 2026 — Basic Auth for SMTP was disabled on March 1, 2026.
The 550 5.7.30 error means an old SMTP/password connection — reconnect over OAuth to fix it.
Set SPF, DKIM, and DMARC before sending, and confirm all three PASS on a test email.
Cap cold volume at 20–30 sends per inbox a day; your real ceiling is the ~1,000 new-contact limit, not 10,000.
Run 3–4 inboxes per domain and never send cold from your company's primary domain.
Fresh inboxes need 4–8 weeks of warm-up; pre-warmed inboxes connect via OAuth and send on day one.
Frequently Asked Questions
How do I connect a Microsoft 365 inbox to Quickmail in 2026?
Use OAuth. In Quickmail, add an email account, choose the Microsoft/Office 365 option, sign in with the specific inbox on Microsoft's consent screen, and grant send and read permissions. SMTP with a password no longer works because Microsoft disabled Basic Auth on March 1, 2026.
Why am I getting a 550 5.7.30 error in Quickmail?
That error means Basic Authentication is not supported for client submission — your inbox is connected over SMTP with a password or app password, which Microsoft turned off. Remove the SMTP connection and re-add the account through the OAuth flow to fix it.
Can I still use app passwords for Microsoft 365 cold email?
No. App passwords rely on Basic Auth, which Microsoft disabled in 2026, and they can't be regenerated. Every connection to Microsoft 365 for sending must now use OAuth 2.0.
How many emails can I send per Microsoft 365 inbox in Quickmail?
For cold outreach, 20–30 sends per inbox per day. Microsoft's 10,000/day cap is a system limit, and the real ceiling is the ~1,000 brand-new-contact limit. Add inboxes to scale rather than pushing one inbox harder.
Do I need to warm up a Microsoft 365 inbox before using it in Quickmail?
Yes, if it's fresh — warm-up takes 4–8 weeks to do properly, and Quickmail's MailFlow can handle it if you mix in real sends. A pre-warmed inbox skips the wait: it connects via OAuth and sends on day one with reputation already built.
Should I use SMTP or OAuth for Quickmail with Microsoft 365?
OAuth, without exception. It's more stable and secure, and SMTP with Basic Auth is disabled anyway. Litemail pre-warmed Microsoft 365 inboxes connect to Quickmail via OAuth in minutes, with SPF, DKIM, and DMARC already set and dedicated US and EU IPs.
Buy Pre-Warmed Email Inboxes & Domains | Litemail
Buy pre-warmed email accounts, inboxes and domains from $4.99/inbox. Google Workspace & Microsoft 365. Automated DNS, US & EU IPs. Setup in 5 minutes.
Related reading: Microsoft 365 Cold Email Troubleshooting for B2B Sales · Outlook Cold Email Troubleshooting — 9 Fixes · Pre-Warmed MS365 Inboxes — Warm-Up History Explained · Best Pre-Warmed Inbox Providers 2026 (Ranked) · Litemail Pre-Warmed Inboxes — Plans and Pricing
Skip the Warm-Up — Pre-Warmed Microsoft 365 for Quickmail
Litemail delivers pre-warmed Microsoft 365 inboxes that connect to Quickmail over OAuth in minutes — SPF/DKIM/DMARC automated, Microsoft SNDS Green, Postmaster Good or High within 48 hours, dedicated US and EU IPs, full admin access. No Basic Auth headaches, no 4–8 week warm-up, no 550 errors. From $4.99/inbox, delivered in 24 hours. Also works with Instantly, Smartlead, and Lemlist.
Get Pre-Warmed Inboxes from $4.99 →
OAuth-ready · SPF, DKIM, DMARC pre-set · SNDS Green · US and EU IPs · Setup in 5 minutes
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 Troubleshooting for B2B Sales · Outlook Cold Email Troubleshooting — 9 Fixes · Pre-Warmed MS365 Inboxes — Warm-Up History Explained · SPF, DKIM, DMARC on Pre-Warmed Inboxes · Pre-Warmed Inbox for Quickmail Campaigns 2026 · Litemail Pre-Warmed Inboxes — Plans and Pricing
