MC1261593 – M365 Change Digest

One-line summary

Outlook now properly disables the Reactions button when email reactions are disallowed, ensuring consistent behavior and avoiding user confusion across clients.

Similar updates

Details

RoadmapIds

558442

Summary

Outlook Classic for Windows now disables the Reactions button and reverts failed reaction attempts when the x-ms-reactions: disallow header is used, ensuring consistent behavior across clients. This update, rolled out in version 2904 (build 19929), requires no action but may prompt helpdesk updates.

Platforms

Desktop

Body (from Message Center)

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.

user settings

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.

Raw JSON (for debugging)

Expand/collapse the full payload below.

Show/hide raw

{
  "snapshot_item": {
    "action_required_by": null,
    "ai_action_required_by": "2026-05-01T00:00:00Z",
    "ai_actions": [
      "Inform helpdesk of new reaction behavior",
      "Review internal docs if referencing reactions"
    ],
    "ai_master_tags": [
      "User",
      "Admin"
    ],
    "ai_model": "gpt-4.1",
    "ai_summary": "Outlook now properly disables the Reactions button when email reactions are disallowed, ensuring consistent behavior and avoiding user confusion across clients.",
    "ai_topics": [
      "Exchange",
      "Outlook"
    ],
    "category": "stayInformed",
    "details_map": {
      "Platforms": "Desktop",
      "RoadmapIds": "558442",
      "Summary": "Outlook Classic for Windows now disables the Reactions button and reverts failed reaction attempts when the x-ms-reactions: disallow header is used, ensuring consistent behavior across clients. This update, rolled out in version 2904 (build 19929), requires no action but may prompt helpdesk updates."
    },
    "id": "MC1261593",
    "importance": 3,
    "is_major_change": false,
    "last_modified": "2026-05-18T17:32:02Z",
    "ms_products": [
      "Exchange"
    ],
    "platforms": "Desktop",
    "roadmap_ids": [
      "558442"
    ],
    "services": [
      "Exchange Online"
    ],
    "severity": "normal",
    "tags": [
      "Updated message",
      "Feature update",
      "User impact"
    ],
    "title": "(Updated) Outlook: Improved handling of disallowed and failed email reactions"
  }
}