Outlook Sending Limits for Cold Email

Outlook.com and Microsoft 365 are different products

An @outlook.com mailbox is a consumer account. A Microsoft 365 mailbox on your own domain is a business account managed by an administrator. They share an interface but have different limits, different policy controls and different support paths.

Microsoft publishes sending limits per account and per minute, plus message-size and recipient limits. The figures change, so confirm them in Microsoft's documentation for the account type you are using. The practical point is that a business mailbox can still be throttled, and an administrator can restrict sending without the mailbox owner knowing why.

SMTP AUTH may be off

Many cold email tools connect to Outlook by SMTP with a username and password. Microsoft 365 tenants can disable SMTP AUTH, and new tenants often have it disabled by default. When it is off, the connection fails even though the password is correct.

Check with whoever administers the tenant. If SMTP AUTH cannot be enabled, use OAuth where the tool supports it, or move the campaign to a different sending path. Do not keep retrying a connection that policy is designed to block.

Where Outlook cold email breaks

The most common failures are throttling during a large import, messages rejected for exceeding size or recipient limits, and authentication errors caused by tenant policy. Outlook also has stronger built-in filtering on some account types, so a campaign that works from one mailbox may filter from another.

Another practical issue is the shared mailbox. A shared mailbox is useful for a team, but sending cold email from one can confuse ownership and make replies hard to attribute. Use a named mailbox per sender where possible, and keep the shared inbox for genuine team correspondence.

Staying inside the limits

• Confirm the account type and its published limits.
• Confirm SMTP AUTH or OAuth is available before connecting.
• Warm the mailbox and start with a modest daily volume.
• Count recipients, including follow-ups and CC fields.
• Watch for throttle responses and pause the sender.
• Avoid large attachments on a first contact.
• Keep outreach mailboxes separate from billing and support.

Mail Pro connects Outlook and Microsoft 365 mailboxes and shows sender health and bounces per account, so a throttled sender is visible before it silently stops delivering. Volume is set per sender, and campaigns can rotate across inboxes.

What Microsoft throttling looks like

A throttled message may be rejected immediately with a temporary error, or accepted and delayed. Delays are easy to miss in a dashboard that only counts sends, because the campaign looks like it is running while messages queue. Check the actual activity feed and the sender's error log, not only the scheduled count.

If a sender is throttled, reduce its volume and wait. If the whole tenant is affected, an administrator may need to review the account's sending behaviour. Cold email from a business tenant is not invisible to Microsoft; it is measured like any other mail.

Choosing Outlook at all

Outlook is a reasonable sending path when prospects expect to hear from a Microsoft-domain address and when the volume is modest. For larger campaigns, a dedicated SMTP provider gives clearer control over DNS, IP reputation and per-mailbox limits. If you need additional inboxes to spread volume, LocalSMTP SMTP accounts are one option; compare the trade-offs in dedicated sending domain.

Whatever you choose, set the limit from how many cold emails per inbox per day rather than from the provider ceiling.

A worked example

A consultancy connects six Microsoft 365 mailboxes. Two fail immediately: the tenant has SMTP AUTH disabled. The administrator enables it for the outreach mailboxes only, with a policy that keeps it off for finance and support. The remaining four are warmed and split a campaign of 200 first-touch emails a day. One mailbox starts returning temporary errors after a week; it is paused, its volume moves to the others, and the campaign continues without a gap.

The lesson is that the technical connection is part of deliverability. A correct list and good copy cannot compensate for an account that is not allowed to send.