Blog
Microsoft 365 Throttling: Sending Limits, Causes & Best Practices (2026)

Microsoft 365 Throttling: Sending Limits, Causes & Best Practices (2026)

Published on: Nov 02, 2026
•
5 min read
Summarize with

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.

Table of Contents

Quick comparison: Microsoft 365 sending limits at a glance

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. 

Limit Slows or stops? Affects How it clears
30 messages a minute Slows: extra emails are queued One mailbox On its own, within minutes
10,000 recipients a day Stops sending One mailbox On its own, as the rolling 24 hours pass
Tenant external recipient limit Stops external sending Every mailbox in the tenant On its own, as the 24-hour window passes
Outbound spam restriction Stops sending One mailbox An admin has to release it
2,000 external recipients a day Doesn't apply: Microsoft canceled it in January 2026 n/a n/a
Recommended for cold email About 30 cold emails a day Each mailbox Stay under it, and add mailboxes for more volume

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. 

What Microsoft 365 throttling means for cold email

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.

Throttling vs hard sending limits

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.

The limit Microsoft canceled

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.

Microsoft 365 sending limits you need to know

These Exchange Online limits matter when sending from a Microsoft 365 mailbox. 

Limit What it covers What happens if you go over
Message rate 30 messages a minute, per mailbox Extra messages are delayed, not bounced
Recipient rate 10,000 recipients in any rolling 24 hours, per mailbox, internal and external combined The mailbox can't send until its count falls back under the limit
Recipients per message A per-message cap that admins can raise up to 1,000 The message is rejected
Tenant external recipient rate A cap on external recipients for the whole tenant Every mailbox in the tenant is blocked from emailing outside addresses, with error 550 5.7.233
Outbound spam detection Sending patterns Microsoft treats as spam The mailbox is restricted from sending, with error 550 5.1.8

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. 

How many cold emails a Microsoft 365 mailbox should send

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.

What triggers throttling and restrictions

Microsoft watches for sending that looks unusual or unwanted. These patterns most often get cold email mailboxes flagged.

Sudden volume spikes and new accounts

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.

Missing authentication and a weak sender reputation

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.

Poor lists and irrelevant emails

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.

How to tell you've hit a limit

Microsoft doesn’t always give a clear warning. Here are the signs to watch for and what they mean.

What you see What it means
Emails go out, but later than scheduled You're hitting the 30-per-minute speed limit. Spread your sending over more time.
Bounces with 550 5.1.8 The mailbox has been restricted for suspected spam and can't send
Bounces with 550 5.7.233 The whole tenant has hit its external recipient limit
The mailbox stops sending after a busy day It has reached its 24-hour recipient limit
The mailbox appears on the Restricted entities page in Microsoft Defender It's been blocked from sending, and an admin has to release it

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.

Best practices to avoid Microsoft 365 throttling

None of this is complicated. Most restrictions happen because someone skips a step, not because Microsoft acts unpredictably.

1) Ramp up volume gradually, and keep warmup running

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.

warmup status and health score for each connected mailbox in Warmforge
This image shows warmup status and health score for each connected mailbox in Warmforge

Keep warmup running once campaigns begin. It provides steady, normal activity alongside the bounces and complaints that cold email will always bring.

2) Spread volume across mailboxes and domains

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.

3) Send steadily through business hours

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.

4) Authenticate every domain

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.

5) Clean your lists and keep emails relevant

  • Verify every address before adding it to a sequence. Remove invalid addresses, role addresses, and anyone whose address has bounced before.
    ‍
  • Write for the person, not the list. Mention something specific about their company, a recent change, or a common problem in their industry. Using their first name isn’t enough.
    ‍
  • Test two opening versions, then keep the one with more replies and fewer opt-outs.
    ‍
  • Make opting out easy, and remove anyone who asks immediately.

What to do when a mailbox gets restricted

If a mailbox starts bouncing with 550 5.1.8, follow these steps in order. 

  1. Pause every campaign using that mailbox. Further sending attempts will fail and won’t help.
    ‍
  2. Open the Restricted entities page in Microsoft Defender to confirm the block.
    ‍
  3. Find the cause before releasing it. First, rule out a compromised account by checking recent sign-ins, unfamiliar forwarding rules, and emails you didn’t write that were sent. If the account is clean, review the campaign for a volume spike, a new list, or repeated spam complaints.
    ‍
  4. Fix the cause, whether that means resetting credentials, removing the bad list, or rewriting the email.
    ‍
  5. Remove the mailbox from the Restricted entities page. You’ll need a tenant admin role. If a provider supplies your mailboxes and you don’t have admin access, contact their support team.
    ‍
  6. Restart at a lower volume, keep warmup running, and build back up over a week or two.

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. 

How Primeforge helps you stay within Microsoft 365's limits

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.

1) One tenant per domain

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.

2) Pre-warmed mailboxes, ESP matching and automated DNS

Three Primeforge features address the triggers discussed earlier. 

  • New accounts with no history. Pre-warmed mailboxes already have warmup activity, so you’re not starting from zero. They offer a head start, not a free pass. Primeforge’s guidance says to keep warmup running after purchase and follow recommended sending limits. To learn how long a specific domain was warmed, ask support.
    ‍
  • Spam filtering. With ESP matching, Primeforge lets you send through the same email provider your prospects use. If most of your list uses Microsoft 365, sending from Microsoft 365 mailboxes improves your chances of reaching the inbox.
    ‍
  • Missing authentication. Primeforge automatically sets up SPF, DKIM, DMARC and custom tracking for every domain, so a missed step doesn’t leave a domain unauthenticated.
pre-warmed Microsoft 365 mailboxes available in Primeforge
This image shows pre-warmed Microsoft 365 mailboxes available in Primeforge

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. 

reply rates by recipient provider in Primeforge Mailbox Analytics
This image shows reply rates by recipient provider in Primeforge Mailbox Analytics

3) Monitoring with Warmforge

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.

4) Primeforge vs a standard Microsoft 365 setup

Features Primeforge Standard Microsoft 365
Built for Cold outreach Everyday business email
Tenants One per domain Usually one shared by every domain
SPF, DKIM and DMARC Set up automatically Set up by hand for each domain
Profile pictures Added at scale Added one mailbox at a time
Pre-warmed mailboxes Available as an add-on Not available
Setup time About 30 minutes Days to weeks
Price per mailbox $4.50, dropping to $3.50 at volume From $6
Personalized Outbound Strategy

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

Conclusion: Count your mailboxes before you count your limits 

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.

Scale outreach with real Google and Microsoft inboxes

Set up Google Workspace and Microsoft 365 inboxes faster.
Start with
4.6 rating on G2
Add as a preferred
source on Google