A frustrating bug in legacy Outlook for Mac has been confirmed by Microsoft, causing the original message body to vanish whenever a user replies to or forwards an email. The confirmation came on June 17, 2026, through a post on the company’s community forums, where a Microsoft representative acknowledged that the Outlook team is actively investigating the issue. For organizations and individuals still relying on the classic Mac client, the glitch has turned everyday email actions into productivity roadblocks, stripping away critical conversation context and leaving only empty headers.

What is the legacy Outlook for Mac?

To understand the scope of this bug, it’s important to distinguish between the two versions of Outlook available for macOS. The legacy Outlook for Mac—often referred to as classic Outlook—is the traditional application that shipped as part of Office for Mac since 2011. Users can identify it by its purple icon and the version number starting with 16 (as in 16.xx). It was the standard email client for Mac users in corporate environments for years, offering deep integration with Exchange Server and on-premises infrastructure.

In October 2020, Microsoft introduced a completely redesigned experience called the new Outlook for Mac. Built on Microsoft sync technology and optimized for Apple Silicon, it brought performance improvements, a cleaner interface, and better alignment with the Windows and web versions. By 2023, the new Outlook became the default for most Microsoft 365 subscribers, though the legacy client remained available as a toggleable option. Microsoft has been gradually nudging users toward the new version, stating that it would eventually replace the classic client. However, many organizations have kept the legacy version enabled due to feature gaps—such as lack of support for public folders, certain add-ins, or some advanced delegation scenarios.

As of 2026, the legacy client is in maintenance mode, receiving only critical security updates. This bug, therefore, hits a user base that may already be planning a migration but hasn’t yet completed it—or one that is forced to stay on legacy because of unresolved compatibility needs.

The bug in detail

According to the Microsoft confirmation, when a user of legacy Outlook for Mac clicks Reply, Reply All, or Forward on any email, the compose window that opens often fails to include the original message body. Instead, only the header fields—To, From, Subject, and Date—appear, leaving a completely blank area where the previous email’s text should be. In some cases, the headers themselves may be missing or truncated, but the consistent symptom is an empty email body.

The result is that users cannot see what they are responding to or forwarding. In lengthy email threads, this loss of context is more than an inconvenience; it can lead to miscommunication, missed action items, and a breakdown in collaborative workflows. For legal, healthcare, or financial sectors that rely on email chains as informal records, the bug raises serious documentation concerns.

The issue appears to affect all account types configured in legacy Outlook—Exchange Online, on-premises Exchange, IMAP, and POP—but the majority of reports stem from Microsoft 365 and Exchange Online users. This suggests that a server-side change, possibly in the way Exchange Online Web Services (EWS) delivers message content to the legacy client, may be triggering the problem. The bug does not impact the new Outlook for Mac, Outlook on the web (OWA), or Outlook for Windows.

Microsoft’s acknowledgment and investigation

On June 17, 2026, a Microsoft employee posted on the official Microsoft Community forums acknowledging the bug. The statement, paraphrased from the forum post, indicated: “We’re aware of an issue in legacy Outlook for Mac where the original message body is missing from replies and forwarded emails. The Outlook engineering team is investigating and will provide an update once a fix is available.”

No further details on the root cause or an estimated time of arrival (ETA) for a patch were provided. Given that legacy Outlook for Mac is no longer actively developed, fixing this bug may require a specific hotfix or an update to the existing 16.x branch. Microsoft’s support lifecycle for Office for Mac typically ties to the support end date of the suite version; however, classic Outlook exists in a gray area because it is distributed via the Microsoft 365 subscription. As such, Microsoft is obligated to address functionality-breaking issues, but the response time may be longer than for the current version.

IT administrators can track the official status through the Microsoft 365 admin center’s Message Center or the Service Health Dashboard (SHD). As of this writing, no incident ID has been publicly shared, but any service degradation should appear under Exchange Online or Outlook for Mac.

Impact on users and organizations

The blank body bug strikes at the heart of email-based communication. In environments where employees handle dozens of threaded conversations daily, losing the original text means either composing a reply purely from memory—risking mistakes—or manually copying and pasting the text from the reading pane before hitting Reply. Over hours and days, this adds significant friction.

Helpdesks at affected organizations have reported a spike in tickets since the bug surfaced. Common user complaints include confusion about whether the email was sent correctly, lost replies, and wasted time reconstructing discussions. For teams that rely on email forwarding for approvals, ticketing, or reporting, the absence of the original body can break automated parsing scripts that depend on embedded content.

Furthermore, the bug undermines confidence in the legacy platform. Many decision-makers were already considering a move to the new Outlook or alternative email clients. This incident may accelerate those migration plans. Microsoft’s own recommendation has been clear for years: users should transition to the new Outlook for Mac to benefit from ongoing feature updates, better performance, and modern security features. The bug serves as a practical reminder that relying on sunset software carries operational risk.

Workarounds until a fix arrives

While Microsoft has not yet published an official workaround, several temporary measures can restore some functionality:

  • Switch to the new Outlook for Mac – The most straightforward solution is to toggle on the new Outlook. In legacy Outlook, go to the Help menu and select “New Outlook” (or turn on the “New Outlook” slider in the top-right corner). The new version is unaffected and will display the original message body in replies and forwards as expected. Organizations should test this with critical workflows first, as some add-ins or public folder access may not be available.

  • Use Outlook on the web (OWA) – The browser-based version offers full functionality and is always up to date. Users can log in at outlook.office.com and reply to emails without losing the original body. This is a lightweight, zero-install fallback that requires no configuration.

  • Manual copy-paste – For those who must stay on legacy and can tolerate a clumsy workaround: open the email in the reading pane, select and copy the entire text (Cmd+C), then click Reply or Forward, and paste the copied content into the body of the new message. This preserves at least the visible text, though formatting and inline images may be lost.

  • Open the email in a separate window – Some users have reported that if you double-click an email to open it in its own window before clicking Reply, the original body sometimes survives the transition. This behavior is inconsistent and not officially documented, but it may help in a pinch.

  • Use “Forward as Attachment” – For forwarding needs, the “Forward as Attachment” option (via the Message menu) retains the full email including its body as an .eml file. This is useful for record-keeping but doesn’t help with inline replies.

No registry hacks or terminal commands are currently known to resolve the issue at the system level. Users should avoid resetting Outlook profiles or reinstalling the app unless advised by Microsoft, as these actions rarely fix bugs caused by server-client interaction.

The broader context: sunset of legacy Outlook for Mac

This bug lands at a time when legacy Outlook for Mac is already on borrowed time. Microsoft’s official roadmap indicated that the new Outlook would eventually become the only Outlook for Mac, with the classic client removed entirely. While a specific hard cutoff date hasn’t been announced for all customers, enterprise tenants have been given ample notice. In fact, Microsoft 365 apps for macOS version 16.75 (released in mid-2024) marked the last version to ship with both the new and legacy experience selectable by default; later builds made the new experience the default, with legacy buried as an advanced option.

For organizations still clinging to legacy, the primary blockers have been:

  • Public folder support – The new Outlook introduced read-only public folders only in 2023; full write capability remains limited.
  • Add-in compatibility – COM add-ins built for classic Outlook do not function in the new version. Some third-party solutions have not yet provided JavaScript-based replacements.
  • Shared and delegate mailbox behaviors – The new client handles some delegation scenarios differently, which can confuse automations and users.
  • MacOS version requirements – The new Outlook requires macOS 10.14 Mojave or later; however, machines stuck on older OS releases cannot run it.

Given these barriers, many IT departments have delayed migration, leaving a substantial installed base of legacy users vulnerable to this bug. This incident may be the push needed to resolve those blockers and complete the transition.

Implications for Windows users and cross-platform environments

While the blank body bug is exclusive to legacy Outlook for Mac, it’s not without consequences for Windows users. In many organizations, email threads involve participants on both platforms. If a Mac user replies without including the original thread, Windows recipients may see an out-of-context message, leading to disjointed conversations. Additionally, shared mailboxes or delegation setups—where a Mac user acts on behalf of a Windows colleague—can result in the forwarded or replied-to email arriving with a blank body, garbling workflows that depend on the full context.

Windows administrators who manage hybrid environments should be aware of this issue and proactively communicate workarounds to their Mac-using colleagues. This is especially important in remote or hybrid work settings, where email remains the backbone of asynchronous collaboration. No action is required on the Windows side, but monitoring the Microsoft 365 admin center for updates is advisable, particularly if the investigation reveals an Exchange Online service incident that could have broader impact.

How we got here: a history of similar Outlook bugs

Outlook has a long history of formatting oddities, from scrambled HTML rendering to missing inline attachments. The current bug is reminiscent of two past incidents:

  • Blank reply bodies due to corrupted NormalEmail.dotm (Windows) – In 2019, some Windows Outlook users found that replies were blank because a damaged template file prevented content from being inserted. The fix involved deleting the template, but that required a different architecture.
  • Missing body in Outlook for Mac after macOS upgrades (2021) – After certain macOS updates, some Mac users experienced blank reply bodies if the default mail format was set to RTF or if the .olk14/15Message cache was corrupted. Rebuilding the profile or switching to HTML format sometimes helped.

However, this new bug appears distinct because it correlates with a server-side component rather than local corruption. Users across different organizations began reporting the issue simultaneously, which points to a change on Microsoft’s end—possibly in the way Exchange Online processes the “PR_IN_REPLY_TO_ID” or “PR_BODY” properties for legacy EWS clients. Until the Outlook team completes its root cause analysis, these details remain speculative.

Preparing for the fix and next steps

When Microsoft eventually releases a patch, it will likely come in the form of an Office for Mac update. Because the legacy client persists in the same installation package as the new Outlook, updates are typically delivered through the AutoUpdate (MAU) tool or via Microsoft’s CDN. IT admins should ensure that their Mac fleet is configured to receive automatic updates from the “Current Channel” or “Monthly Enterprise Channel,” as appropriate.

Organizations that cannot wait for a patch should accelerate their migration to the new Outlook. A phased approach works best:

  1. Pilot group testing – Identify a small set of users who are not heavily reliant on public folders or legacy add-ins. Enable the new Outlook for them and gather feedback on missing features.
  2. Address gaps – Work with add-in vendors to secure JavaScript-based alternatives. Evaluate whether public folder usage can shift to shared mailboxes or Microsoft 365 Groups.
  3. User training – Brief employees on the interface changes, especially the redesigned ribbon and the switch between mail and calendar using the lower-left module switcher.
  4. Full rollout – Use preferences (CFG) payloads or Intune policies to silently enable the new Outlook for all users and hide the legacy toggle.
  5. Monitor – Keep an eye on support tickets and the Microsoft 365 roadmap for further enhancements to the new Outlook that might close remaining parity gaps.

Microsoft’s own documentation provides extensive guidance on the migration process, and third-party consultants frequently offer adoption workshops. While the blank body bug is a nuisance, it also serves as a timely nudge to modernize before legacy support ends entirely.

Conclusion

The confirmed bug in legacy Outlook for Mac that blanks the original message body during replies and forwards is a significant disruption for users who depend on the aging client. With Microsoft’s investigation underway but no fix date in sight, the practical options are clear: switch to the new Outlook for Mac, use Outlook on the web, or adopt manual workarounds. IT leaders should treat this incident as a catalyst to complete their long-planned transition away from legacy software, ensuring their organizations remain productive and secure.