How to Recall an Email in New Outlook and Check the Result

November 10, 2026

Sent the wrong attachment or noticed a mistake just after sending? New Outlook and Outlook on the web can request removal of an eligible message from recipients’ mailboxes. Submitting the request is only the first step: check the recall report before assuming it worked.

Documentation reviewed: 10 November 2026. These instructions were verified against the Microsoft sources below; Guava has not independently executed this procedure in a live environment.

Scope, accounts, and permissions

This guide covers your own Microsoft 365 work or school mailbox in Exchange Online, using new Outlook for Windows or Outlook on the web, with recipients in the same organization. You need access to that mailbox and its sent message; the user procedure does not require an administrator role.

Personal Outlook.com, Hotmail, and Gmail accounts are outside this workflow. Your organization must provide the appropriate Exchange Online mailbox entitlement and allow the recall capability. This guide does not ask you to purchase a separate add-on or change tenant-wide policy.

Documentation caveat: Microsoft’s general Outlook support page describes recall as limited to unread messages. Its Exchange Online administrator documentation says cloud-based recall can also remove read messages when the organization allows it. This guide uses the support page for client navigation and the administrator documentation for service behavior. Do not assume a message becomes unrecoverable solely because it was opened—or that recall erases what the recipient has already seen.

1. Open the original sent message

  1. In new Outlook or Outlook on the web, select the correct work or school account.
  2. Open Sent Items.
  3. Double-click the original email to open it in a separate window.
  4. Check the recipients, subject, and attachment before proceeding. Avoid recalling a similarly named message by mistake.

2. Request the recall

  1. On the message ribbon, choose Recall Message.
  2. Select OK in the confirmation dialog.
  3. Return to your inbox and look for the Message Recall Report.

If you need to provide corrected information, prepare a separate, clearly labelled correction. Review the attachment and recipients again before sending it. Do not assume that starting recall automatically creates or sends your replacement.

3. Verify the result for every recipient

Open the report’s link and inspect each recipient’s status. The service can continue trying for up to 24 hours.

Reported result Practical response
Succeeded The recall completed for that recipient. It does not establish that nobody previously read, photographed, or copied the contents.
Pending The result is unresolved. Check again later; do not describe the message as successfully withdrawn.
Failed Treat the original as still available to that recipient and take the appropriate corrective action.

For a low-risk practice exercise, agree on a test with a colleague, send a harmless message, recall it, and compare the report with what they see. Record the client and tenant conditions. A successful practice run does not guarantee every later recall.

Encrypted email: Microsoft documents additional requirements for recalling messages protected with OME or MIP labels, including the Premium Encryption service plan for the sender and use of new Outlook or Outlook on the web. Ask IT to verify eligibility rather than assuming ordinary-mail behavior applies.

Common problems

  • Recall is missing: confirm the account type and that you opened the sent message separately. Ask IT whether the feature is available in your tenant; do not switch organization settings yourself.
  • The message is too old: administrators can configure a maximum recallable age. Microsoft documents a default of 365 days, with a configurable range from five minutes to ten years.
  • No report arrives: Microsoft identifies Office365Reports@microsoft.com as the report sender. IT can investigate filtering or message trace; do not broadly disable mail protection.
  • External or hybrid recipient: ordinary internet delivery and on-premises Exchange recipients are not covered by this same-organization cloud procedure. Microsoft also documents cross-tenant recall scenarios, but those are outside this walkthrough and should be checked with IT.
  • Shared or delegated mailbox: additional recall and report-access limitations apply. Use the administrator documentation rather than assuming the personal-mailbox steps are equivalent.

Security and follow-up

Recall is not incident containment. If the email disclosed credentials, personal information, or confidential business data, notify your security or privacy contact promptly and follow the incident process. Do not wait for a successful report before reporting the exposure.

Recipient notifications depend on tenant settings, so do not promise a silent recall. Microsoft also documents limits on recalling forwarded copies. There is no rollback procedure offered here for a completed recall; if appropriate, send a carefully reviewed replacement.

For messages that benefit from review time, see how to schedule email in new Outlook and the web. For recurring inbox organization, see how to create new Outlook rules.

Sources

Topics:
Read next
November 21, 2026

How to Create and Configure a Shared Mailbox in Microsoft 365

Create a Microsoft 365 shared mailbox, grant the correct Full Access and Send As permissions, understand automapping and licensing, and verify that users can work from Outlook safely.
November 17, 2026

Microsoft 365 Business Basic vs Standard vs Premium vs E3 in Canada (2026): Which Plan Should You Buy?

A practical Canadian comparison of Microsoft 365 Business Basic, Standard, Premium, and E3, including verified November 2026 pricing, feature differences, user limits, hidden costs, and recommendations by business need.