New Microsoft Outlook and Outlook for the web: New setting to enable two-click view for encrypted emails

Updated June 11, 2025: We have updated the content. Thank you for your patience.

New Outlook for Windows desktop, Outlook for the web, Outlook iOS and Outlook Android will soon support a two-click view for encrypted emails, which requires user confirmation before allowing access to encrypted emails. As an admin, you can enable the two-click feature for your users.

This message is associated with Microsoft 365 Roadmap ID 483883.

When this will happen:

General Availability (Worldwide): We will begin rolling out early April 2025 and expect to complete by late April 2025.

General Availability (GCC): We will begin rolling out early May 2025 and expect to complete by late May 2025.

General Availability (Worldwide, GCC): For Android and iOS, we will begin rolling out mid-June 2025 and expect to complete by late June 2025.

How this will affect your organization:

With this two-click feature enabled, users will be required to select View message for every encrypted email, and then the email will render. This feature ensures that users deliberately access encrypted email content, reducing the risk of accidental exposure, especially in unsecured environments like public spaces or during screen sharing:

Admins can find the TwoClickMailPreviewEnabled setting in the Microsoft Azure directory. This setting is a Boolean type with default = 0, which means the experience is disabled by default. To enable the feature for all users in your tenant, set value = 1.

Alternatively, you can access and set the value for this setting using the Microsoft PowerShell cmdlet -Set-OrganizationConfiguration in the Microsoft Exchange Online PowerShell. Learn more: Exchange Online PowerShell | Microsoft Learn

By default, the two-click setting is off.

What you need to do to prepare:

No action is required from admins unless you want to enable this feature.

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation if you plan to enable this feature.