Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 22:54 UTC Customize Public modeDiscuss ChangeIntel on Discord

Outlook: Improved handling of disallowed and failed email reactions

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
558442

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 18 May 2026 early May 2026, late May 2026, early June 2026, late June 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated May 18, 2026: We have updated the timeline. Thank you for your patience.  Introduction We’re improving how Outlook respects the x‑ms‑reactions: disallow header in Classic Outlook for Windows. This update ensures that when reactions are disallowed, the Reactions button is correctly disabled and any failed reaction attempts are fully reverted. This provides a more consistent and trustworthy user experience across Outlook clients and prevents user confusion. This message is associated with Roadmap ID 558442. When this will happen: Current Channel: This change has rolled out as part of version 2904 (build 19929). Monthly Enterprise Channel: This change has rolled out as part of version 2904 (build 19929). Semi-Annual Enterprise Channel: This change will be rolled out as part of version 2904 (build 19929). How this affects your organization: Who is affected: Users running Classic Outlook for Windows Organizations that disallow email reactions using the x‑ms‑reactions: disallow header What will happen: The Reactions button will appear grayed out when reactions are disallowed. Failed reaction attempts will be automatically undone in the UI. Users will no longer see misleading reaction states. Behavior will be consistent across all Outlook clients. The change is enabled by default and respects existing configurations. What you can do to prepare: No action is required. You may optionally: Inform helpdesk staff about the improved reaction behavior to reduce potential user questions. Review internal documentation if you reference reaction controls or messaging headers. Continue using the x‑ms‑reactions: disallow header as you do today; existing configurations are fully supported. Learn more: Disallow reactions in Outlook | Microsoft Learn Compliance considerations: No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first
    • Tags Feature update, User impact → Updated message, Feature update, User impact

    Updated May 18, 2026: We have updated the timeline. Thank you for your patience.  Introduction We’re improving how Outlook respects the x‑ms‑reactions: disallow header in Classic … This message is associated with Roadmap ID 558442. When this will happen: Public Preview (Worldwide): We will begin rolling out early May 2026 and expect to complete by late May 2026. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early June 2026 and expect to complete by late June 2026.Current Channel: This change has rolled out as part of version 2904 (build 19929). Monthly Enterprise Channel: This change has rolled out as part of version 2904 (build 19929). Semi-Annual Enterprise Channel: This change will be rolled out as part of version 2904 (build 19929). How this affects your organization: Who is affected: Users running Classic Outlook …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 22:54 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current