Get The Right Outbound Strategy In Minutes
Enter your email to get a custom plan & stack recommendation for your business
It's being carefully crafted by AI
Please check your mailbox in 5 minutes
Microsoft lets each mailbox email up to 10,000 recipients a day. That sounds like plenty of room, so throttling shouldn’t be a problem. Yet cold email mailboxes get blocked at just a few hundred emails a day, sometimes on their first busy morning.
The daily cap rarely causes the block. Long before a mailbox reaches 10,000, Microsoft’s spam detection flags a new account sending too fast, to addresses that bounce, or to people who report emails as spam. It then restricts the mailbox. Only an admin can release it, and most senders don’t know where to look.
Online advice doesn’t help much. Some guides still warn about a 2,000-recipient limit that Microsoft canceled. Others tell you to watch for error codes from Microsoft’s APIs, which you’d only see if your sending tool uses them.
Here’s how Microsoft 365 throttling works for cold email, including the limits, the difference between a delay and a block, the warning signs, ways to keep mailboxes sending, and what to do if one gets restricted.
If you only need the numbers, here they are. The table shows whether each limit slows or stops sending, who it affects, and how it clears.
Only one of these limits simply slows sending. The others stop it, and a spam restriction stays until someone releases it.
The aim is to stay well below Microsoft’s caps, at about 30 cold emails per mailbox each day, spread across several mailboxes and domains.
When people say Microsoft “throttled” their mailbox, they usually mean one of two things. One slows email down. The other stops it completely. Knowing the difference is the first step to fixing either problem.
Actual throttling is a speed limit. Each mailbox can send 30 messages a minute. Anything above that waits in a queue and goes out over the next few minutes, without a bounce or error. Most cold email tools send much more slowly, so you’ll rarely notice it.
Hard limits cause the bigger problems. If you exceed a daily recipient cap or get flagged for spam, Microsoft won’t just slow sending. It blocks the mailbox until the limit resets or an admin releases it. When a campaign suddenly stops, this is almost always the reason.
When something goes wrong, first ask whether your emails are late or not going out at all. Late emails point to the speed limit. Bounced emails, or a mailbox that can’t send, point to a hard limit or restriction.
If you read about cold email in 2024 or 2025, you probably saw warnings about a new cap of 2,000 external recipients per mailbox per day. Microsoft announced it in April 2024 and delayed the start date several times. In January 2026, Microsoft canceled it after customer pushback.
That cap doesn’t apply, so you don’t need to plan around it. The limits that still apply are below.
These Exchange Online limits matter when sending from a Microsoft 365 mailbox.
Two are easy to miss. The tenant limit covers everyone in the tenant, so one mailbox sending too much can block all the others.
Your organization’s outbound spam policy can also set limits below Microsoft’s defaults, so check it if a mailbox gets blocked well below 10,000 recipients.
The 10,000 figure is a ceiling for everyday business email. It isn’t a cold email target. A mailbox sending anywhere near that volume to people who’ve never heard from you will get flagged as spam long before reaching the cap.
For cold outreach, keep each mailbox to about 30 cold emails a day at a steady pace. When you need more volume, add mailboxes instead of pushing each one harder.
Microsoft watches for sending that looks unusual or unwanted. These patterns most often get cold email mailboxes flagged.
A mailbox that sent 10 emails yesterday and 300 today looks like a compromised account. That’s especially true for a new mailbox or domain with no sending history. Microsoft closely monitors new senders when they increase volume quickly. A gradual increase, without sudden jumps, is the safest approach.
Without SPF, DKIM, and DMARC, Microsoft can’t confirm that your email comes from your domain, so it trusts it less from the start. High bounce rates and spam complaints also hurt your sender reputation. Each makes the next email from that mailbox more likely to be filtered or blocked.
Most cold email problems start with the list, so clean your email list before every campaign. Inactive addresses bounce. Role addresses like info@ or sales@ rarely reply and often complain.
Spam traps can damage a domain with a single send. Generic emails sent to people with no reason to care get marked as spam. Those reports count against you, just as bounces do.
Microsoft doesn’t always give a clear warning. Here are the signs to watch for and what they mean.
Admins also receive Microsoft 365 alerts when a mailbox exceeds a sending limit or gets restricted. If someone else manages your tenant, ask them to forward those alerts.
You might also see “429 Too Many Requests” errors and Retry-After headers in guides. These come from Microsoft’s APIs, not mailbox sending limits.
You’ll only see them if your sending tool uses those APIs. A well-built tool waits for the time specified in the header, then tries again.
None of this is complicated. Most restrictions happen because someone skips a step, not because Microsoft acts unpredictably.
Give new mailboxes about two weeks of warmup before sending cold email. Start well below 30 cold emails a day, then increase over the following weeks.

Keep warmup running once campaigns begin. It provides steady, normal activity alongside the bounces and complaints that cold email will always bring.
Ten mailboxes sending 30 emails each look more natural than two sending 150 each. Use 2 to 3 mailboxes per domain, and spread sending across several domains. If one domain has trouble, the others keep sending.
Schedule sends throughout the working day rather than sending everything at once. A pace that resembles someone working through their inbox stays well below the per-minute limit and looks like normal business email.
Set up SPF, DKIM and DMARC on every sending domain before its first campaign, not just your main domain. Check them again after any DNS change.
If a mailbox starts bouncing with 550 5.1.8, follow these steps in order.
If the bounce is 550 5.7.233, the block affects the whole tenant, not one mailbox. Stop external sending from that tenant, let the 24-hour window pass, and reduce volume across its mailboxes before resuming.
Let me start with what people actually ask: Does Primeforge get around Microsoft’s limits? No. Primeforge mailboxes are real Microsoft 365 mailboxes, so every limit in this guide still applies. Primeforge changes how those mailboxes are set up, so a mistake in one place doesn’t stop everything else.
Primeforge gives each domain its own Microsoft 365 tenant. This matters because some Microsoft limits cover the whole tenant, not just one mailbox.
In a typical setup, all domains share one tenant. If one domain’s mailboxes exceed the tenant’s external recipient limit, or the tenant gets restricted, every mailbox stops sending. With a separate tenant for each domain, the problem stays with that domain while the others keep running.
Three Primeforge features address the triggers discussed earlier.

Mailbox Analytics shows each mailbox’s performance, including reply rates by recipient provider and the status code behind every bounce. This helps you distinguish a bad address from a blocked mailbox.

Primeforge mailboxes export directly to Warmforge, Salesforge, and other sending tools. In Warmforge, warmup runs in the background, health checks monitor DNS and blacklist status, and placement tests show whether Microsoft 365 recipients receive your emails in their inbox or spam folder.
Warmforge warmup is included when you send through Salesforge.
If a Primeforge mailbox gets restricted, follow the steps above and contact Primeforge support to have it released.
Here’s a calculation worth doing today. Divide your daily cold email volume by 30.
That’s how many Microsoft 365 mailboxes you need. With fewer, each mailbox sends more than it safely should, and you’ll eventually hit a restriction instead of a warning.
The fix is more mailboxes across more domains. Pushing your existing mailboxes harder won’t help.
Primeforge sets up Microsoft 365 mailboxes in about 30 minutes, gives each domain its own tenant so one problem can’t block the others, and handles SPF, DKIM, and DMARC.
Mailboxes start at $4.50 a month and drop to $3.50 at volume. If you can’t wait for warmup, pre-warmed mailboxes offer a head start.