Encrypting a message in Outlook means choosing between S/MIME certificates and Microsoft Purview Information Protection, and the method your organization has deployed decides which buttons exist in your ribbon. If you have a digital ID installed, open a new message, go to Options, click Encrypt, and pick Encrypt-Only or Do Not Forward. If the Encrypt button is greyed out or missing, no certificate is loaded on that profile and no amount of clicking will change it.

What the Encrypt Button Actually Does to a Message

Outlook's Encrypt control sits on the Options tab of a compose window in classic Outlook for Windows and under the encryption flyout in the new Outlook and Outlook on the web. Microsoft documents the menu as offering Encrypt-Only and Do Not Forward as the baseline choices. Encrypt-Only protects the message body and attachments in transit and at rest within participating services. It does not stop forwarding.

The mechanism matters more than the label. With Encrypt-Only, only the message contents are scrambled. The To, Cc, and Subject lines travel in plain readable text, so anyone who intercepts the message still sees who you wrote to and what you called the subject. If the subject line itself is sensitive, the message needs a stronger wrapper or a different channel.

Do Not Forward adds a restriction layer on top of encryption. Recipients can read the message but cannot forward, print, or copy its contents, and the rights travel with the file even after it leaves your mailbox. This is the option most people actually want when they say "encrypt this email" in a business setting.

Both options require the recipient's identity to resolve before Outlook encrypts anything. If you type an external address that has no certificate and no rights-management identity, Outlook either prompts you to download the recipient's certificate or refuses to send at all.

Three Ways to Get a Digital ID Before You Start

The digital ID, sometimes called an S/MIME certificate, is the key pair that makes classic certificate-based encryption possible. Without one, the Encrypt menu stays dormant. You have three realistic routes to obtaining one.

Buy a certificate from a public certificate authority. Commercial providers sell S/MIME certificates that bind your email address to a public key, and prices and validity periods change, so confirm current terms on each vendor's site. This route works for individuals who need to encrypt with strangers who can look up their certificate.

Use a corporate certificate authority. Most enterprises with Microsoft 365 run their own PKI and push certificates to Outlook automatically through group policy or Intune. If your IT department manages your device, check with them before buying anything β€” the certificate may already be deployed and simply not published to the global address list yet.

Request a free certificate or use an internal self-signed one for testing only. Self-signed certificates will not validate for recipients outside your environment, so treat them as a lab exercise. Microsoft's own support documentation treats the digital ID as a prerequisite, not a feature Outlook supplies.

Publish Your Certificate So Recipients Can Encrypt to You

Encryption is a two-way street. You can only send an encrypted message to someone whose public certificate you hold, and they can only reply in kind if yours is published. Publishing is the step most guides skip, and it is where encrypted threads quietly die.

In classic Outlook for Windows, open File, then Options, then Trust Center, then Trust Center Settings, then Email Security. The Import/Export section lets you load a .pfx or .p12 certificate file and its password. Once imported, the same dialog has a Publish to GAL button that pushes your certificate to the Exchange global address list.

For Microsoft 365 tenants, administrators can configure certificate publishing centrally so every mailbox gains the certificate without user action. Ask your admin whether auto-publishing is enabled before you troubleshoot a send failure, because a published certificate in the GAL is what lets colleagues encrypt to you without asking for a file.

If you use Outlook on the web or the new Outlook, S/MIME support is present but the certificate management surface is thinner. Microsoft's documentation notes that S/MIME in Outlook on the web requires the certificate to be installed on the device or provisioned by policy, and the experience differs by browser and tenant configuration. Verify on your own tenant rather than assuming parity with the desktop client.

Step-by-Step: Encrypting a Single Message With a Certificate

Use this sequence in classic Outlook for Windows once a digital ID is installed and your certificate is published. The names below match the ribbon and dialog labels Microsoft documents.

1: Open a new message and address it to a recipient whose certificate you already hold or whose address resolves in the global address list. 2: Go to the Options tab and click the Encrypt button, then choose Encrypt-Only from the menu. 3: Alternatively, click the small arrow in the bottom-right corner of the Options group to open the Message Options dialog and tick the "Encrypt message contents and attachments" checkbox. 4: Compose the message and attach files as normal. Outlook encrypts the body and every attachment, not just the text. 5: Press Send. Outlook validates each recipient's certificate before transmitting. 6: If a dialog appears saying Outlook cannot find a certificate for a recipient, remove that address or obtain their certificate first β€” do not send unencrypted by accident. 7: Confirm the sent item shows the encryption indicator in your Sent Items folder.

Two failure cases dominate support threads. The first is an expired certificate: Outlook will silently fall back to plaintext if you click through a warning, so watch for the yellow banner. The second is a distribution list β€” Outlook cannot encrypt to a list address unless the list itself holds a certificate, so expand the list into individual recipients first.

Encrypting Every Message by Default, and Signing as a Pair

Sending one encrypted email is the easy part. Making encryption automatic is where policies and habits collide. In the Message Options dialog described above, the same panel holds "Encrypt message contents and attachments" and "Add digital signature to outgoing messages," and both can be set as defaults under File, Options, Trust Center, Email Security.

Check the box labeled "Encrypt contents and attachments for outgoing messages" in that Email Security panel and every new message starts encrypted. The tradeoff is immediate: any recipient without a resolvable certificate becomes a send error, so a default-on setting suits a closed organization and frustrates anyone emailing the public.

Digital signing is the natural companion. A signature proves the message came from you and that nobody altered it in transit. Encrypt-Only without a signature protects confidentiality but leaves authenticity to the honor system, which is why Microsoft pairs the two concepts in the same dialog.

Microsoft Purview message encryption offers a second default path that does not need certificates at all. An administrator defines a mail flow rule or sensitivity label that applies encryption automatically, and users send normally. That is the mechanism most Microsoft 365 organizations actually run, and it changes the instructions entirely β€” see the next section.

Microsoft 365 and Purview: Encryption Without Certificates

If your tenant has Microsoft Purview Information Protection licensed, the Encrypt button may open a template list instead of a certificate prompt. Templates such as "Encrypt" and "Do Not Forward" apply Azure Rights Management, and recipients authenticate with a Microsoft account, a one-time passcode, or federated credentials rather than an S/MIME certificate.

This model solves the biggest practical weakness of certificates: the recipient does not need to have installed anything. Microsoft's documentation for Purview message encryption describes recipients opening protected mail through a web experience when their client cannot handle the rights management wrapper. That is why it dominates enterprise deployments despite licensing cost.

Licensing is the boundary to check. Purview message encryption requires eligible Microsoft 365 or Office 365 subscriptions, and the specific SKUs that include it change over time β€” confirm on Microsoft's licensing pages or with your reseller rather than trusting a blog table. A tenant on a basic plan may see the button and get an error.

Revocation is the quiet advantage here. A message protected with Purview encryption can have its access revoked after sending, because the rights check happens when the recipient opens it. Certificate-encrypted mail cannot be recalled once delivered in usable form. For anyone sending contracts, payroll data, or patient information, that difference decides the architecture.

Reading Encrypted Mail: What the Recipient Actually Sees

Encryption advice usually covers sending and stops. The receiving side is where most confusion lives. A recipient of S/MIME-encrypted mail needs their own private key to decrypt, which means they must have been issued a certificate and the sender must have used it.

Outlook on Windows generally decrypts automatically when the recipient's certificate is in the local store and matches the message. Outlook for Mac handles S/MIME through the account settings and stores certificates in the macOS keychain; if the certificate is missing, the message shows a padlock warning and body text may not render.

Mobile is the weak link. Outlook for iOS and Android can display some protected messages, but S/MIME support and Purview-protected content behave differently across app versions and account types. For a recipient on a phone, test the workflow before you promise anyone a secure channel.

Purview-protected mail behaves differently again. A Gmail recipient typically clicks a link, receives a one-time passcode by email, and reads the message in a browser. That works, but it also means the passcode lands in the same inbox as the message β€” a real weakness worth naming to anyone who assumes encryption equals immunity.

Encrypt vs. Sign vs. Protect: Picking the Right Control

People conflate three controls that solve different problems. The table below lines them up on the dimensions that actually vary, so you can pick without reading a vendor brochure.

Control Protects Metadata exposed Recipient setup Revocable after send
S/MIME Encrypt-Only Body and attachments To, Cc, Subject Certificate required No
S/MIME plus digital signature Body, attachments, sender authenticity To, Cc, Subject Certificate required both ways No
Do Not Forward (rights-managed) Body, attachments, forwarding, printing, copying To, Cc, Subject visible to service Account or passcode Yes, in Purview
TLS in transit only The hop between servers Everything at rest on both ends None No

The verdict splits by recipient. Encrypt with S/MIME when you and the recipient both live inside a certificate-managed organization and cannot justify Purview licensing. Reach for rights-managed encryption when recipients are outside your tenant, when revocation might matter, or when you need to stop forwarding.

TLS deserves a caution. Transport encryption protects mail between servers, but it is not end-to-end β€” the message decrypts at each gateway and sits readable in the recipient's mailbox. Marketing pages that call TLS "email encryption" are describing a different guarantee than the Encrypt button.

The Costs Nobody Prices In: Time, Licensing, and Support Load

Certificate-based encryption carries a hidden operating cost. Every certificate has an expiry date, commonly one year for commercial S/MIME products, and renewal is not automatic in most deployments. Microsoft's documentation points users to Trust Center settings to manage certificates, which means someone has to remember.

Do the arithmetic on a small team. Twenty staff, each with a certificate renewed annually, and a conservative 15 minutes per renewal to re-import the file, re-publish to the global address list, and test one encrypted send β€” that is five hours of administrative time per year before counting the support tickets from the first failed send. Add the inevitable calendar reminder that gets ignored, and a single expired certificate takes down encrypted replies for days.

Licensing is the larger line item for the Purview route. Microsoft bundles message encryption into higher-tier subscriptions, and the effective cost per seat only makes sense when the same license also delivers data loss prevention, retention labels, and sensitivity labeling. A 25-person firm buying the top tier solely to encrypt outbound invoices will overpay; the same firm can run S/MIME for the certificate purchase price instead.

Support load is the third cost. Every encrypted external thread generates at least one "I can't open this" call. Budget for a one-page recipient instruction sheet that names the passcode flow, or route sensitive external mail through a portal instead.

Common Mistakes That Quietly Break Encryption

The most frequent mistake is replying unencrypted to an encrypted message. Threads do not inherit protection automatically in every configuration, and Outlook will happily send a plain reply if the Encrypt button was not active. Check the sent item, not the compose window.

A second mistake is encrypting to a distribution list or an alias. Certificates bind to a specific address, and a list address rarely carries one. Outlook's send validation catches this sometimes, but not always β€” expand the list and address people individually.

The third is assuming an encrypted message cannot be screenshotted. Encrypt-Only stops interception, not a recipient holding a phone up to a monitor. Do Not Forward and Purview sensitivity labels can block copy and print in supported clients, but screen capture defeat is not a promise any vendor makes.

The fourth is trusting the subject line. Because Encrypt-Only leaves headers readable, never put a client name, diagnosis, or deal value in a subject of an encrypted message. Move identifying detail into the body, or use a rights-managed template that obscures more.

FAQ

Does Outlook encrypt emails automatically without me doing anything?

Only if an administrator has applied a mail flow rule or default sensitivity label, because Outlook has no built-in always-on encryption for ordinary consumer accounts. Classic Outlook for Windows does let you tick "Encrypt contents and attachments for outgoing messages" in Trust Center, which applies Encrypt-Only to every new message. That default breaks the moment you email someone without a certificate, so most organizations leave it off and rely on Purview rules instead.

Why is the Encrypt button greyed out in my Outlook?

The most common cause is that no digital ID is installed on your Outlook profile, which removes the certificate-based option entirely. The second cause is a licensing gap: on Microsoft 365 tenants without eligible Purview licensing, rights-managed templates fail even when the button appears. Check Trust Center's Email Security panel for an imported certificate, then ask your administrator whether encryption is licensed on your account.

Can I read an encrypted email in Gmail or on my phone?

Yes for rights-managed messages, usually through a browser link and a one-time passcode sent to the same inbox. S/MIME-encrypted messages are harder: Gmail has no native S/MIME decryption, so the recipient needs a mail client with the matching private key. Test one message with your actual recipient's device before relying on encryption for a real deadline.

What happens if my certificate expires while someone is replying to me?

They cannot encrypt to you, because Outlook validates the certificate at send time and a stale certificate fails that check. Your previously received encrypted mail remains readable on your machine as long as the private key is still installed. Renew the certificate, re-import the new file, and re-publish to the global address list so senders pick up the replacement.

Is encrypted email the same as a secure portal?

No, and the difference matters for compliance. Encrypted email still lands in the recipient's mailbox and remains there after reading, while a portal keeps the document behind a login you control and logs every access. For regulated data like health records or financial statements, a portal gives you an audit trail that neither S/MIME nor Encrypt-Only provides.

Does Do Not Forward stop someone from copying the text with their own eyes and keyboard?

It blocks the in-client copy, print, and forward functions in supported clients, but a determined recipient can retype what they read. Treat Do Not Forward as a speed bump that stops accidental leakage and casual forwarding, not as a control against a motivated insider. Pair it with a retention label if the data warrants real monitoring.

Why did my encrypted message arrive as an attachment instead of readable text?

Some recipients receive rights-managed mail as a wrapped attachment that opens in a browser or a Microsoft viewer, which is expected behavior for Purview message encryption. S/MIME-encrypted mail can also fail to render inline when the receiving client lacks the private key, leaving a smime.p7m attachment. Neither indicates a send failure β€” tell the recipient to open the attachment through the link or viewer.

How much does it cost to set up Outlook encryption for a small business?

S/MIME certificates are sold per address by commercial certificate authorities, and the entry price for a single-address certificate has historically sat in the low tens of dollars per year, though current prices and validity terms must be confirmed with each vendor. Purview message encryption is not sold standalone; it arrives inside higher-tier Microsoft 365 plans whose per-seat cost is substantial. A ten-person firm should price both routes before deciding, because the licensing jump usually dwarfs the certificate spend.

The article is general educational information and not legal, compliance, or security advice for your specific environment. Certificate requirements, licensing tiers, and supported clients change, so confirm current terms with Microsoft, your certificate authority, and a qualified IT or compliance professional in your jurisdiction before relying on any configuration described here.