Maximum Number of Email Recipients in Outlook 365: All 3 Caps
The direct answer to the maximum number of email recipients in outlook 365 is 500 on any single message - counted across To, Cc and Bcc combined. But that number lives inside two siblings that trip people who plan against 500 alone: a 10,000-recipient rolling daily budget and a 30-message-per-minute pace limit. All three belong to the mailbox, so they follow you from new Outlook to classic Outlook to the web to any SMTP client - changing apps never changes the arithmetic.
Here is how each cap counts, how they interact on real sends, and the routes around them that do not involve a second mailbox.
The maximum number of email recipients in outlook 365, all caps
| Cap | Number | Scope | What trips it |
|---|---|---|---|
| Recipients per message | 500 | One message, To+Cc+Bcc together | Wide announcements, big CC chains |
| Recipients per day | 10,000 | Rolling 24 hours, all messages | Merges, busy campaigns, automations sharing the mailbox |
| Messages per minute | 30 | Per mailbox, any submission path | Bulk jobs, scripts, enthusiastic merge runs |
Admins can lower the per-message figure through recipient limits settings (per mailbox or org-wide), and some tenants do - so if your rejections arrive below 500, ask the admin what the mailbox's configured limit is before debugging anything else. No admin can raise any cap above the service's numbers.
How the caps count, precisely
Every address is one recipient, regardless of field. A message To 2 people, Cc 8, Bcc 490 is exactly at 500 and legal; one more address anywhere bounces the whole message for everyone - Exchange rejects the message outright rather than trimming the list.
A distribution list or Microsoft 365 group counts as one recipient at submission, with expansion happening inside Exchange afterward. That makes groups the sanctioned way to address large internal audiences: a 3,000-member all-staff group is one recipient against the 500 cap. External contact lists enjoy no such collapse once individual external addresses are on the message itself.
Against the daily budget, the counting is cumulative and rolling: the 400 recipients from this morning still occupy budget tonight, and capacity returns 24 hours after each send rather than at midnight. The two caps multiply into a practical shape: twenty maximal 500-recipient messages exhaust the entire day's 10,000 - one wide message every 20 minutes for a workday, and then silence until the window rolls.
The failure messages, matched to their cap
- "The message has too many recipients" with a 5.5.3-style code - the per-message 500 (or a lower admin-configured limit). Fix by splitting the audience or using a group.
- "Daily user sending limit exceeded" language, 550 5.4.5-class - the 10,000 rolling budget. Nothing resumes until the window releases capacity; splitting the message does not help because the budget, not the width, is spent.
- Deferrals that slow a run to a crawl with 4.3.2-class transient codes - the 30-a-minute tempo. Mail is not refused, only paced; retry storms make it worse.
Matching the message to the cap before reacting prevents the classic wrong fix: splitting a bounced 600-recipient message into two 300s works, while splitting after a daily-budget bounce just produces two more bounces.
Shared mailboxes and delegates: whose caps apply
A wrinkle worth its own paragraph, because shared team mailboxes are where recipient math goes to get confusing. When you Send As or Send On Behalf of a shared mailbox, the limits consumed depend on how the message is submitted, and in the common cases the shared mailbox's own budgets take the hit - which means five teammates sending "from" support@ are jointly draining one 10,000-recipient day and one 30-a-minute tempo without any individual noticing their share. Teams that route announcements, ticket replies and a weekly digest through one shared identity should inventory that identity's total daily consumption the same way they would a service account's, because the Thursday the caps trip, every workflow on the mailbox stops at once and the bounce does not name which teammate spent the budget.
Designing sends that never meet the caps
For legitimate wide internal mail, groups are the whole answer: build the audience once, address one name, let Exchange expand it. For external announcements to modest lists, batch under the per-message cap with margin - 400s, not 499s, because someone always adds recipients later - and keep the day's total under half the budget so the mailbox's other duties keep breathing.
For personalized sends, remember the trade: mail merge converts one 500-wide message into 500 individual messages, which respects the per-message cap beautifully while spending the daily budget 500 times faster and marching straight into the per-minute throttle. Merges above a few hundred belong early in the day and nowhere near month-end invoice hours.
And the structural answer once numbers grow: recipient caps are mailbox properties, and mail that routinely needs more recipients than a mailbox allows is - by Exchange's own design language - not mailbox mail anymore. Newsletters, product announcements to customer lists, and event blasts belong on sending infrastructure with list management, unsubscribe handling and reputational isolation, where "maximum recipients" is a plan parameter rather than a hard-coded 500.
The one-paragraph version for the person mid-bounce
Count your addresses: over 500 (or your tenant's lower setting) on one message means split it or use a group. Under the per-message cap but bounced with daily-limit wording means the mailbox's rolling 10,000 is spent - wait out the window, and move recurring volume off the mailbox. Slow trickling with temporary errors means the 30-a-minute pace - throttle the sender and stop retrying fast. Three caps, three behaviors, three fixes, and none of them is "try again harder".
Frequently asked questions
What is the maximum number of recipients per email in Outlook 365?
500 recipients per message counted across To, Cc and Bcc together, unless an admin has configured a lower limit for the mailbox. Exceeding it bounces the entire message rather than delivering to the first 500.
Does a distribution list count as one recipient in Outlook 365?
Yes - at submission a distribution list or Microsoft 365 group counts as a single recipient, with expansion handled inside Exchange. That is the supported way to reach large internal audiences without meeting the 500 cap.
Can an admin increase the 500 recipient limit in Office 365?
Admins can lower per-mailbox recipient limits but cannot raise them beyond the service maximum of 500. Larger audiences need groups for internal mail or dedicated sending infrastructure for external lists.
Why do my Outlook 365 emails slow down during a large send?
The 30-messages-per-minute mailbox throttle paces bulk runs with transient deferrals. It is a tempo control, not a rejection - space the sends below the rate and the delays disappear.