
Microsoft 365 can encrypt email you send outside your organization so only the intended recipients can read it — and, with some options, so they can't forward or print it. Used well, it protects contracts, health details, and financial data. Used carelessly, it frustrates clients and gets messages ignored. This guide covers how to encrypt external emails in Microsoft 365: the layers of protection available, the encryption options, setting up mail flow rules, what recipients experience, advanced features and licensing, and the habits that keep encryption useful.
Encrypting Everything Isn't the Goal
💡 TL;DR
To encrypt external emails in Microsoft 365, use Microsoft Purview Message Encryption with mail flow rules that target specific messages — sensitive keywords, sensitivity labels, or chosen recipients — rather than every outbound email. Choose Encrypt-Only when recipients may need to forward or save, and Do Not Forward for tighter control. Test the recipient experience with Gmail and Outlook.com, remember the 25 MB message limit, and never apply encryption to cold outreach.
Here's a contrarian take: encrypting every external email is usually a mistake. Recipients outside Microsoft 365 often get a notice email with a link to a web portal instead of the message itself. For a contract or a medical record, that's a reasonable trade. For a meeting confirmation, it's friction — and for cold outreach, a wrapper email from an unknown sender looks a lot like phishing.
The goal is to encrypt what's sensitive, automatically and reliably, and leave everything else readable.
By the end of this, you'll know exactly how to encrypt external emails in Microsoft 365 in a way your clients will actually tolerate.
Three Layers of Protection in Microsoft 365
Layer | What it protects | Recipient effort |
|---|---|---|
TLS in transit | The connection between mail servers; Exchange Online uses TLS where the receiving server supports it | None |
Microsoft Purview Message Encryption | The message itself, with options to restrict forwarding or printing | Low — native in many Outlook clients; a portal for others |
S/MIME | Message signing and encryption using certificates on both ends | High — both sides need certificates |
Microsoft Purview Message Encryption is the practical choice for most organizations sending to external recipients. It's built on Azure Rights Management and replaced the older Office 365 Message Encryption, which Microsoft deprecated on July 1, 2023.
Encrypt-Only vs Do Not Forward vs Custom Templates
Option | What it does | Best for |
|---|---|---|
Encrypt-Only | Encrypts the message; recipients can still forward, print, and save | Most sensitive external email — contracts, invoices with personal data |
Do Not Forward | Encrypts and prevents forwarding, printing, and copying | Highly confidential content to a specific person |
Custom templates / sensitivity labels | Organization-defined rules for specific data types | Regulated data and consistent classification |
Encrypt-Only is the right default for most external mail. Do Not Forward can block a recipient's normal workflow — for example, forwarding a contract to their lawyer — so reserve it for cases that truly need it.
Setting Up Mail Flow Rules for External Mail
Mail flow rules apply encryption automatically, so users don't have to remember. Here's the process in the Exchange admin center.
Confirm encryption is available in your tenant — your plan needs to include Microsoft Purview Message Encryption.
Go to the Exchange admin center → Mail flow → Rules → Add a rule → Apply Office 365 Message Encryption and rights protection to messages.
Set conditions — for example, the recipient is outside the organization and the message contains sensitive keywords or has a specific sensitivity label.
Choose the option — Encrypt or Do Not Forward, or a custom template.
Start in test mode or with a narrow condition, such as a subject keyword like [secure].
Send test messages to Outlook, Outlook.com, and Gmail accounts and check the experience.
Enforce once you're happy, and tell users how to trigger encryption when they need it.
Users can also encrypt individual messages themselves from Outlook. Rules are for the cases where encryption shouldn't depend on someone remembering. Microsoft's message encryption FAQ covers supported clients and limits.
What External Recipients Experience
Recipient uses | Typical experience |
|---|---|
Microsoft 365 / Outlook clients | Often read the message natively in Outlook |
Outlook.com, Gmail, Yahoo, or other services | Receive a notice email with a link to a secure portal, then sign in or use a one-time passcode |
Mobile apps | Outlook mobile can display many encrypted messages; others use the portal |
Two limits are worth knowing. Microsoft lists a 25 MB maximum message size for encrypted messages, including attachments. And protection is applied to supported file types — Office files, for example, stay protected even after download when Do Not Forward is used.
Here's the advice we'd push back on: "Recipients will figure out the portal." Many won't, and some will assume the notice email is phishing. Tell clients in advance that sensitive documents will arrive encrypted, and use custom branding where available so the notice clearly comes from you.
Advanced Message Encryption: Revoke, Expire, Brand
Microsoft Purview Advanced Message Encryption adds controls for external mail:
Revocation — remove a recipient's access after sending, for messages read through the encryption portal.
Expiration — make external messages unreadable after a set date.
Custom branding — templates that show your organization's look on the notice and portal.
These features require higher-tier licensing — Microsoft's training materials list Microsoft 365 E5 or equivalent add-ons — whereas basic message encryption is included in plans such as Microsoft 365 E3. Licensing changes over time, so confirm against your current plan before rolling out.
A Rollout Plan That Doesn't Annoy Clients
Organizations that encrypt external emails in Microsoft 365 smoothly usually roll it out in stages rather than flipping one big rule on.
Week | Step | Goal |
|---|---|---|
1 | Turn on a keyword-triggered rule (for example, [secure] in the subject) for one team | Learn the recipient experience safely |
2 | Gather feedback from a few friendly clients | Spot portal or sign-in confusion early |
3 | Add content- or label-based rules for clearly sensitive data | Encrypt automatically where it matters |
4 | Add custom branding if licensed; brief all staff | Trustworthy notices; consistent use |
Ongoing | Review rule matches and user questions monthly | Catch over- or under-encryption |
The keyword trigger is a useful long-term option too. It lets staff encrypt a single message deliberately without waiting for an admin, while rules handle the obvious cases automatically.
In practice, the teams that encrypt external emails in Microsoft 365 without complaints are the ones that told clients first, tested with Gmail recipients, and kept the rules narrow. Broad rules can always be widened later; a client who got frustrated in week one is harder to win back. If you ever need to encrypt external emails in Microsoft 365 for a whole department, expand one condition at a time and watch the help-desk questions.
What Works — and Common Mistakes
Practice | Why |
|---|---|
Encrypt by content or label, not everything | Keeps routine email readable and encryption meaningful |
Default to Encrypt-Only for external mail | Fewer blocked workflows for recipients |
Use custom branding where licensed | Recipients trust notices that clearly come from you |
Warn clients before the first encrypted message | Reduces confusion and phishing worries |
Test with Gmail and Outlook.com recipients | Most external friction appears there |
Never encrypt cold outreach | Portal notices from unknown senders look like phishing and hurt replies |
That last point matters for sales teams. Outreach belongs on separate outreach domains and mailboxes, without encryption rules — see separating prospecting mailboxes from customer communication. Encryption belongs on the mail your customers and partners rely on. Securing those accounts with MFA is the other half of the job — see Microsoft 365 MFA setup.
Litemail provides Microsoft 365 inboxes for outreach with full admin access, automated SPF/DKIM/DMARC, and dedicated US and EU IPs — keeping outbound prospecting separate from the business mail you protect with encryption.
Keep outreach separate from protected business mail — Litemail Microsoft 365 and Google Workspace inboxes give sales teams separate outreach domains with full admin access, SPF/DKIM/DMARC pre-configured, and dedicated US and EU IPs — so encryption policies stay on the mail that needs them. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: Microsoft 365 MFA Setup · Microsoft 365 OAuth Setup · Separate Prospecting From Customer Email · Microsoft 365 Inboxes
Key Takeaways
To encrypt external emails in Microsoft 365, use Microsoft Purview Message Encryption with targeted mail flow rules.
Legacy Office 365 Message Encryption was deprecated on July 1, 2023 and replaced by Purview Message Encryption.
Default to Encrypt-Only; reserve Do Not Forward for highly confidential messages.
Recipients outside Microsoft 365 often read encrypted mail through a portal — warn them and use branding where licensed.
Encrypted messages are limited to 25 MB including attachments.
Never encrypt cold outreach; keep encryption for customer and partner mail.
Frequently Asked Questions
How do I encrypt external emails in Microsoft 365?
Use Microsoft Purview Message Encryption. Create a mail flow rule in the Exchange admin center that applies encryption to messages sent outside your organization that match conditions you choose.
What's the difference between Encrypt-Only and Do Not Forward?
Encrypt-Only protects the message while letting recipients forward, print, and save. Do Not Forward also blocks forwarding, printing, and copying.
Can Gmail users read encrypted Microsoft 365 email?
Yes. They receive a notice email with a link to a secure portal, where they sign in or use a one-time passcode.
Is Office 365 Message Encryption still available?
The legacy version was deprecated on July 1, 2023 and replaced by Microsoft Purview Message Encryption.
Can I revoke an encrypted email in Microsoft 365?
With Advanced Message Encryption, you can revoke access to messages read through the encryption portal and set expiration dates. It requires higher-tier licensing.
Should I encrypt all external emails?
Usually not. Encrypt sensitive messages by content, label, or recipient, and leave routine mail readable.
Should cold outreach emails be encrypted?
No. Encryption notices from unknown senders look like phishing. Keep outreach on separate domains, such as Litemail outreach inboxes, without encryption rules.
Protect Business Mail, Keep Outreach Separate
Litemail Microsoft 365 inboxes come with full admin access, SPF/DKIM/DMARC configured, OAuth export, dedicated US and EU IPs, and free domain replacement on pre-warmed plans.
Plans from $39/month · Microsoft 365 and Google Workspace · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Microsoft 365 Inboxes · Microsoft Cold Email Policy 2026 · Cold Email Compliance Checklist 2026 · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


