Skip to content

Microsoft Office 365 secure email: what your plan already includes

On this page

In Office 365, a secure email starts on the Options tab of a new Outlook message. The Encrypt button there offers two choices, Encrypt and Do Not Forward. Pick one and send as usual. The button comes from Microsoft Purview Message Encryption, which Business Premium, E3 and E5 already include. Business Basic and Standard get it with a small add-on. Your recipient can be on Gmail, Yahoo or anything else, and they don’t need a Microsoft subscription.

Most firms on Microsoft 365 have more protection than they’ve switched on. The mail between servers is already encrypted in transit. Spam and malware filtering is already running. What’s often missing is the last part, which is a habit, or a rule, for the few messages that carry a tax return or a bank detail. This guide is the view from the admin center. It covers what your plan includes, how to check it works, and how to make encryption happen without anyone remembering.

If you only need the button in your own Outlook, sending it in Outlook has the steps for each app.

Microsoft Office 365 secure email by plan

The first question is what you already pay for. Here’s how Microsoft’s own Purview service description and Defender overview line up, checked October 4, 2026.

PlanEncrypt button and rulesSensitivity labels with encryptionExpiry and revocationThreat filtering
Business Basic or StandardAdd Azure Information Protection Plan 1Comes with that add-onNoBuilt-in protection
Business PremiumIncludedApplied by handNoDefender for Office 365 Plan 1
Microsoft 365 E3IncludedApplied by handNoDefender for Office 365 Plan 1
Microsoft 365 E5IncludedBy hand or automaticallyYes, with Advanced Message EncryptionDefender for Office 365 Plan 2

Office 365 E3 and E5 match their Microsoft 365 namesakes on encryption. Exchange Online Plan 1 and Plan 2 take the same add-on as Business Basic. A firm on Business Premium that wants expiry and revocation can add the Microsoft 365 E5 Information Protection and Governance add-on, which the service description lists for Advanced Message Encryption.

One line in Microsoft’s Message Encryption FAQ catches small firms most often:

Each user benefiting from Microsoft Purview Message Encryption needs a license to use message encryption.

So the add-on goes on each person who sends sensitive mail, not on the tenant once. A firm of seven where one person lacks it has one person without the button.

Your recipients need nothing. The service description puts it plainly: “They don’t need a subscription to view encrypted messages or send encrypted replies.”

If you’ve seen the name Office 365 Message Encryption, or OME, it’s the same family. Microsoft retired the older version on July 1, 2023 and replaced it with Purview Message Encryption automatically.

Checking that encryption is on

On an eligible plan, encryption usually switches itself on. Microsoft’s setup page says that when the Rights Management service is active, “Microsoft 365 activates message encryption automatically and you don’t need to do anything.” That service is also activated automatically for most eligible plans.

To confirm it, an admin connects to Exchange Online PowerShell and runs two commands:

  1. Get-IRMConfiguration. Look for AzureRMSLicensingEnabled set to True.
  2. Test-IRMConfiguration -Sender you@yourfirm.com -Recipient you@yourfirm.com, using any two addresses in your tenant. The last line should read OVERALL RESULT: PASS.

If the Encrypt button shows in desktop Outlook but not on the web, Microsoft’s troubleshooting article has the fix. Run Set-IRMConfiguration -SimplifiedClientAccessEnabled $true.

Then do the test that matters most. Send an encrypted message to a personal Gmail address you control, and open it on your phone. Five minutes now shows you exactly what a client will see.

Encrypting by rule so nobody has to remember

The Encrypt button depends on someone choosing it. At 6 p.m. on a Friday, that’s the part that slips. A mail flow rule moves the choice to the server. It encrypts every message that matches, from every app, every time.

Microsoft’s FAQ says a rule can match on recipient, recipient domain, or words in the subject or body. A common shape for a small firm is “encrypt anything going outside the firm with secure in the subject.” Staff then type one word to protect a message, even from a phone.

Microsoft’s mail flow rule steps run like this:

  1. In the Microsoft 365 admin center, go to Admin centers, then Exchange.
  2. In the Exchange admin center, go to Mail flow, then Rules, and select Create a new rule.
  3. Name it, for example “Encrypt external mail marked secure.”
  4. Under Apply this rule if, add The sender is located, then Inside the organization.
  5. Add the condition The recipient is external/internal, then Outside the organization.
  6. Add a condition for the subject containing the word secure.
  7. Under Do the following, select Modify the message security, then Apply Office 365 Message Encryption and rights protection, and pick Encrypt from the template list.
  8. Save it, then send yourself a test from inside the firm to an outside address.

If the template list is empty, encryption isn’t active yet. Go back to the checks above.

A rule protects what leaves your firm. Microsoft is clear about the other direction: “You can’t encrypt inbound mail from senders outside of your Exchange Online organization.” Mail a client sends you arrives however they sent it.

One more limit is worth knowing. Rules don’t touch calendar invites. Microsoft’s FAQ says sensitivity labels handle meeting invites instead, so keep the sensitive detail out of the invite.

Sensitivity labels for sending from a phone

A sensitivity label is a named setting, built by an admin, such as “Client confidential,” with encryption built in. On Business Premium, E3 and E5, staff apply labels by hand. On E5, labels can also be applied automatically.

Labels matter most on phones. Microsoft’s labeling documentation says:

Outlook for iOS and Android: These apps don’t support users applying encryption without labels, so nothing to disable.

So if staff send sensitive mail from their phones, a label is how they encrypt it. Microsoft’s label encryption page gives a ready example for sending to Gmail. In the label’s Access control settings, choose Let users assign permissions when they apply the label. The box below it reads In Outlook, enforce restrictions equivalent to the Do Not Forward option. Encrypt-Only is the other choice there.

Once the label exists, publish it in a label policy so it appears in staff Outlook. A label with a plain name also teaches the habit. “Client confidential” says why it’s there in a way “Do Not Forward” doesn’t.

What your recipient sees and what you can shape

Someone on Microsoft 365 or Outlook.com reads your message inside Outlook like any other email. Anyone else gets a short notice email with a Read your message button. A Gmail user can sign in with Google. Anyone else can request a one-time passcode by email. It’s good for a short while, and Microsoft’s recipient page puts the limit at 15 minutes. What a Gmail user sees walks through it screen by screen.

Two parts of that flow are yours to shape from the tenant.

Branding. The default notice is a plain Microsoft message, and a careful client may hesitate before clicking it. On every plan with encryption, an admin can brand the notice and the portal with Set-OMEConfiguration. It covers:

  • your logo and a background color
  • the line next to your name, such as “has sent you a secure message”
  • a disclaimer and a link to your privacy statement
  • the text at the top of the portal

A notice with your firm’s logo and familiar wording looks like you. That’s half the work of getting a client to open it.

How recipients sign in. With Advanced Message Encryption on E5, an admin can build more than one template. Each template can switch one-time passcodes on or off with -OTPEnabled, and Google, Yahoo or Microsoft sign-in with -SocialIdSignIn. A firm might keep passcodes for clients and require a real account sign-in for a partner bank.

When the passcode goes missing. The usual cause is junk mail. Microsoft’s FAQ says “DKIM and DMARC settings for your organization might cause these emails to end up filtered as spam,” and early passcodes can land in quarantine. Tell the client to check junk first. A quick text saying “I’ve just sent you an encrypted email” helps too.

Expiry and revocation on E5

Advanced Message Encryption adds two controls. An admin can set encrypted mail to expire after a number of days, and a sender can revoke access to a message they’ve sent. Microsoft draws the boundary in its overview:

You can only revoke and set an expiration date for emails sent to external recipients.

It also has to be mail the recipient reads through the portal, which in practice means mail with a custom branding template applied. A message that a Microsoft 365 recipient reads inline in Outlook stays in their mailbox. Revoking closes the portal door. It doesn’t pull back a copy someone has already saved or printed. Expiring a message covers what expiry reaches across every provider.

How message encryption differs from TLS, SPF, DKIM, DMARC and Defender

Admin pages call several different things “email security.” Each one solves its own problem, and only one of them keeps the message itself private.

FeatureWhat it doesWho sets it upWhat the recipient sees
Purview Message EncryptionEncrypts the message, so only the named recipient can open itOn by default on eligible plans, then rules and labelsA sign-in or a passcode, unless they’re on Microsoft 365
TLS, opportunisticEncrypts the connection between mail servers when both support itOn by defaultNothing
TLS, forced by connectorRefuses to send to one partner unless the connection is encryptedAn admin, per partnerNothing
SPF, DKIM and DMARCProves mail from your domain really came from youAn admin, in your domain’s DNSNothing, unless a check fails
Defender and built-in filteringScreens mail for spam, malware and phishingOn by default, tuned by an adminNothing, unless a message is held

TLS and partner connectors

Microsoft’s TLS page puts the key fact in one line:

TLS doesn’t encrypt the message, just the connection.

Exchange Online tries TLS on every outgoing message. If the other server can’t do it, the message goes anyway. Microsoft says that “by default Exchange sends the message without encryption if the recipient’s organization doesn’t support TLS encryption.” Once delivered, the message sits readable in the recipient’s mailbox. How far the email padlock goes follows that trip hop by hop.

A connector changes that for one partner, such as a bank or a payroll provider that asks for it. In the Exchange admin center, go to Mail flow, then Connectors, and add one from Office 365 to Partner organization. On the security page, tick Always use Transport Layer Security (TLS) to secure the connection. Microsoft’s connector steps cover the rest. Mail that can’t meet the rule is rejected rather than sent in the clear. Forced TLS suits steady traffic with one partner. For a one-off message to a client, message encryption fits better.

SPF, DKIM and DMARC

These three prove that mail from your domain is yours. Microsoft’s email authentication page defines them:

  • SPF “specifies the source email servers that are authorized to send mail for the domain.”
  • DKIM “uses a domain to digitally sign important elements of the message to ensure the message remains unaltered in transit.”
  • DMARC “specifies the action for messages that fail SPF or DKIM checks for senders in the domain.”

They keep someone else from sending as you, and they help your mail land in the inbox. They don’t hide what your message says. They do touch encryption in one place, since the passcode emails above can fall foul of a strict DMARC setup.

Defender and the built-in filters

Every Microsoft 365 tenant has spam, malware and phishing filtering switched on. Microsoft says these protections “are included in all organizations with cloud mailboxes.” Business Premium and E3 add Defender for Office 365 Plan 1, with Safe Links and Safe Attachments. E5 adds Plan 2. All of this guards what arrives in your inbox. It keeps nothing private on the way out. Phishing and impersonation have their own guides in Point’s phishing and email fraud collection.

Is that email from Microsoft genuine?

People who start sending encrypted mail soon get mail that looks like it too. Some of it is real and some is a scam. Microsoft’s scam guidance gives two firm rules:

Microsoft doesn’t send unsolicited email messages or make unsolicited phone calls to request personal or financial information, or to provide technical support to fix your computer.

Error and warning messages from Microsoft never include a phone number.

An encrypted message from a client’s firm is a different thing. It names a real sender you know, and it asks you to read a message, not to pay or call. When in doubt, ask the sender by phone, using a number you already have. The same habit works in reverse. Tell your own clients ahead of time that your secure messages will carry your logo.

Point on a Microsoft 365 account

Point connects to your Microsoft 365 mailbox and reads the client’s thread for you. It writes the reply in your voice. By default, that reply waits for you to review and send. Point doesn’t encrypt mail. Encryption is Microsoft’s, and it stays in your tenant.

A mail flow rule pairs well with that. Rules run on Exchange as mail leaves, so they apply to whatever your mailbox sends. When a client asks for last year’s return, Point has the reply ready. You add secure to the subject, attach the file and press send, and your rule encrypts it on the way out. What else Point does has the rest.

Common questions

How do I send a secure email in Office 365?

A new Outlook message has an Encrypt button on its Options tab, offering Encrypt or Do Not Forward. That works on Business Premium, E3 and E5, and on Business Basic or Standard with the Azure Information Protection Plan 1 add-on. An admin can also set a rule that encrypts matching messages automatically.

What is the difference between a secure email and a regular email?

Regular email is protected only while it moves between servers, and only if both ends support TLS. Once delivered, anyone with access to either mailbox can read it. Secure email locks the message itself. The recipient has to prove who they are before it opens. Four things people call secure email compares the types in one table.

How do I know if an email from Microsoft support is genuine?

Microsoft says it doesn’t send unsolicited email or calls asking for personal or financial information or offering technical support. Its error messages never include a phone number. If an email claims to be Microsoft support and asks you to call, click or pay, treat it as a scam. Reach Microsoft through the help links inside your own admin center instead.

Does Microsoft 365 Business Standard include email encryption?

Not on its own. Microsoft lists Purview Message Encryption in Business Premium, E3 and E5. Business Basic and Business Standard get it by adding Azure Information Protection Plan 1, assigned to each person who’ll send encrypted mail.

Is Office 365 email encrypted by default?

The connection is, when the other server supports TLS. Exchange Online tries TLS on every message and sends without it if the recipient’s server can’t use it. The message itself isn’t encrypted until someone chooses Encrypt, applies a label, or matches a mail flow rule.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.