{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihje6bnkyzwwz2ylut4enaofbzyxtlntbdg3pgztaswl2gbdgwzjm",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3ml7vxpnaaqn2"
  },
  "description": "The new Outlook for Windows will support storing S/MIME certificates directly in Contacts, enabling encrypted emails and continuity from classic Outlook. This feature rolls out worldwide mid-May 2026, requires no admin setup, and improves secure communication for organizations using S/MIME encryp...",
  "path": "/m365-message-center/message/mc1302908/",
  "publishedAt": "2026-05-07T00:00:11.000Z",
  "site": "https://blog.tophhie.cloud",
  "tags": [
    "518288",
    "Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support"
  ],
  "textContent": "**[Introduction]**\n\nThe**new Outlook for Windows** now allows users to store **S/MIME** encryption certificates directly within Contacts. This capability enables users to save recipients’ public certificates and use them to send S/MIME encrypted emails, improving secure communication and continuity when transitioning from **classic Outlook for Windows (Win32)**. Certificates previously stored in Contacts in classic Outlook will automatically be available in new Outlook.\n\nThis message is associated with Microsoft 365 Roadmap ID 518288.\n\n**[When this will happen:]**\n\n  * General Availability (Worldwide): We will begin rolling out in **mid-May 2026** and expect to complete by **late May 2026**.\n  * General Availability (GCC): We will begin rolling out in **early June 2026** and expect to complete by **late June 2026**.\n\n\n\n**[How this affects your organization:]**\n\n**Who is affected:**\n\n  * Users of **new Outlook for Windows**\n  * Organizations that use **S/MIME encryption**\n\n\n\n**What will happen:**\n\n  * Users can store recipients’ S/MIME public certificates directly in Contacts.\n  * Screenshot: _To add a S/MIME certificate, go to**Your contacts** > **Certificates** > **Add certificate** :_\n  * Stored certificates can be used to encrypt outgoing email to those recipients.\n  * Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.\n  * Feature is **available by default** ; no admin configuration required.\n  * No impact to users who are not using new Outlook for Windows.\n\n\n\n**[What you can do to prepare:]**\n\n  * No admin action is required to enable this feature.\n  * If your organization uses S/MIME:\n    * Instruct users to add or import S/MIME public certificates into Contacts.\n    * Communicate how to select S/MIME encryption when composing emails. Learn more: Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support.\n  * Update internal documentation for users transitioning from classic Outlook.\n  * Inform helpdesk teams of this improved certificate handling experience.\n\n\n\n**[Compliance considerations:]**\n\n**Area**| **Explanation**\n---|---\nDoes the change store new customer data?| Classic Outlook already has this capability, and we are bringing it to new Outlook as well. S/MIME public certificates can now be stored in Outlook Contacts; these persist as part of contact data.\nDoes the change alter how existing customer data is processed, stored, or accessed?| Existing certificates stored in classic Outlook Contacts are now accessible in new Outlook, improving continuity.",
  "title": "MC1302908: Outlook: Support for storing S/MIME certificates in contacts in new Outlook",
  "updatedAt": "2026-05-07T00:00:12.045Z"
}