Outlook & Microsoft 365 Sending Limits in 2026 (Full Tables + Safe Volumes)
Microsoft 365 (Exchange Online) mailboxes can send to 10,000 recipients per day over a 24-hour sliding window, with a default cap of 500 recipients per message
Microsoft 365 (Exchange Online) mailboxes can send to 10,000 recipients per day over a 24-hour sliding window, with a default cap of 500 recipients per message and a hard limit of 30 messages per minute for authenticated SMTP submission — as documented by Microsoft, which notes these values can change, so verify current figures before building on them. Consumer Outlook.com accounts get far less: Microsoft documents 5,000 daily recipients for Microsoft 365 subscribers and explicitly says free-account limits are “lower” without publishing a number. For cold email, none of those ceilings are the real constraint — 30-50 sends per mailbox per day is the volume that keeps complaint rates survivable.
TL;DR: Microsoft Sending Limits at a Glance
| Limit | Microsoft 365 / Exchange Online | Outlook.com (consumer) |
|---|---|---|
| Recipients per day | 10,000 (24-hour sliding window) | 5,000 for M365 subscribers; free accounts “lower,” not published |
| Recipients per message | 500 default (admin-customizable 1-1,000) | 500 |
| “Non-relationship” recipients per day | — | 1,000 (people you’ve never emailed) for M365 subscribers |
| SMTP submission rate | 30 messages/minute, max 3 concurrent connections | — |
| Tenant external recipient limit (TERRL) | Scales with licenses; trial tenants 5,000 external/day | — |
| onmicrosoft.com domains | 100 external recipients per tenant per 24h | — |
| High-volume sender rules | 5,000+ msgs/day to Microsoft consumer mail: SPF + DKIM + DMARC required (since May 5, 2025) | Same threshold applies to mail arriving at these inboxes |
| Limit exceeded behavior | Sending blocked until window drains; NDRs 550 5.7.233 / 5.7.236 / 5.7.515 | Temporary block; new accounts start with low quotas |
| Safe cold email volume | 30-50/day per mailbox | Do not use for cold email |
Primary sources: Microsoft’s Exchange Online limits, outbound spam limits troubleshooting, and Outlook.com sending limits pages.
What Are Microsoft’s Sending Limits in 2026?
Like Gmail, Microsoft enforces two distinct layers, and they fail differently.
Layer 1: hard service limits. Per-mailbox recipient quotas, per-message recipient caps, SMTP rate limits, and — unique to Microsoft — tenant-wide external recipient limits. Cross one and Exchange Online either delays your mail or bounces it with a specific NDR code. Microsoft’s limits page carries an explicit disclaimer that applied limits “may differ depending on how long the organization has been enrolled in the service” and that changes take time to propagate — which is why every number in this article should be read as “as documented by Microsoft, verify current values.”
Layer 2: sender reputation requirements. Effective May 5, 2025, Microsoft requires high-volume senders — those sending 5,000 or more messages per day to Outlook.com, Hotmail, Live.com, and other Microsoft consumer addresses — to authenticate with SPF, DKIM, and DMARC. Microsoft initially routed non-compliant mail to Junk, then hardened the policy to outright rejection. This mirrored Google and Yahoo’s February 2024 requirements and completed the picture: all three major inbox providers now enforce authentication as a condition of delivery.
If you’ve read our companion guide to Gmail sending limits, note the asymmetry in how the headline numbers are counted: Google’s headline cap is 2,000 messages per day, while Microsoft’s is 10,000 recipients per day. Comparing “2,000 vs 10,000” without that distinction is how senders talk themselves into volumes Microsoft never promised them.
Microsoft 365 (Exchange Online) Limits: The Full Table
The figures below come from Microsoft’s Exchange Online service description and the cleaner consolidated table on the outbound sending limits troubleshooting page, current as of mid-2026:
| Limit type | Value | Behavior |
|---|---|---|
| Recipient rate limit | 10,000 recipients per day per mailbox | 24-hour sliding window; hard limit “enforced at the service level and can’t be increased” |
| Recipient limit per message | 500 (default) | Admin-customizable from 1 to 1,000 in the Exchange admin center or PowerShell |
| Message rate (SMTP AUTH) | 30 messages per minute | Excess submissions are delayed and carried over to following minutes, not rejected |
| Concurrent SMTP connections | 3 | A fourth connection receives 432 4.3.2 Concurrent connections limit exceeded |
| Tenant External Recipient Rate Limit (TERRL) | Scales with license count; trial tenants: 5,000 external recipients/day | Exceeding returns NDR 550 5.7.233 |
| onmicrosoft.com (MOERA) domains | 100 external recipients per tenant per 24h rolling window | Exceeding returns NDR 550 5.7.236 |
Details worth internalizing:
The 10,000/day limit applies per mailbox, uniformly across plans. Business Basic, Business Premium, E3, E5, and standalone Exchange Online plans all carry the same recipient rate limit. Unlike Google’s standard-vs-trial distinction, Microsoft doesn’t publish different per-mailbox numbers by SKU — the plan differences show up at the tenant level instead.
It’s a sliding window, not a midnight reset. Once you hit 10,000 recipients, “messages can’t be sent from the mailbox until the number of recipients that were sent messages in the past 24 hours drops below the limit.” Your capacity drains back gradually as old sends age out of the window.
Recipient counting has a quirk. A distribution group stored in your organization’s address book counts as one recipient; a group in your personal contacts counts each member individually.
The 500-per-message default is adjustable — in both directions. Admins can set it anywhere from 1 to 1,000. For cold outreach this is academic (you should be sending one-to-one messages), but it matters for the occasional newsletter-style internal send.
For the operational playbook on running outreach through Microsoft’s stack, see our Outlook and Microsoft 365 cold email guide.
The 30-Messages-Per-Minute Rule (and Why Your Tool Must Respect It)
Authenticated SMTP client submission — what most sending tools use when connected to smtp.office365.com — carries its own throttle, documented on Microsoft’s SMTP submission improvements page: 30 messages per minute per mailbox, plus a maximum of three concurrent connections.
The failure mode is gentler than a bounce, and that’s exactly why it catches people. Per Microsoft: “If the mailbox exceeds the per minute limit, then email delivery delays occur. Any excess in message submissions is throttled and successively carried over to the following minutes.” A tool that fires 200 messages in a burst doesn’t get 170 rejections — it gets a growing invisible backlog, messages arriving minutes or hours late, and follow-up timing that silently drifts.
A well-behaved sending platform paces Microsoft mailboxes with human-like gaps between sends rather than bursting to the rate limit. If your current tool’s idea of throttling is “retry until it goes through,” that’s a sign it was built for throughput, not account safety.
Outlook.com Consumer Limits: What Microsoft Actually Documents
Microsoft’s official Outlook.com sending limits page is more candid than most summaries of it. What it documents — for Microsoft 365 subscribers using a consumer Outlook.com account:
- 5,000 recipients per day
- 500 recipients maximum per message
- 1,000 “non-relationship recipients” per day — Microsoft’s term for “someone you’ve never sent email to before,” which is a precise description of every cold email recipient
And three statements that matter more than the numbers:
- Free accounts get less, and Microsoft won’t say how much less. The page states limits “may vary based on usage history and will be lower for non-subscribers.” The widely-circulated “300 messages per day” figure for free Outlook.com is not on Microsoft’s current page — treat it as legacy folklore, not a documented limit.
- New accounts start with a deliberately low quota. Microsoft: “If you recently created a new Outlook.com account, a low sending quota is a temporary restriction which is upgraded to the maximum limit as soon as you establish credibility in the system.” That is Microsoft describing warmup as a platform mechanic.
- The non-relationship cap is the cold-email killer. Even a subscriber-tier consumer account caps first-contact recipients at 1,000/day — and unsolicited commercial mail from consumer accounts violates the Microsoft Services Agreement well before you approach that line.
The conclusion mirrors the Gmail one: consumer mailboxes are for personal mail. Cold outreach belongs on a custom domain you own, hosted on Microsoft 365 (or Google Workspace), where reputation accrues to an asset you control.
Tenant-Level Throttling: TERRL and the onmicrosoft.com Trap
Two Microsoft-specific behaviors blindside senders who sized their program on per-mailbox math alone.
TERRL — the Tenant External Recipient Rate Limit. Introduced via Exchange Online’s tenant outbound limits rollout, TERRL caps how many external recipients your entire tenant can message per day. Per Microsoft, it “scales automatically with the number of licenses in the organization,” and trial tenants get a default of 5,000 external recipients per day. Exceed it and mail bounces with 550 5.7.233. Microsoft does not publish the per-license formula — your tenant’s actual number is visible in the Exchange admin center’s Tenant Outbound External Recipients report, so check yours rather than assuming. The practical implication: stacking 40 mailboxes into one small tenant does not buy you 40 × 10,000 of external capacity.
The onmicrosoft.com throttle. Mail sent from your default *.onmicrosoft.com address (the domain every new tenant gets before adding a custom one) is limited to 100 external recipients per tenant per 24-hour rolling window, with excess bounced as 550 5.7.236. Microsoft did this deliberately to stop abuse from disposable tenants. If you spun up a tenant yesterday and your “test campaign” died at a few dozen sends, this is why — add and verify a custom domain before sending anything that matters.
Microsoft’s Sender Requirements for High-Volume Senders (May 2025, Enforced Through 2026)
Microsoft’s equivalent of the Google/Yahoo bulk-sender rules arrived on May 5, 2025 and is documented on the official NDR 550 5.7.515 support page. Senders of 5,000 or more messages per day to Microsoft consumer email (Outlook.com, Hotmail, Live.com, MSN) must:
- Pass both SPF and DKIM — “Both SPF and DKIM checks must pass.”
- Publish a DMARC record — minimum
v=DMARC1; p=none, with at least one of SPF or DKIM aligned to the visible From: domain. - Follow the accompanying best practices: a valid, reply-capable From/Reply-To address, a clearly visible unsubscribe option, and ongoing list hygiene that removes invalid and bouncing addresses.
Enforcement escalated fast: Microsoft first routed non-compliant high-volume mail to Junk, then moved to rejecting it outright with “550; 5.7.515 Access denied, sending domain does not meet the required authentication level.”
Combined with Google and Yahoo’s requirements, the industry floor in 2026 is simply: SPF + DKIM + DMARC on every sending domain, at any volume, full stop. If your DNS records aren’t airtight, start with our SPF, DKIM and DMARC compliance guide before sending another campaign.
What Happens When You Hit Microsoft’s Limits
Each ceiling fails with its own signature, which makes diagnosis straightforward if you know the codes:
| Symptom | What you hit |
|---|---|
| Sends delayed, arriving over following minutes | 30/minute SMTP throttle — excess is queued, not bounced |
432 4.3.2 Concurrent connections limit exceeded |
More than 3 simultaneous SMTP connections |
| Mailbox suddenly can’t send; recovers within a day | 10,000-recipient sliding window exhausted |
550 5.7.233 NDRs across multiple mailboxes |
Tenant-level TERRL exhausted |
550 5.7.236 NDRs |
Sending from an onmicrosoft.com address |
550 5.7.515 NDRs on mail to Outlook/Hotmail |
High-volume sender authentication failure (SPF/DKIM/DMARC) |
| Account restricted from sending entirely | Outbound spam controls flagged the mailbox — requires admin unblock and a genuine behavior change |
The correct response to any of these is the same as on Gmail: stop, identify which layer fired, and restart lower and slower. Repeatedly bouncing off Microsoft’s limits is itself a reputation signal — Exchange Online Protection remembers senders that behave like scripts.
Safe Cold Email Volumes on Microsoft 365
Microsoft will transmit 10,000 recipients a day for you. Its consumer inboxes will not forgive you for trying. The binding constraint on cold email is never the documented cap — it’s complaint rate, engagement, and the outbound spam controls watching every mailbox in your tenant.
Practitioner consensus for Microsoft 365 mailboxes matches what works on Google:
| Mailbox state | Safe cold email volume per day |
|---|---|
| Brand-new mailbox (week 1-2) | 0 cold emails — warmup only |
| Warming (weeks 3-4) | 10-20, alongside continued warmup |
| Established (2-3 months, clean metrics) | 30-50 |
| Mature, pristine list quality | Up to ~100, as a ceiling, not a target |
That’s 0.3-1% of the documented recipient cap, and the gap is deliberate: it’s your margin against a bad list segment or a content variant that trips filters. Need more volume? Add mailboxes and domains — while respecting TERRL and keeping each mailbox boringly low — rather than pushing any single sender toward its ceiling. And remember the new-tenant realities stack: a fresh tenant has a trial-tier TERRL, an unwarmed domain, and unwarmed mailboxes. There is no configuration change that skips the earning-trust phase.
Warmup for Outlook and Microsoft 365 Mailboxes
Microsoft tells you directly that new senders start throttled and earn capacity “as soon as you establish credibility in the system.” Warmup is how you establish it deliberately instead of accidentally: a steady, growing stream of sends that get opened, replied to, and rescued from Junk, building the engagement history that Exchange Online Protection and Outlook’s filters weigh.
If warmup is new territory, start with our complete email warmup guide, then the Outlook-specific comparison of the top warmup tools for Outlook and Microsoft 365. For timeline expectations — how many weeks until a new M365 mailbox can carry real campaign volume — see How Long Does Email Warmup Take?
WarmySender’s A.H.D.E. warmup handles this automatically on every plan, including for Outlook OAuth-connected mailboxes: adaptive daily targets from 10 up to 100 emails per day, ramp controls, human-like pacing that stays far inside the 30/minute SMTP throttle, and engagement tracking so you can see credibility building before you bet campaigns on it.
Monitoring: SNDS and JMRP
Microsoft’s postmaster tooling is older and rougher than Google’s, but it’s free and it’s the only official window you get:
- SNDS (Smart Network Data Services) — Microsoft’s sender portal at sendersupport.olc.protection.outlook.com/snds shows IP-level data for sending IPs you register: volume observed, complaint rates, spam-trap hits, and filter status. Note that Microsoft has been migrating this portal to new infrastructure, so verify the current URL if the portal has moved by the time you read this.
- JMRP (Junk Mail Reporting Program) — Microsoft’s complaint feedback loop. Enroll (via SNDS) and every time an Outlook.com user marks your mail as junk, the complaint is forwarded to an address you designate, so you can suppress that recipient immediately and spot problem campaigns early.
Two caveats: SNDS is IP-based, which makes it most useful for dedicated infrastructure and less granular for shared M365 IPs, and Microsoft publishes no consumer-side equivalent of Gmail’s domain-reputation dashboard. That makes your own metrics — bounce codes, reply rates, spam-folder placement checks — a bigger share of your Microsoft monitoring than they are on Google. Our cold email deliverability checklist covers the full monitoring stack.
Frequently Asked Questions
How many emails can Microsoft 365 send per day?
Exchange Online enforces a recipient rate limit of 10,000 recipients per day per mailbox over a 24-hour sliding window, as documented by Microsoft (verify current values — Microsoft notes limits can change). Since cold email is one recipient per message, that’s effectively up to 10,000 messages — but tenant-level limits (TERRL) and, far more importantly, complaint-rate realities make 30-50 cold sends per mailbox per day the sane operating number.
What is the Outlook.com daily sending limit for free accounts?
Microsoft doesn’t publish one. Its official page documents 5,000 daily recipients, 500 per message, and 1,000 “non-relationship” recipients per day for Microsoft 365 subscribers, and says only that limits are “lower” for non-subscribers and vary with usage history. The often-quoted “300 per day” for free accounts is not on Microsoft’s current documentation. Either way, consumer Outlook.com accounts are the wrong vehicle for cold email.
What is Microsoft’s 30 messages per minute limit?
Authenticated SMTP client submission (smtp.office365.com) is throttled to 30 messages per minute per mailbox, with a maximum of three concurrent connections. Excess messages aren’t bounced — they’re delayed and carried over into following minutes, which quietly wrecks send timing for tools that burst. Sending platforms should pace Microsoft mailboxes well under this rate.
Does Microsoft require SPF, DKIM, and DMARC?
For high-volume senders, yes — since May 5, 2025, domains sending 5,000+ messages per day to Microsoft consumer addresses (Outlook.com, Hotmail, Live) must pass SPF and DKIM and publish at least a p=none DMARC record, or see mail rejected with error 550 5.7.515. In practice, every serious sender should meet this standard at any volume: Google and Yahoo enforce equivalent requirements, and unauthenticated mail is effectively undeliverable across all major providers in 2026.
Why can’t my brand-new Microsoft 365 tenant send external email properly?
Three stacked restrictions hit new tenants: the default onmicrosoft.com domain is capped at 100 external recipients per tenant per day (use a verified custom domain instead), trial tenants carry a TERRL of 5,000 external recipients per day, and individual new mailboxes have no sending reputation yet. The fix is sequence, not settings: add a custom domain, authenticate it with SPF/DKIM/DMARC, warm each mailbox for several weeks, and only then layer in campaign volume.
Can I raise Microsoft 365 sending limits?
Mostly no. Microsoft states the recipient rate limit and message rate limit “are hard limits enforced at the service level and can’t be increased.” Admins can adjust the per-message recipient cap (1 to 1,000), and tenant-level TERRL grows automatically as you add licenses. For volume beyond mailbox limits, Microsoft points senders to dedicated bulk-email services — and for cold outreach, the right answer is horizontal scale across warmed mailboxes, each kept far below its documented ceiling.
The Bottom Line
Microsoft’s documented numbers — 10,000 recipients/day per mailbox, 500 per message, 30 per minute — are generous on paper and largely irrelevant to cold email in practice. The limits that actually shape your program are the ones that don’t appear in the headline table: the tenant-wide TERRL, the 100-recipient onmicrosoft.com throttle, the May 2025 authentication mandate, and above all the complaint math that makes 30-50 daily sends per warmed mailbox the professional standard. Build for those, hedge every hard number against Microsoft’s own “values may change” disclaimer, and the service limits will never be what stops you.
WarmySender runs this discipline for you across both Microsoft and Google mailboxes: A.H.D.E. adaptive warmup on every plan, paced campaign sending with multi-step sequences, A-Z variant testing and suppression lists, LinkedIn and Instagram outreach add-ons at $20/seat, and an open REST API with webhooks that connects to any AI agent, Zapier, Make, or n8n. Plans start at $14.99/month with a 7-day free trial and 55% off annual billing — get your Outlook mailboxes warming at warmysender.com.