Outlook Sending Limits: Daily Caps for Microsoft 365 and Outlook.com
Summarize with AI
Outlook sending limits depend on the service behind the mailbox. A Microsoft 365 subscriber using Outlook.com has a published limit of 5,000 recipients per day. An Exchange Online work mailbox has a 10,000-recipient limit in a rolling 24-hour window, plus a rate limit of 30 messages per minute. Those figures measure different things and can sit beneath stricter tenant or anti-spam controls. Identify the account type first, then plan against the narrowest recipient, message, and organization-wide limit that applies.
Outlook Sending Limits at a Glance
The Outlook application does not set one universal quota because the underlying service controls the allowance. Microsoft's Outlook.com support page covers consumer Outlook.com accounts, while the Exchange Online service limits cover work and school mailboxes hosted by Microsoft 365.
| Account or limit layer | Published recipient limit | Message limit | Window or scope |
|---|---|---|---|
| Outlook.com for Microsoft 365 subscribers | 5,000 recipients per day | 500 recipients per message | Consumer account |
| Outlook.com new recipients | 1,000 recipients per day | Included in other Outlook.com limits | People the sender has never emailed before |
| Exchange Online mailbox | 10,000 recipients | 30 messages per minute | Per user, rolling 24 hours |
| Exchange Online message | Not applicable | 500 recipients by default, configurable up to 1,000 | Per message |
| Exchange Online trial tenant | 5,000 external recipients per day | Separate mailbox limits still apply | Organization-wide |
| Default onmicrosoft.com domain | 100 external recipients | Separate mailbox limits still apply | Organization-wide, rolling 24 hours |
A connected Gmail, Yahoo, or other third-party account remains subject to that provider's rules. Using it through Outlook does not replace the provider's limits.
Outlook.com Sending Limits for Consumer Accounts
Microsoft publishes three figures for Microsoft 365 subscribers who use Outlook.com:
- 5,000 recipients per day
- 500 recipients per message
- 1,000 non-relationship recipients per day
Microsoft defines a non-relationship recipient as someone you have never sent email to before. The 5,000 figure is a recipient cap, not a promise that the account can send 5,000 separate messages. One message addressed to many people uses multiple recipient counts.
Limits can be lower for non-subscribers and can vary with usage history. Microsoft also says a new Outlook.com account may receive a temporarily reduced quota until it establishes credibility. The support page does not publish one lower figure that applies to every non-subscriber or new account.
It also does not specify a universal reset clock, lockout period, error code, or recovery process after an Outlook.com account exceeds its limit. Avoid scheduling a consumer workflow around an assumed midnight reset or fixed recovery time.
Microsoft 365 and Exchange Online Per-User Limits
An Exchange Online mailbox has three separate constraints. Its recipient rate limit is 10,000 recipients in a rolling 24-hour period, while the message rate limit is 30 messages per minute. One message can have 500 recipients by default, although an administrator can set that value from 1 to 1,000.
Microsoft describes the recipient and message rate limits as hard service limits that cannot be increased. Raising the per-message recipient setting does not raise the 10,000-recipient rolling total or the 30-message rate.
The recipient total includes internal and external recipients. It also follows the person doing the sending in delegated-mailbox scenarios. If a user sends through another mailbox with delegated permissions, the usage counts against the delegate, not the mailbox displayed in the From field.
Group counting needs closer attention. A distribution group in the organization's address book counts as one recipient toward the sender's per-user recipient-rate limit. A group stored in the sender's Contacts folder counts each member separately. Tenant external-recipient enforcement uses different group-counting rules, covered below.
Our outbound services use client-owned sending infrastructure and operating controls rather than treating a mailbox cap as a campaign target. The cap tells you where Microsoft enforces service capacity. It does not tell you what volume is appropriate for a particular audience or message.
Tenant External Recipient Limits in Microsoft 365
Exchange Online also applies the Tenant External Recipient Rate Limit, or TERRL. It counts external recipients across the organization in a rolling 24-hour window. Microsoft defines an external recipient by domain: the recipient's domain is not an accepted domain in the tenant.
For paid tenants, TERRL scales with the number of licenses. Microsoft does not publish one numeric allowance that applies to every paid Microsoft 365 organization. Administrators can see the tenant's actual limit and usage in the Tenant Outbound External Recipients report under mail-flow reports in the Exchange admin center.
Trial organizations have a published cap of 5,000 external recipients per day. This is a tenant restriction, separate from each user's 10,000-recipient rate limit. The lower applicable boundary controls what the organization can send externally.
TERRL expands distribution groups before counting. A group with 1,000 external members consumes 1,000 external-recipient counts, even though an internal directory group can count as one recipient toward the sender's per-user limit.
Microsoft applies another restriction to outbound mail from the tenant's default onmicrosoft.com domain: 100 external recipients per organization in a rolling 24-hour window. Attempts above that limit receive NDR 550 5.7.236. This rule is specific to the default domain and should not be presented as the general allowance for custom accepted domains.
What Happens When a Limit Is Exceeded?
The consequence depends on which limit was reached. Microsoft's outbound sending limit troubleshooting guide distinguishes mailbox throttling from tenant-wide external-recipient enforcement.
| Limit reached | Documented behavior |
|---|---|
| Exchange Online 10,000-recipient rate | The mailbox cannot send until its count for the preceding 24 hours falls below the limit |
| Exchange Online 30 messages per minute | Excess is generally throttled, queued, and carried into later minutes |
| SMTP client submission over its message rate | Messages can be rejected, requiring the client to retry |
| Tenant External Recipient Rate Limit | External sending is blocked across the tenant with NDR 550 5.7.233 |
| Default onmicrosoft.com domain limit | Attempts above the cap receive NDR 550 5.7.236 |
| Outbound spam enforcement | Mail can use the high-risk delivery pool, and continued activity can restrict the user from sending |
The 30-message limit does not have one universal client behavior. Ordinary excess is generally delayed, but SMTP client submission can reject messages and require retry logic. Likewise, exceeding TERRL blocks tenant sending to external recipients. It does not mean all internal email stops.
Administrators investigating a restricted user should check Restricted entities and the relevant NDR. Microsoft documents 5.1.8 as one error associated with a restricted sender. Outbound spam policies can also produce different actions based on configuration, including restricting a user, restricting until the next day, or alerting without restriction.
Why These Caps Do Not Authorize Bulk Email
Microsoft's outbound spam protection documentation says Exchange Online is not intended for bulk-mailing scenarios. Microsoft 365 bulk sending is supported only on a best-effort basis. A published capacity limit therefore does not grant a bulk-email entitlement.
Capacity, anti-spam enforcement, and recipient acceptance are separate checks. Staying under 10,000 recipients does not prevent Microsoft from applying an undisclosed spam threshold. It also does not promise that a recipient's mail system will accept or place the message.
Teams that need a repeatable outbound process should define sending infrastructure, audience selection, suppression, reply handling, and CRM ownership together. Our resources for outbound teams cover the wider operating system around the mailbox rather than turning a provider maximum into a send plan.
Outlook Sending Limits FAQ
These answers preserve the service boundaries behind the headline numbers. Check the account type before applying any figure.
How many emails can I send per day from Outlook?
There is no single Outlook email count. Outlook.com publishes 5,000 daily recipients for Microsoft 365 subscribers. Exchange Online publishes 10,000 recipients per user in a rolling 24-hour window, plus 30 messages per minute. Count recipients and messages separately.
Is the Outlook limit 5,000 or 10,000?
Both numbers can be correct for different services. The 5,000-recipient figure applies to Microsoft 365 subscribers using Outlook.com. The 10,000-recipient figure applies to an Exchange Online user in a rolling 24-hour period.
When does the Microsoft 365 daily limit reset?
The Exchange Online recipient rate limit uses the preceding 24 hours, so it is a rolling window rather than a fixed midnight reset. Microsoft does not publish an equivalent universal reset clock on the cited Outlook.com consumer support page.
Can an Exchange administrator raise the 10,000-recipient limit?
Microsoft calls the recipient and message rate limits hard service limits, so an administrator cannot raise the 10,000-recipient limit. The per-message recipient setting can change from 1 to 1,000, but that does not increase the rolling total.
Ready to Build Outbound Around the Right Limits?
We can map mailbox capacity, tenant controls, suppression, and reply routing into a client-owned outbound system with clear operating boundaries. Book your free discovery call →
Frequently Asked Questions
A strong positive reply rate for B2B cold email is 1.5–3%. Top-performing campaigns with tight targeting and personalized copy can hit 4–5%. If you're below 1%, it usually signals a deliverability or messaging problem, not a volume problem.
The safe range is 30–50 emails per inbox per day for warmed inboxes. That's why outbound systems use multiple inboxes (we use 80) to reach 40,000+ monthly sends while keeping each inbox well within safe limits. Sending more than 50/day from a single inbox risks spam folder placement.
Yes. The CAN-SPAM Act permits unsolicited commercial email as long as you include a physical address, an unsubscribe mechanism, accurate headers, and non-deceptive subject lines. Unlike GDPR in Europe, the US does not require prior opt-in consent for B2B cold outreach.
Domain warm-up typically takes 2–3 weeks. During this period, sending volume gradually increases while the email warm-up tool generates positive engagement signals (opens, replies) to build sender reputation. Skipping or rushing warm-up is the most common cause of deliverability problems.
Cold email is targeted, relevant outreach to a specific person based on their role, industry, or company, with a clear business reason. Spam is untargeted mass messaging with no personalization or relevance. The distinction matters legally (CAN-SPAM compliance) and practically (deliverability depends on relevance signals).
Sofia Urrego
Account Success, LeadHaste
Looks after LeadHaste accounts end to end, from targeting and copy through to the conversations that come back, so each client keeps improving month over month.
