Apollo.io is one of the best prospecting tools in existence — and one of the weakest places to actually send from. Its native mailboxes share infrastructure with thousands of other senders, so your deliverability rides on strangers' behavior. Connecting your own Microsoft 365 inbox to Apollo.io fixes that: you keep Apollo's prospecting and sequencing while sending from isolated, reputation-managed infrastructure you control. This is the current setup — OAuth connection after Microsoft's Basic Auth shutdown, the Entra admin-consent step that trips up business accounts, the right per-inbox settings, and why external inboxes beat Apollo's built-in sending every time for real cold volume.
Native Apollo Sending vs Your Own Inboxes
Start with the decision that matters most, because it's the one Apollo's convenience pitch glosses over. Apollo offers two ways to send: its native mailboxes, or your own external inboxes connected to the platform.
Native Apollo sending is convenient and bad for cold email. Those mailboxes share sending infrastructure with thousands of other Apollo users — if other senders on that shared infrastructure spam, your deliverability suffers for it. You have no control over reputation you don't own.
💡 The rule for real volume
For any meaningful cold email volume, connect external Microsoft 365 inboxes to Apollo rather than using native sending. External inboxes give you isolated, controlled, reputation-managed infrastructure. Apollo stays your prospecting and sequencing engine; your own inboxes do the sending. That separation is what protects deliverability.
Apollo doesn't actually send on its own regardless — when you use it for outreach, emails go out through your connected mailbox. So connecting a strong external inbox isn't fighting Apollo; it's using Apollo the way it's meant to work at scale.
The Authentication Change You Have to Know First
Before connecting anything, one 2026 change reshapes how this works. Microsoft deprecated Basic Auth for SMTP on March 1, 2026. Username-and-password SMTP connections no longer work — for Apollo or any other platform.
The only supported way to connect a Microsoft 365 inbox now is OAuth 2.0, the secure flow that authorizes the app without sharing your password. Apollo added Microsoft OAuth support ahead of the deadline, so the connection path is OAuth, full stop.
🚩 If your Apollo mailbox connection broke in 2026
Basic Auth's shutdown is almost certainly why. If you connected a Microsoft 365 inbox to Apollo via SMTP username-password, it stopped working on March 1. Don't debug the old connection — reconnect via Microsoft OAuth, which is the only method Microsoft accepts now. This one change caught a lot of Apollo users off guard.
For the wider picture of what changed, our Microsoft 365 Smartlead integration guide covers the same shift on a different platform.
Connecting Your Microsoft 365 Inbox to Apollo
Here's the OAuth connection flow, including the step that specifically trips up business accounts.
In Apollo, go to Settings → Mailboxes (labeled Email Accounts in some versions), then click Add Email Account or Connect Mailbox.
Select Microsoft 365 / Outlook from the provider list.
Sign in with your inbox credentials via Microsoft OAuth — no password goes into Apollo directly.
Grant the OAuth permissions Apollo requests, then you're redirected back and the mailbox appears connected.
💡 The Entra admin-consent step
If your Microsoft 365 is a business tenant with conditional access, you may hit an “admin approval required” error. A Microsoft 365 admin has to grant tenant-wide consent to Apollo in Entra ID — Enterprise applications → Apollo → Permissions → Grant admin consent. Without this, the OAuth connection fails on managed accounts. This is why full admin access to your inboxes matters: you can grant it yourself instead of waiting on IT.
Inboxes that come with full admin credentials let you clear this step directly. Litemail Microsoft 365 inboxes connect to Apollo via OAuth in under three minutes each, with the admin access to grant consent yourself.
The Settings That Keep Apollo Sending Safe
Connecting is done; now the sending settings decide whether your inboxes stay healthy. Apollo's per-mailbox limits are the key control.
Setting | Recommended | Why |
|---|---|---|
Daily limit per mailbox | 30 to 50 | Safe cold volume per warmed inbox |
Sending schedule | Business hours, weekdays | Human sending pattern |
Scaling method | Add mailboxes | Not higher per-inbox limits |
The scaling point is the one people get wrong. When you need more volume, add more connected mailboxes to the rotation — don't push individual inbox limits above the safe ceiling. Apollo lets you connect many mailboxes precisely so you can spread volume instead of overloading one.
Set sending schedules to business hours in the recipient's timezone so emails arrive when people are at their desks. And keep the ramp gradual on fresh inboxes — start low and build. For the volume math across a mailbox pool, our inbox count guide covers it.
Why the Inbox You Connect Decides Everything
Here's the part that determines your Apollo results more than any sequence tweak. Apollo is a great sequencer, but it can only send through the inbox you give it — and a weak inbox means weak deliverability no matter how good your prospecting is.
Connect a fresh Microsoft 365 inbox with no warm-up and shaky authentication, and Apollo faithfully delivers your carefully built sequences straight to spam. Connect a warmed inbox with clean SPF, DKIM, and DMARC and real reputation, and the same sequences reach the inbox. Apollo is identical either way; the inbox is the variable.
This is the whole case for connecting pre-warmed inboxes to Apollo instead of using native sending or fresh accounts. You get Apollo's prospecting strength plus deliverability that Apollo's shared infrastructure can't provide.
Litemail pre-warmed Microsoft 365 inboxes connect to Apollo via OAuth in minutes, arrive with SPF/DKIM/DMARC pre-configured, 4 to 12 weeks of warm-up history, dedicated US and EU IPs, and verified Good or High Postmaster reputation within 48 hours — the sending layer that turns Apollo's prospecting into actual inbox placement, from $4.99/inbox. For a look at replacing Apollo's native mailboxes specifically, see our cold email infrastructure guide.
Keep Apollo's prospecting, upgrade the sending. Litemail pre-warmed Microsoft 365 inboxes connect to Apollo via OAuth in minutes with full admin access to clear the Entra consent step — SPF/DKIM/DMARC pre-configured, dedicated US and EU IPs, 4 to 12 weeks of warm-up history, from $4.99/inbox. 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 Smartlead Integration · Cold Email Infrastructure Guide · How Many Inboxes You Need · Automate Outlook for B2B · Authentication Checklist · Litemail Pre-Warmed Inboxes — Plans and Pricing
The Bottom Line
For real cold volume, connect your own external Microsoft 365 inboxes to Apollo — native Apollo sending shares infrastructure with thousands of senders.
Microsoft killed Basic Auth for SMTP on March 1, 2026 — connect via Microsoft OAuth, not username-password.
Business tenants may need a Microsoft 365 admin to grant Apollo tenant-wide consent in Entra ID.
Set each mailbox to 30 to 50 sends a day and scale by adding mailboxes, not by raising per-inbox limits.
Apollo can only send as well as the inbox you connect — a weak inbox delivers great sequences to spam.
Pre-warmed inboxes give Apollo the reputation and authentication its shared native infrastructure can't.
Frequently Asked Questions
How do I connect a Microsoft 365 inbox to Apollo.io in 2026?
Use Microsoft OAuth — Basic Auth for SMTP was deprecated March 1, 2026, so username-password no longer works. In Apollo, go to Settings, Mailboxes, Add Email Account, select Microsoft 365, and sign in via OAuth. Business tenants may need a Microsoft 365 admin to grant Apollo tenant-wide consent in Entra ID before the connection succeeds.
Should I use Apollo's native mailboxes or connect my own?
Connect your own for any real cold volume. Apollo's native mailboxes share sending infrastructure with thousands of other users, so your deliverability depends on strangers' behavior. External Microsoft 365 inboxes give you isolated, reputation-managed infrastructure you control, while Apollo stays your prospecting and sequencing engine. Apollo sends through your connected mailbox either way.
Why does my Apollo mailbox connection say admin approval required?
Your Microsoft 365 is a business tenant with conditional access, so a Microsoft 365 admin must grant Apollo tenant-wide consent in Entra ID — under Enterprise applications, Apollo, Permissions, Grant admin consent. Without it, the OAuth connection fails on managed accounts. Having full admin access to your inboxes lets you grant this yourself instead of waiting on an IT team.
How many emails can I send per mailbox in Apollo?
Keep each warmed mailbox to 30 to 50 cold sends a day. Apollo lets you connect many mailboxes precisely so you can spread volume safely — when you need more capacity, add mailboxes to the rotation rather than raising individual limits above the safe ceiling. Ramp fresh inboxes gradually from a low daily count before reaching full volume.
Does the inbox I connect to Apollo affect deliverability?
Enormously — it's the biggest factor. Apollo can only send through the inbox you give it, so a fresh inbox with no warm-up and weak authentication delivers your sequences to spam no matter how good your prospecting is. A warmed inbox with clean SPF, DKIM, and DMARC and real reputation lands the same sequences in the inbox.
Does Litemail work with Apollo.io?
Yes. Litemail pre-warmed Microsoft 365 and Google Workspace inboxes connect to Apollo via OAuth in under three minutes each, with full admin access to clear the Entra consent step. They arrive with SPF/DKIM/DMARC pre-configured, 4 to 12 weeks of warm-up history, dedicated US and EU IPs, and verified reputation within 48 hours, 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 Apollo, automated DNS, US & EU IPs, setup in 5 minutes.
No minimum order · Apollo OAuth-ready · Full admin access
Related reading: Microsoft 365 Smartlead Integration · Cold Email Infrastructure Guide · Automate Outlook for B2B · Authentication Checklist · Litemail Pre-Warmed Inboxes — Plans and Pricing
