(Updated) Outlook: Support for storing S/MIME certificates in contacts in new Outlook

Message ID

MC1302908

Services

Exchange OnlineMicrosoft 365 apps

Summary

The new Outlook for Windows will support storing S/MIME certificates directly in Contacts, enabling encrypted emails and seamless transition from classic Outlook. Rollout starts late May 2026 worldwide, mid-June for GCC. No admin action needed; users should add certificates and update documentation accordingly.

Details

Updated May 27, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

The 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.

This message is associated with Microsoft 365 Roadmap ID 518288.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in late May 2026 (previously mid-May) and expect to complete by mid-June 2026 (previously late May).
General Availability (GCC): We will begin rolling out in mid-June 2026 (previously early June) and expect to complete by late June 2026.

[How this affects your organization:]

Who is affected:

Users of new Outlook for Windows
Organizations that use S/MIME encryption

What will happen:

Users can store recipients’ S/MIME public certificates directly in Contacts.

Screenshot: To add a S/MIME certificate, go to Your contacts > Certificates > Add certificate:

Add certificate option in contacts.

Stored certificates can be used to encrypt outgoing email to those recipients.
Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.
Feature is available by default; no admin configuration required.
No impact to users who are not using new Outlook for Windows.

[What you can do to prepare:]

No admin action is required to enable this feature.
If your organization uses S/MIME:
- Instruct users to add or import S/MIME public certificates into Contacts.
- Communicate how to select S/MIME encryption when composing emails. Learn more: Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support.
Update internal documentation for users transitioning from classic Outlook.
Inform helpdesk teams of this improved certificate handling experience.

[Compliance considerations:]

Area	Explanation
Does 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.
Does 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.

Change History

Show

Published: May 6, 2026

Last Updated: May 27, 2026

May 27, 2026 at 6:30 PM Updated

Summary

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 late-May 2026, requires no admin setup, and improves secure communication for organizations using S/MIME encryption.

New

Last Updated Date

2026-05-21T16:16:43.517Z

New

2026-05-27T16:58:33.307Z

Body Content

Updated May 21, 2026: We have updated the timeline. Thank you for your patience. [Introduction] The 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. This message is associated with Microsoft 365 Roadmap ID <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=518288" target="_blank">518288</a>. [When this will happen:] <ul> <li>General Availability (Worldwide): We will begin rolling out in late May 2026 (previously mid-May) and expect to complete late May 2026. </li><li>General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by late June 2026.</li> </ul> [How this affects your organization:] Who is affected: <ul> <li>Users of new Outlook for Windows</li> <li>Organizations that use S/MIME encryption</li> </ul> What will happen: <ul> <li>Users can store recipients’ S/MIME public certificates directly in Contacts.</li>Screenshot: To add a S/MIME certificate, go to Your contacts > Certificates > Add certificate:<img src="https://cxcs.microsoft.net/file/ccp/en-us/5f20f0ad-0dbc-4652-8558-c3e21b7ae72b" style="width: 400px;" alt="Add certificate option in contacts."> <li>Stored certificates can be used to encrypt outgoing email to those recipients.</li> <li>Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.</li> <li>Feature is available by default; no admin configuration required.</li> <li>No impact to users who are not using new Outlook for Windows.</li> </ul> [What you can do to prepare:] <ul> <li>No admin action is required to enable this feature.</li> <li>If your organization uses S/MIME: <ul> <li>Instruct users to add or import S/MIME public certificates into Contacts.</li> <li>Communicate how to select S/MIME encryption when composing emails. Learn more: <a href="https://support.microsoft.com/office/send-s-mime-or-microsoft-purview-encrypted-emails-in-outlook-373339cb-bf1a-4509-b296-802a39d801dc" target="_blank">Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support</a>.</li> </ul> </li> <li>Update internal documentation for users transitioning from classic Outlook.</li> <li>Inform helpdesk teams of this improved certificate handling experience.</li> </ul> [Compliance considerations:]<table class="table table-bordered"><tbody><tr><td>Area</td><td>Explanation</td></tr><tr><td>Does the change store new customer data?</td><td>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.</td></tr><tr><td>Does the change alter how existing customer data is processed, stored, or accessed?</td><td>Existing certificates stored in classic Outlook Contacts are now accessible in new Outlook, improving continuity.</td></tr></tbody></table>

New

Updated May 27, 2026: We have updated the timeline. Thank you for your patience. [Introduction] The 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. This message is associated with Microsoft 365 Roadmap ID <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=518288" target="_blank">518288</a>. [When this will happen:] <ul> <li>General Availability (Worldwide): We will begin rolling out in late May 2026 (previously mid-May) and expect to complete by mid-June 2026 (previously late May). </li><li>General Availability (GCC): We will begin rolling out in mid-June 2026 (previously early June) and expect to complete by late June 2026.</li> </ul> [How this affects your organization:] Who is affected: <ul> <li>Users of new Outlook for Windows</li> <li>Organizations that use S/MIME encryption</li> </ul> What will happen: <ul> <li>Users can store recipients’ S/MIME public certificates directly in Contacts.</li>Screenshot: To add a S/MIME certificate, go to Your contacts > Certificates > Add certificate:<img src="https://cxcs.microsoft.net/file/ccp/en-us/5f20f0ad-0dbc-4652-8558-c3e21b7ae72b" style="width: 400px;" alt="Add certificate option in contacts."> <li>Stored certificates can be used to encrypt outgoing email to those recipients.</li> <li>Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.</li> <li>Feature is available by default; no admin configuration required.</li> <li>No impact to users who are not using new Outlook for Windows.</li> </ul> [What you can do to prepare:] <ul> <li>No admin action is required to enable this feature.</li> <li>If your organization uses S/MIME: <ul> <li>Instruct users to add or import S/MIME public certificates into Contacts.</li> <li>Communicate how to select S/MIME encryption when composing emails. Learn more: <a href="https://support.microsoft.com/office/send-s-mime-or-microsoft-purview-encrypted-emails-in-outlook-373339cb-bf1a-4509-b296-802a39d801dc" target="_blank">Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support</a>.</li> </ul> </li> <li>Update internal documentation for users transitioning from classic Outlook.</li> <li>Inform helpdesk teams of this improved certificate handling experience.</li> </ul> [Compliance considerations:]<table class="table table-bordered"><tbody><tr><td>Area</td><td>Explanation</td></tr><tr><td>Does the change store new customer data?</td><td>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.</td></tr><tr><td>Does the change alter how existing customer data is processed, stored, or accessed?</td><td>Existing certificates stored in classic Outlook Contacts are now accessible in new Outlook, improving continuity.</td></tr></tbody></table>

May 21, 2026 at 6:30 PM Updated

Title

Outlook: Support for storing S/MIME certificates in contacts in new Outlook

New

(Updated) Outlook: Support for storing S/MIME certificates in contacts in new Outlook

Summary

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 encryption.

New

Last Updated Date

2026-05-06T22:54:47.193Z

New

2026-05-21T16:16:43.517Z

Tags

New feature,User impact

New

Updated message,New feature,User impact

Body Content

[Introduction] The 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. This message is associated with Microsoft 365 Roadmap ID <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=518288" target="_blank">518288</a>. [When this will happen:] <ul> <li>General Availability (Worldwide): We will begin rolling out in mid-May 2026 and expect to complete by late May 2026. </li><li>General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by late June 2026.</li> </ul> [How this affects your organization:] Who is affected: <ul> <li>Users of new Outlook for Windows</li> <li>Organizations that use S/MIME encryption</li> </ul> What will happen: <ul> <li>Users can store recipients’ S/MIME public certificates directly in Contacts.</li>Screenshot: To add a S/MIME certificate, go to Your contacts > Certificates > Add certificate:<img src="https://cxcs.microsoft.net/file/ccp/en-us/5f20f0ad-0dbc-4652-8558-c3e21b7ae72b" style="width: 400px;" alt="Add certificate option in contacts."> <li>Stored certificates can be used to encrypt outgoing email to those recipients.</li> <li>Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.</li> <li>Feature is available by default; no admin configuration required.</li> <li>No impact to users who are not using new Outlook for Windows.</li> </ul> [What you can do to prepare:] <ul> <li>No admin action is required to enable this feature.</li> <li>If your organization uses S/MIME: <ul> <li>Instruct users to add or import S/MIME public certificates into Contacts.</li> <li>Communicate how to select S/MIME encryption when composing emails. Learn more: <a href="https://support.microsoft.com/office/send-s-mime-or-microsoft-purview-encrypted-emails-in-outlook-373339cb-bf1a-4509-b296-802a39d801dc" target="_blank">Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support</a>.</li> </ul> </li> <li>Update internal documentation for users transitioning from classic Outlook.</li> <li>Inform helpdesk teams of this improved certificate handling experience.</li> </ul> [Compliance considerations:]<table class="table table-bordered"><tbody><tr><td>Area</td><td>Explanation</td></tr><tr><td>Does the change store new customer data?</td><td>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.</td></tr><tr><td>Does the change alter how existing customer data is processed, stored, or accessed?</td><td>Existing certificates stored in classic Outlook Contacts are now accessible in new Outlook, improving continuity.</td></tr></tbody></table>

New

Never Miss a Microsoft 365 Update

Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.

Explore Dashboard Sign Up Free