New Outlook for Windows: S/MIME signed emails lose attachments in secondary Microsoft 365 accounts

Michael Paulke 0 Reputation points
2026-11-20T13:26:55+00:00

Problem: S/MIME-signed emails do not display their original attachments in secondary Microsoft 365 accounts in the new Outlook for Windows.

We are experiencing a reproducible issue with the new Outlook for Windows when using multiple Microsoft 365 accounts.

Environment:

  • New Outlook for Windows

Four Microsoft 365 accounts configured independently

One primary account and three secondary accounts

Incoming S/MIME digitally signed emails containing PDF attachments

Observed behavior:

When opening an S/MIME-signed email in a secondary account, Outlook displays the following error:

"The S/MIME signature cannot be verified when viewing in a secondary account."

The original email body is displayed correctly, and the message list shows the paperclip icon indicating an attachment. However, the actual PDF attachment is missing from the message view.

Troubleshooting performed:

Opened the affected original email in the secondary account. The attachment was missing.

Opened the same email in Outlook on the web. The attachment was present and accessible.

Temporarily changed the affected secondary account to the primary account in the new Outlook.

Reopened the exact same email. The S/MIME signature was now reported as valid and trusted, and the PDF attachment appeared immediately.

Changed the original primary account back to primary.

Reopened the same email. The S/MIME verification error returned, and the attachment disappeared again.

Result:

The issue is directly reproducible and depends on whether the receiving Microsoft 365 account is configured as the primary or a secondary account in the new Outlook.

The attachments are not deleted or missing from Exchange Online. They simply cannot be displayed in the secondary account.

Expected behavior:

S/MIME-signed emails and their original attachments should remain fully accessible in all configured Microsoft 365 accounts, regardless of which account is designated as primary.

Questions for Microsoft:

Is this a known limitation or confirmed bug in the new Outlook for Windows?

Is there an existing fix, update, or supported workaround?

Is full S/MIME support for independently configured secondary Microsoft 365 accounts planned?

How can we permanently access S/MIME-signed attachments in all configured accounts without repeatedly changing the primary account or switching to Outlook on the web?

Switching between primary accounts is not an acceptable permanent solution in a business environment.

We would appreciate an official technical clarification and a permanent solution.

Outlook | Windows | New Outlook for Windows | For business
0 comments No comments

1 answer

Sort by: Most helpful
  1. Jayden-P 4,465 Reputation points Independent Advisor
    2026-11-20T14:04:11.53+00:00

    Please note that this forum is not Microsoft Support. This is a user-to-user community forum, and responses are provided by community members based on publicly available information, documentation, and personal experience.

    Hi @Michael Paulke

    Based on the information provided, the behavior appears to be related to how New Outlook for Windows currently handles S/MIME-signed messages in secondary accounts.

    According to the article, S/MIME processing in New Outlook is tied to the primary account context. When an S/MIME-signed message is viewed from a secondary account, Outlook may not fully process the S/MIME container. For messages that use Opaque Signing, the original attachments are stored within that container, which can result in attachments not being displayed even though they still exist in the mailbox.

    Ref: New Outlook: S/MIME signature cannot be verified in secondary account, attachments missing | Rafael …

    This information is provided as a convenience to you. These sites are not controlled by Microsoft, and cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

    Because public documentation does not clearly state whether this is an intended limitation or a product defect, I recommend opening a support case through the Microsoft 365 Admin Center. Microsoft Support can verify whether this behavior is associated with a known issue, determine whether a fix is available or planned, and provide an authoritative statement regarding support for S/MIME in secondary accounts.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.