How to Send Mass Internal Email With Outlook

Most Microsoft 365 teams start with the same question: can we just send it from Outlook? For small, low-stakes updates, yes. For anything that has to reach everyone at once, stay on brand, and come back with proof of engagement, Outlook starts to strain.

Send mass email from Outlook, step by step

Outlook gives you two built-in ways to do this: a personalised mail merge that sends each person their own copy, or a quick Bcc send that hides recipients from one another. The mail merge steps come first, then the Bcc method. Both are the right call only when the audience is small and the timing is flexible. 

1. Prepare the email in Word

Open your draft in Word and go to View, then Web Layout, so the page behaves like an email canvas. Write in short paragraphs, keep the formatting simple, and put the primary call to action in the first screen. Use light visuals, clear link text, and alt text for anything you keep.

2. Connect your recipient list

Mail merge can read from Excel, Outlook Contacts, Access, or another database, and you can also start a new list in Word. If your list is a CSV or TXT file, import it into Excel first and use the worksheet as the source. Make sure there is an Email column and that every recipient has an address. Keep headers in row 1, one person per row, and no blank rows, and store values like postal codes as text so they are not truncated. If you use Outlook Contacts, set Outlook as the default mail app and match Word’s version.

3. Start the merge and pick E-mail Messages

In Word, open the Mailings tab, choose Start Mail Merge, then E-mail Messages. Word will produce one message per person and hand it to Outlook to send.

4. Select the recipients you trust

Choose Select Recipients, then Use an Existing List, and point to your Excel table. Confirm that the header row is detected and the Email column is clean.

5. Personalise with restraint

Use Insert Merge Field for FirstName or Department where it adds clarity. For deliverability and readability, less is more.

6. Send from Outlook, one message per person

Choose Finish and Merge, then Send E-mail Messages. Set the To field to your Email column, add a concise subject, choose HTML format, and send. Each recipient gets their own individual copy, addressed only to them.

Hide recipients with Bcc, the quick alternative

If you do not need personalisation and the list is small, you can skip the merge altogether. Start a new message in Outlook, put your own address in the To field, and add everyone else in the Bcc field, so no recipient can see who else received it. Bcc is the only built-in way to hide recipients from one another in Outlook, which is why it is the usual answer when you want to email a large group at once without exposing the whole list. It is fast, but it does not personalise, it gives you no analytics, and a large Bcc send runs straight into the per-message and per-day limits covered next.

Where Outlook reaches its limits in 2026

Outlook is an excellent inbox. It was built for conversation, not for broadcast, and at scale that distinction shows up quickly. Microsoft also adjusted its sending rules over the past year, so it is worth knowing exactly what a mailbox is allowed to do today.

The limits, and what they actually mean

Exchange Online caps a single message at 1,000 recipients across To, Cc and Bcc combined (often defaulted to 500), and each mailbox at 10,000 recipients per rolling 24 hours. Send to a distribution group and Exchange expands it in transport: one recipient against the rate limit, one message against the rate. For an internal announcement, none of these is the wall in your way, as anyone who runs Exchange knows.

The one that does count your members individually is TERRL, the tenant external recipient rate limit. It only counts external addresses, those outside your accepted domains, so internal recipients never touch it. Which is why capacity rarely decides this. A distribution group sends one identical message and keeps no record of what follows. 

What a list actually counts as

A distribution group stored in your organisation’s shared address book counts as a single recipient against the recipient rate limit. A personal contact group counts every member individually. That is why the same group send can behave very differently depending on how the list was built.

External sends now have their own cap

This is the part that changed. In 2026 Microsoft introduced a tenant-level limit on external recipients, the Tenant External Recipient Rate Limit, which caps how many people outside your organisation the whole tenant can email over a rolling 24 hours. The allowance scales with how many Microsoft 365 licences the tenant holds, and trial tenants are capped at 5,000 external recipients a day. If your audience ever includes alumni, contractors, partners, or any address outside your own domains, this is a real planning constraint rather than a footnote. Microsoft briefly proposed an even tighter per-mailbox external limit and then withdrew it in early 2026 after customer feedback, which tells you how much pressure single-mailbox bulk sending puts on the service.

Mail merge and the Graph API hit the same wall

Classic mail merge sends one message per person through Outlook, so it reaches the per-minute and per-day limits fast, and the newer Outlook does not fully support merges, which often means switching back to classic Outlook to run them. Sending through the Microsoft Graph API is the modern, programmatic path, and it is how integrated apps connect to your tenant in the first place. But a Graph send still routes through the same Exchange Online mailbox limits. Graph gives you cleaner automation, not a higher ceiling.

Outlook does not close the loop

Read receipts are not analytics. Leadership asks for click maps, click paths, read time, segment trends, and proof of reach, and none of that exists as a native broadcast workflow. So the process fragments: one tool to design, Excel to clean the list, Outlook to send, and the report lives somewhere else entirely. Every handoff adds risk, whether it is the wrong draft, a stale export, a missing link, or duplicate sends while working around throttling. Outlook rendering also varies across desktop, web, and mobile, so templates pick up spacing shifts, font fallbacks, and dark-mode contrast issues you did not see in the draft.

What Microsoft actually recommends

Microsoft is clear on this point. Exchange Online is built for everyday mail between people, and Microsoft’s own guidance is to use a dedicated service for legitimate bulk email such as newsletters. So the real question is not whether to add a broadcast layer. It is which one keeps your identity, content, and governance inside the Microsoft environment you already trust.

The Microsoft-native pattern that scales

The pattern is simple. Keep identity, content, delivery, and governance inside Microsoft, and add one layer built for scale, targeting, planning, and evidence. That is the role the JungleMail app plays, and it integrates with Microsoft 365 rather than sitting outside it.

Target from live Microsoft data

You select audiences straight from Entra ID by role, department, office, or any attribute, and you can resolve dynamic distribution lists at send time without exports. External subscribers such as alumni, contractors, and partners sit under the same policies, so the tenant-level external cap is managed for you rather than working against you.

Build on brand, with content from where it lives

You start from a locked brand template, so fonts, colours, and logos stay consistent by default. Deep SharePoint integration pulls pages, documents, and list items into the newsletter, or runs a dynamic query such as created in the last 7 days, then archives back to SharePoint for an auditable history. A communication calendar keeps launches from colliding, an AI assistant handles the work that moves the needle such as subject line testing, clear translations, and short summaries, and a stock library and AI image generation are available in the editor.

Throughput that matches the brief

This is where the difference is obvious. Typical sends move at 20,000 to 60,000 emails per hour, and up to 120,000 under optimal conditions, with no list splitting, no staging windows, and no duplicates. Set against a single mailbox’s 10,000 recipients a day, that is the difference between reaching everyone this hour and reaching everyone by the end of the week.

Governance and proof, by default

Power Automate approvals, send-on-behalf rights, and template section locks create a clear chain of custody, and archiving to SharePoint closes the loop. After send, you open analytics rather than guess: click maps show where attention pooled, clickstream shows how people moved through the content, read time shows whether a message was skimmed or read, and trends show how offices or roles performed over time. Add a short image or text survey when you need sentiment. Reporting can be anonymous or identified, depending on your policy.

JungleMail is trusted by 550+ companies, with more than 150 million emails sent to over 2 million employees. It is certified to ISO 27001, SOC 2 Type II, and ISO 9001, and is GDPR compliant.

What this looks like in practice

A global division needed a policy change to reach about 38,000 employees within the hour. The Outlook workaround split the list across a day, so some offices saw different versions at different times, IT fielded duplicate-send complaints, and the comms team had no way to prove reach. With JungleMail, the same team targeted live Entra attributes, delivered in a single window at enterprise throughput, and had a board-ready report covering read time, click maps, and office-level trends that same afternoon.

A simple decision rule

Use Outlook when the audience is small, the timing is flexible, and analytics do not matter. Use JungleMail when the brief is to reach everyone at once, stay on brand, and come back with evidence. Microsoft built Exchange Online for everyday mail and points bulk senders toward a dedicated layer. JungleMail is that layer, and it is an almost Microsoft-native one.

Frequently asked questions

Quick answers to common questions about sending bulk email from Outlook.