Outlook Mail Merge Limit: How to Send 1000+ Emails Without Blocks
You write a campaign, hit Send on 1,200 personalized emails, and somewhere around recipient 500 Outlook stops cooperating. New messages disappear into the Outbox. A few hours later you get a polite NDR titled SubmissionQuotaExceeded. Welcome to Microsoft's mail-merge limit.
This post covers exactly what the limit is, why it exists, what triggers it, and the realistic ways to send 1,000+ personalized emails per day from an Outlook account without getting throttled or — worse — flagged for abuse.
The actual numbers
Microsoft publishes their official limits at learn.microsoft.com/exchange-online-limits. Stripped to the essentials:
| Account type | Recipients/day | Messages/min | Recipients/message |
|---|---|---|---|
| Outlook.com (free) | ~500 | ~30 | 50 |
| Microsoft 365 Personal / Family | ~500 | ~30 | 500 |
| Microsoft 365 Business Basic / Standard / Premium | 10,000 | 30 | 500 |
| Exchange Online (standalone) | 10,000 | 30 | 500 |
| New Microsoft 365 tenant (first 30 days) | 1,000–2,000 (graduated) | 30 | 500 |
| Trial / education tenants | Reduced — varies | 30 | 500 |
Three numbers in tension:
- Recipients per day — your hard ceiling. Hitting this returns
SubmissionQuotaExceeded. - Messages per minute — throughput throttle. Going above results in
RecipientRateLimitedTemporarily; messages queue and retry. - Recipients per message — caps the To/CC/BCC fields on a single message.
For a personalized campaign you're sending one message per recipient (one address in To:), so the per-message cap doesn't matter. The two that do are per day and per minute.
Why these limits exist
Microsoft is balancing two pressures: legitimate business email throughput vs. spam/phishing prevention. If a compromised account could send 100,000 emails/hour, criminals would weaponise every breach. The 30/minute cap is anti-abuse infrastructure. The 10,000/day cap is policy.
The graduated limits for new tenants are about reputation. A brand-new domain with no email history that suddenly fires 10,000 messages looks exactly like a spam campaign. Microsoft restricts the first 30 days specifically so legitimate domains build a slow, normal-looking sending pattern.
Important. Microsoft's limits are not the same as your inbox-placement limits. You can technically send 9,999 cold emails on day 30 from a fresh tenant — and watch every single one go to spam. Anti-spam filters at the receiving end (Gmail, Yahoo, corporate domains) have their own thresholds, and they're stricter than Microsoft's.
What actually happens when you exceed the limit
Per-day limit
Microsoft returns a non-delivery report (NDR) with code 5.2.121 RESOLVER.RST.RecipSizeLimit or, more commonly, 5.7.1 SubmissionQuotaExceeded. The message disappears from your Outbox and lands in your Sent Items as "queued." Future sends within the 24-hour window get the same treatment until the counter resets — for most tenants, at the top of the UTC day.
Your account is not suspended. You don't get an email from Microsoft. The only visible effect is that nothing is sending and you eventually find the NDR if you go looking.
Per-minute limit
Microsoft returns 4.7.500 Server busy and the message stays in the queue. Outlook (or your sending tool) is expected to retry after a short delay — typically 30–120 seconds. If your tool doesn't retry, those messages just hang.
Burst patterns trigger separate anti-abuse systems
Even if you stay under the published limits, sending 200 identical messages in 10 seconds is a pattern that Microsoft's anti-abuse layer flags as automated. The penalty is escalating: temporary throttle first, soft-block on the account second, full suspension on repeat offenses. Avoiding bursts isn't optional.
How to send 1000+ emails without hitting the wall
Stay below the per-minute throughput
Microsoft's documented cap is 30 messages/minute. The practical cap for cold outreach is much lower — sending 30 personalized messages in 60 seconds still looks robotic to anti-abuse systems. Aim for 1 message every 1–2 seconds instead. That gives you about 1,800 messages/hour, well under throughput limits and looks like a person who's typing genuinely fast.
Tools like OutMass bake this in automatically — there's a 1-second delay between sends by default, and the schedule is enforced server-side so you can't accidentally trip over it.
Spread campaigns across multiple days
If your list is 5,000 recipients and you're on a Microsoft 365 Business plan (10,000/day cap), you can technically send the whole thing in a day. You shouldn't. A 5,000-message daily volume from an account that normally sends 50 messages/day is exactly the pattern that lights up Microsoft's anti-abuse dashboards. Split the list:
- Day 1: 500 messages (warmup)
- Day 2: 1,000
- Day 3: 1,500
- Day 4: 2,000
That's a normal sales operator's sending pattern. Microsoft doesn't blink, recipient mail servers don't blink, your reputation builds.
Personalize past the first line
Outlook's anti-spam system has a hash-similarity detector. If 1,000 messages have the same body except for {{firstName}} at the top, that's still ~99% the same — it triggers similarity flags. Effective personalization changes more than a name:
- Different first sentences ("I noticed you just launched X" vs "Saw your team's recent post on Y").
- Reference different facts about the recipient's company.
- Vary the call-to-action between two or three options (a direct meeting, a reply with a question, a link).
This is where AI email writers shine. OutMass's AI Writer (Claude-powered) generates per-recipient first lines from a CSV column — turning a "1000-message identical send" into "1000 individually-written messages" without 1000 hours of work.
Use a real, working unsubscribe link
One spam complaint per 1,000 messages is normal. Three per 1,000 starts ringing alarms. The fastest way to lower complaints is to make unsubscribe trivial — a one-click link in every message. Recipients who would have hit "Mark as spam" will hit Unsubscribe instead, and Microsoft's reputation system distinguishes between the two.
Skip attachments for cold outreach
Attachments are the single biggest deliverability killer for cold mail. A 1 MB PDF attached to an unrecognized sender is treated like a phishing attempt by most modern filters. The same PDF as a OneDrive sharing link — the sender's name on the link, no payload in the message — sails through.
OutMass enforces this by default: attachments are added as OneDrive links rather than encoded into the message. More on why this matters.
If 10,000/day still isn't enough
You've hit the policy ceiling. Three real options, all of them changing the architecture rather than working around limits:
Option 1: Multiple sending accounts (carefully)
Some companies set up several Microsoft 365 mailboxes — sales@, outreach@, individual reps — and split the campaign across them. This works but only if each mailbox is a real, signed-off address with a real human attached. Burner accounts created solely to escape the limit get caught and banned within days.
Option 2: A transactional email service
For genuine high-volume marketing or transactional traffic, the right tool is a dedicated transactional email service: Azure Communication Services, SendGrid, Mailgun, Postmark, Amazon SES. They're built for the 50,000+ messages/day case, with their own deliverability infrastructure, IP warming, and bounce/complaint handling.
The trade-off: messages send from noreply@yourdomain.com, not from your personal Outlook mailbox. Recipients can tell it's a marketing platform. For cold outreach where personal-looking matters, this is a downgrade. For transactional or newsletter mail, it's the correct tool.
Option 3: Multi-day campaigns
Most "I need to send 50,000 emails" use cases are actually "I need to send 50,000 emails over the next 30 days." A 50,000-message campaign at 1,500/day = 33 days, comfortably below limits and far better for deliverability than a 5-day blast at 10,000/day. OutMass's scheduled sending handles this natively — you upload the CSV, set the daily cap, and the worker spreads sends automatically.
Send 1,000+ personalized emails without hitting Microsoft's ceiling
Built-in rate limiting, automatic per-day spreading, and OneDrive attachments for better deliverability.
Install OutMass — free up to 50/monthFrequently asked questions
What is the Outlook send limit?
Outlook.com personal accounts can send to roughly 500 unique recipients per day. Microsoft 365 business and Exchange Online plans allow up to 10,000 recipients per day, with a maximum of 500 per single message and a throughput cap of 30 messages per minute.
What happens when I hit the Outlook send limit?
Microsoft returns a SubmissionQuotaExceeded error and rejects new sends until the daily counter resets at midnight UTC. The counter is a rolling 24-hour window in some regions; in most tenants it resets at the top of the UTC day.
Can I increase my Outlook send limit?
The limit is enforced server-side and cannot be raised through any user setting. For new tenants the limit is intentionally lower for the first 30 days to prevent abuse. Organisations sending high-volume legitimate mail typically use a transactional service like Microsoft Azure Communication Services, SendGrid, or Mailgun for that traffic — not their primary Outlook mailbox.
Does sending slowly avoid the limit?
Slowing the per-minute rate avoids the throughput cap (30/min) but does not raise the daily total. If you need to send 5,000 emails on a 500/day account, you need a multi-day campaign or a different sending channel.
Will my account get suspended for sending too much?
Hitting the daily limit by itself doesn't suspend your account — Microsoft just throttles new sends. Suspension typically happens when a high spam-complaint rate, abuse reports, or a sudden burst pattern triggers Microsoft's anti-abuse systems. Slow, personalized, per-minute-rate-limited sending stays well below those thresholds.
Last updated: April 29, 2026.