Skip to main content
Cybersecurity

Microsoft 365 Message Encryption: Encrypt Is Not Do Not Forward

Microsoft 365 Message Encryption: Encrypt Is Not Do Not Forward

Here’s the short version: Microsoft 365 message encryption protects the email, and the Encrypt choice still lets the recipient forward, print, and copy it. Do Not Forward is the choice that blocks those actions. Neither choice encrypts a SharePoint or OneDrive file that the message only links to.

A firm hits Encrypt on a payroll spreadsheet and calls the problem solved. The recipient can forward that message. If the spreadsheet was a cloud link, the file in the library was never part of the encryption. This page is the difference between those controls.

What Microsoft 365 message encryption actually does

Microsoft Purview Message Encryption is the current service. It is built on the Azure Rights Management service. You can protect a message with a rights template, with Do Not Forward, or with the encrypt-only option. A person can apply it from Outlook for Windows, Outlook for Mac, or Outlook on the web. An admin can apply it with a mail flow rule. Office 365 Message Encryption, the older product, was deprecated on July 1, 2023, and Microsoft’s message encryption FAQ says it is being replaced by this service. If the sender’s mailbox is still active, old OME mail can still be read.

The service assumes Azure Rights Management is on. Microsoft’s setup article says that is the only prerequisite, and that eligible tenants usually already have it. It also says Purview Message Encryption is not compatible with Active Directory Rights Management Services. A firm still on AD RMS has to move to Azure Rights Management before this works. Get-IRMConfiguration should show AzureRMSLicensingEnabled as true.

Microsoft’s comparison of email encryption separates three ideas that get mashed into the word “encrypted.” Message encryption sends a protected message to a person inside or outside the tenant, including Gmail, Yahoo, and Outlook.com. The recipient does not need a Microsoft 365 subscription to read it or to send an encrypted reply. Information Rights Management adds usage restrictions, such as do-not-forward, on top of encryption. S/MIME uses certificates, and Microsoft notes that S/MIME messages are not scanned for malware the way ordinary mail is. TLS protects the connection between mail servers. It does not decide whether the bookkeeper can forward the message after it arrives. BitLocker encrypts the disk. It does not encrypt an email.

Encrypt is not Do Not Forward

A hand holding paper envelopes on a table
A sealed envelope is not the Encrypt button. Encrypt still lets the recipient forward.

Microsoft’s usage rights article is the page to settle an argument about the Encrypt button. Encrypt-Only gives the recipient every usage right except Save As, Export, and Full Control. Microsoft’s own example is that the recipient can copy from the email, print it, and forward it. What they cannot do is strip the protection off. Unencrypted Office documents attached to that message inherit the same permissions: they are encrypted, and the recipient can still save, edit, copy, and print them from Office.

Do Not Forward is the other button. Microsoft’s sensitivity label encryption article describes it in the Outlook client: recipients cannot forward the email, print it, or copy from it. The Forward button is not available. Save As and Print are not available. The recipient cannot add or change people in To, Cc, or Bcc.

A sensitivity label can offer the user those same two choices when the label is set up for user-assigned permissions. The label can also encrypt the file that lives in a library. Message encryption does not do that second job. A label that is only a name, with no encryption, does not hide a file from someone who can already open it, which is the point we made about Copilot. Hitting Encrypt on one email does not publish a label program.

Office files are protected. PDFs are a switch

The FAQ lists the Office extensions Purview Message Encryption encrypts by default, including docx, xlsx, and pptx. It does not support the 97-2003 formats: .doc, .xls, and .ppt. PDF attachments are not encrypted until an admin with at least the Information Rights Management role runs Set-IRMConfiguration -EnablePdfEncryption $true. Until that command has been run, a PDF riding on an encrypted message is not in the same state as the docx next to it. The maximum size of a protected message, attachments included, is 25 MB.

Protection is inherited from the message onto an unencrypted attachment of a supported type, and it stays after download. The FAQ’s example is a Do Not Forward attachment: the original recipient downloads it, attaches it to a new message, and the new recipient cannot open it. That inheritance is not a reason to email the only copy of a client file. It is a reason to know which button you used.

A cloud attachment is not inside the encrypted message

Two colleagues reviewing a spreadsheet and a stack of files
The file in the library is a different object from the message that mentioned it.

The FAQ is direct about the modern way people send files. SharePoint and OneDrive attachments are not supported. You can encrypt the mail message. You cannot encrypt the cloud attachment. Outlook’s “share a link” behavior puts a link in the message and leaves the file in the library. Encrypting the message encrypts the sentence that contains the link. The file opens for whoever the link and the library allow, which is the subject of SharePoint external sharing.

If the file should not travel, do not attach it and do not drop an Anyone link into an encrypted message as a substitute. Put the file in a library the other party can open, with a sensitivity label if the file itself needs encryption, and send a short note. Message encryption is for the note that has to be an email. It is a poor vault for the workbook.

Mail flow rules also cannot encrypt or decrypt meeting invites and their responses. The FAQ says to use sensitivity labels for calendar items, Teams meetings, and chat. A rule that “encrypts everything leaving the firm” will not catch the invite, and it will catch password-reset mail, vendor notifications, and anything over 25 MB. Test one real message to a Gmail address before you turn a rule on for the whole domain. Microsoft’s article on mail flow rules for encryption also says to remove any action that still applies the previous version of OME.

Who can open a protected message

People inside the tenant read a protected message in Outlook for Windows, Mac, the web, and Outlook mobile. People outside Microsoft 365 read it in a browser through the encrypted message portal. The portal does not support calendar items or voice mail. It supports preview of Word, Excel, PowerPoint, and PDF attachments that were protected with the message.

A shared mailbox needs the right client

A shared mailbox stacks on shared mailbox security. The FAQ says you can open an encrypted message sent to a shared mailbox. If it came from inside the organization, a supported Outlook client can open it while you are signed in. If it came from outside, you need Outlook on the web.

Outlook for Windows does not open a delegate’s encrypted mail

Delegated access is narrower than Full Access suggests. When someone has Full Access to another user’s mailbox, encrypted mail is supported in Outlook on the web, Outlook for Mac, and Outlook mobile. Outlook for Windows does not support that delegated access. The assistant who lives in desktop Outlook, opened onto the attorney’s mailbox, can miss the protected message that Outlook on the web would show.

There is a second limit if you grant a mail-enabled security group access to a shared mailbox so that Windows Outlook can open protected mail. The FAQ says that method needs Outlook version 2402 or later, only works for mail generated after June 2024, and the message has to be Do Not Forward or Encrypt-Only. Mail from outside the organization is not in that set. Do not promise the front desk that every encrypted vendor message will open in the desktop app.

Business Premium includes the button, not the revoke

The FAQ lists Microsoft Purview Message Encryption with Office 365 E3 and E5, Microsoft 365 E3 and E5, Microsoft 365 Business Premium, and several education and government plans. Each person who benefits needs a license. Business Basic, Business Standard, and Exchange Plan 1 or Plan 2 are not on that included list. Those plans need Azure Information Protection Plan 1 added. A tenant with a mix of Business Standard and Business Premium does not get the button for every mailbox.

Revocation is a different product layer. Microsoft’s revoke article says email revocation is part of Advanced Message Encryption, included in Microsoft 365 E5, Office 365 E5, and the matching nonprofit and education A5 plans. You also have to enable Premium Encryption on the E5 license. Business Premium is not on that list. Even with E5, you can revoke only when the recipient received a link to the branded portal. A native inline message in Outlook cannot be revoked. Gmail and Yahoo recipients get the link. A coworker in Outlook often does not. Expiration of access through the portal is the same Advanced feature. Do not tell a Business Premium firm that a sent payroll message can be pulled back.

Advanced Message Encryption is an E5 feature

Advanced Message Encryption is also where Microsoft puts expiration and extra branding for external portal messages. It is useful when a regulator or a client contract asks for a message that dies, and when you can accept that the control applies to the portal copy. It is not the first switch a 20-person firm should hunt for. The first switch is knowing which button the staff are actually clicking.

A mail flow rule is for a pattern, not every message

Use a rule when a pattern is real. Messages to a specific outside counsel domain. A subject line the firm already uses for drafts. A word in the body that means a tax identifier. The rule should name Encrypt or Do Not Forward on purpose, not “whatever the default template is.” Encrypt is the right choice when the outside party must be able to forward the message inside their own firm, and you still want the message protected on the way. Do Not Forward is the right choice when the recipient list is the whole audience.

Two operational limits belong in the rule, not in a footnote. The FAQ says that in some connector setups, including Exchange hybrid, BCC recipients are removed before the message is encrypted. If a person must see the message, put them in To or Cc. And a rule cannot fix a file that was already shared from SharePoint last quarter. Encryption on Tuesday’s email does not rewind Monday’s link.

What we will and will not call encrypted

We will say a message is protected when Azure Rights Management is on, the sender or the rule applied Encrypt or Do Not Forward, and someone outside the tenant has opened a test message in a browser. We will say a file is protected when a sensitivity label with encryption is on the file, which is a different project from the Outlook button.

We will not call these Microsoft 365 message encryption:

  • TLS, because the message arrived
  • BitLocker, because the laptop disk is encrypted
  • The Encrypt button, when the requirement was that nobody forward it
  • A SharePoint link pasted into a protected message
  • A PDF attachment, before PDF encryption is turned on
  • A promise to revoke the message on a Business Premium tenant
  • An old mail flow rule that still applies the previous version of OME

If the Outlook button, the labels on the files, and the sharing links should be one pass instead of three, start with cybersecurity and contact Secure Techies. The button is one click. The choice of which button, and which object it actually covers, is the work.

Frequently Asked Questions

No. Encrypt-Only protects the message and still lets the recipient copy, print, and forward it. They cannot remove the protection. Do Not Forward is the option that blocks forward, print, and copy, and it removes the Forward button in Outlook. Read the button you actually clicked.
No. Microsoft deprecated Office 365 Message Encryption on July 1, 2023, and it is being replaced by Microsoft Purview Message Encryption. A mail flow rule that still says to apply the previous version of OME is the old action. Purview Message Encryption is what a current Microsoft 365 tenant uses, and it includes Encrypt-Only and Do Not Forward.
Yes. Microsoft lists Microsoft Purview Message Encryption with Business Premium, and with Microsoft 365 E3 and E5, among other plans. Each person who benefits needs a license. Business Basic and Business Standard need Azure Information Protection Plan 1 added. Revoking an encrypted message, and setting it to expire, are Advanced Message Encryption, which Microsoft lists with E5 plans, not with Business Premium.
No. Microsoft says SharePoint and OneDrive attachments are not supported. You can encrypt the message. You cannot encrypt the cloud file by encrypting the message. The file opens or stays closed based on the link and the library permissions. Put the sensitive file under a sensitivity label if the file itself needs protection.
Only in a narrow case. Revocation is part of Advanced Message Encryption, which requires an E5 plan, and it works when the recipient got a link to the encrypted message portal. A recipient who opened the message inline in Outlook cannot have that copy revoked. Gmail and Yahoo recipients usually get the portal link. A colleague in the same tenant, in Outlook, usually does not.
Share

Related Articles

Keep reading — more guides you might find useful.

Talk to a real IT expert — free

No sales pressure, no jargon. Just a straight assessment of where your IT and security stand, and what to do next.