How to Recall an Email in Outlook Before Someone Reads It

Yes, you can recall an email in Outlook. If you last tried this a few years ago and gave up, the feature you remember is not the feature you have today.

In April 2023, the Microsoft Exchange engineering team quietly replaced the ancient client-based recall with Cloud-based Message Recall. The old version asked the recipient’s copy of Outlook for Windows to delete a message on your behalf. Microsoft’s own telemetry at the time was brutal, showing roughly 800,000 recall attempts every day with only about a 40 percent success rate. Since the rebuild, the recall runs as a server-side agent inside Exchange Online against the recipient’s cloud mailbox, and Microsoft reports success rates above 90 percent.

That single architectural change invalidated most of the advice still floating around the web. Recall now works even if the recipient has already read the message. It works if they have filed it in a subfolder. It works if they are on a Mac, an iPhone, or a third-party IMAP client because their client is no longer part of the transaction at all.

What has not changed is the boundary. Recall lives inside the Exchange Online service boundary. If you sent that message to Gmail, Yahoo, iCloud, Outlook.com, or a colleague at another company, there is nothing to recall. Your message is sitting on someone else’s server, and Microsoft has no authority there. That boundary is finally moving too. Cross-Tenant Message Recall, announced by the Exchange team on 10 July 2026, begins rolling out mid-August 2026 and completes by mid-September 2026. It is off by default and requires the receiving organisation to allow-list your tenant.

Below is exactly how to check whether your message is eligible, how to trigger the recall from every Outlook client, how to read the status report properly, and what a competent recovery looks like when recall is not an option.

When Email Recall Actually Works

Email was designed for interoperability, not for centralised control. Once a message crosses into another organisation’s mail system, it is that organisation’s data. SMTP has no “take it back” verb, and no vendor can invent one unilaterally. That is why recall has always been, and remains, a tenant-scoped feature.

Inside your own Microsoft 365 tenant, the picture is completely different. When you trigger a recall, Outlook generates a hidden message of class IPM.Outlook.Recall. The Transport Message Recall Agent in Exchange Online intercepts it and attempts a hard-delete of the original directly from each recipient’s cloud mailbox. The recipient’s laptop can be shut in a bag in an airport and the deletion still happens. The message is simply gone the next time their client syncs.

Situation	Can recall work?
Same Microsoft 365 / Exchange Online tenant	Yes, typically over 90 percent success
Different Microsoft 365 tenant (partner, client, supplier)	Not today, cross-tenant recall from mid-Aug 2026 if they allow-list you
Hybrid (sent from cloud mailbox to on-premises Exchange)	No
Gmail / Google Workspace	No
Outlook.com, Hotmail, Live (personal accounts)	No
Yahoo Mail, iCloud, Proton	No
Recipient already opened the message	Yes, unless your admin disabled read-message recall
Message was auto-forwarded outside the organisation	No

The “Already-Read” Factor

Two details in that table catch experienced users out. First, already-read is no longer a blocker. The confirmation dialog inside Outlook still says only unread copies will be deleted, but Microsoft’s own documentation states plainly that this wording is out of date. Admins can turn read-message recall off, but the default is on.

The Hybrid Trap

Second, hybrid environments are a genuine trap. If your organisation still has mailboxes on an on-premises Exchange server, a message sent from a cloud mailbox to one of those mailboxes cannot be recalled, even though both people share the same email domain and the same GAL. If you work somewhere mid-migration, assume recall coverage is patchy until IT confirms otherwise.

Before Trying to Recall Your Email

The instinct after a bad send is to lunge for the recall button. Slow down for fifteen seconds because the triage matters more than the click.

Was it internal? Open the message in Sent Items and look at the actual SMTP addresses, not the display names. A distribution list that looks internal can quietly contain an external contact, and a single external recipient is the most common reason an internal recall comes back with mixed results.
Was there a forwarding rule in play? Recall follows automatic internal forwards, but it cannot touch a message a recipient forwarded manually, or one redirected by an Inbox rule, or anything auto-forwarded outside the organisation. If you emailed a shared team address that fans out externally, treat the message as unrecoverable.
Was the content actually sensitive, or merely embarrassing? This is the fork in the road. A typo or a missing attachment is a recall-or-follow-up problem. Regulated data, salary information, unreleased financials, or personal data covered by GDPR is an incident, not a mistake. Trigger the recall, then contact your security or compliance team in the same minute. Recall hard-deletes the message, but if the recipient’s mailbox is on Litigation Hold or In-Place Hold, the recalled message still surfaces in eDiscovery, which is exactly what a compliance investigation needs.
Was there a link rather than an attachment? If you sent a OneDrive or SharePoint link, recalling the email removes the pointer, not the permission. Revoking access on the file is the action that actually protects the data.

How to Recall an Email in Classic Outlook

Classic Outlook for Windows remains the most reliable place to trigger a recall, and it is supported by Microsoft through 2029.

Open the Sent Items folder and double-click the message so it opens in its own window. This is not a stylistic preference; selecting the message so it appears in the reading pane genuinely does not expose the recall command, and it is the single most common reason people conclude the feature has been removed.
On the Message tab, go to Actions and select Recall This Message. On newer builds, the command may appear directly as Recall Message.
Choose one of two options:
- Delete unread copies of this message: The agent attempts a hard-delete of the original from every internal recipient’s mailbox.
- Delete unread copies and replace with a new message: Same deletion, followed by a fresh compose window pre-filled with your original content, so you can fix the error and resend.

How to Replace the Original Email With an Updated Version

The replace option is the one worth learning properly because it converts a visible mistake into something most recipients never notice. Under the cloud model, the sequence is: the agent hard-deletes the original from the recipients’ mailboxes, and Outlook then sends your corrected message through normal delivery as an independent email.

The replacement is a new message with a new timestamp, not an edit. It will land at the top of the recipient’s inbox, so write it as though it stands alone. If you replace a message that had already generated a notification banner on someone’s phone, they may well have seen the preview text of the original. Assume the first line was read.
Use the second chance properly. Re-check the recipient list, re-attach the correct file, and re-read the opening sentence—the three things that go wrong most often. And check the To field specifically if the original error was a wrong-recipient send, because the compose window inherits the original addressing, including the person you never meant to email.
There is no third attempt. If the replacement is also wrong, you are now sending a correction to a correction, and the professional cost of that exceeds the cost of the original typo.

How Email Recall Works in the New Outlook

Message Recall is fully supported in the new Outlook for Windows, and because the heavy lifting happens server-side, it behaves identically to the classic client. Open Sent Items, double-click the message to open it in its own window, and select Recall Message on the ribbon, then confirm.

If the command is missing, work through the causes in order. The account must be a work or school Microsoft 365 or Exchange Online mailbox. Recall is not available on personal Outlook.com, Gmail, or POP accounts connected to new Outlook, which is why the option is absent for most home users. Your admin may have disabled the feature outright. If the message is genuinely external, the option may appear but the recall will simply report a failure.

One capability that is specific to the modern clients is recalling encrypted mail. Messages protected with Office 365 Message Encryption or Microsoft Purview sensitivity labels can be recalled only when the sender holds the Premium Encryption in Office 365 service plan, and only when the recall is triggered from new Outlook or Outlook on the web. Classic Outlook will not do it. If your organisation labels everything sensitive by policy, that detail decides which client you should be sitting in during an emergency.

Can You Recall an Email in Outlook on the Web?

Yes, and for a couple of scenarios, Outlook on the web is the best place to do it.

Sign in at outlook.office.com, open Sent Items, and open the message in its own window by double-clicking it or using the More actions menu represented by three dots. Select Recall Message and confirm.

The browser client is where I would start if you are on a Mac, if you are away from your usual machine, if the message was encrypted, or if classic Outlook is misbehaving with the Online-mode and multi-account limitations. You are talking directly to the service that performs the recall, with the fewest client-side variables in the way.

If Recall Message is absent in the web client on an internal message, that is a strong signal the feature has been disabled at the tenant level rather than a client bug. This is worth a one-line message to your helpdesk, because most admins leave it enabled and do not realise it is off.

What If You Are Using Outlook on Mac?

Outlook for Mac supports Message Recall. The old advice—that Mac users are locked out because the client lacks the Exchange hooks—described the client-based era accurately. Under cloud recall, the client’s only job is to generate the recall request message; the deletion is performed by the service. That is why parity across platforms became possible in the first place.

In practice, the ribbon on Mac has shifted across builds, so if you cannot find the command quickly, do not burn minutes hunting for it. Open the message in its own window and look for Recall Message. If it is not there, sign in to Outlook on the web and trigger it from there. Update to a current build of Outlook for Mac afterwards when you are no longer under time pressure.

How to Know Whether the Recall Worked

Recall is one of the few Outlook features that reports back honestly, and you should always read the report rather than assume.

Within roughly 30 seconds to a few minutes, you receive an email titled “Message Recall Report for message [subject]” sent from Office365Reports@microsoft.com. It contains a link to a web-based status report showing per-recipient results. This is a single consolidated page, replacing the flood of individual notification emails the classic feature used to generate. You may be prompted to sign in with your mailbox credentials to view it.

Succeeded: The original was hard-deleted from that recipient’s mailbox. Under the cloud model this holds even if they had opened it, though nothing can un-read a message someone has already read.
Pending: The service is still working. Exchange Online retries for up to 24 hours before giving up, so a pending status hours later is normal behaviour, not a stuck job.
Failed: The recall could not be completed for that recipient, such as an external address, forwarded message, on-premises mailbox, or the 24-hour window elapsed.
Mixed results: The usual outcome on group emails. Read it line by line and treat each failed recipient as someone who kept the message.

Why Outlook Could Not Recall Your Email

When a modern recall fails, the reason is almost always structural:

The recipient is outside your tenant: The dominant cause, and the one no setting fixes today. Cross-tenant recall changes this from mid-August 2026, but only between organisations that have explicitly allow-listed each other.
A forwarding rule moved the message: Manual forwards, Inbox-rule forwards, and redirects all place a copy beyond the agent’s reach. Auto-forwards to another internal mailbox are recalled; everything else is not.
The mailbox is on-premises: Hybrid organisations lose recall on the on-prem side of the boundary.
Your client configuration blocked it: Classic Outlook in Online mode, or a profile with multiple Exchange accounts, will not generate a valid recall request.
Your admin disabled it: Either the feature entirely or read-message recall specifically. Regulated industries often disable read-message recall deliberately because silently removing something an employee has already read has its own audit implications.
Third-party mail routing: If your organisation routes internal mail through an external security gateway, the message leaves the service boundary and comes back. Microsoft supports this “external round-trip” scenario, but only when inbound and outbound connectors are configured correctly.

What to Do If Email Recall Does Not Work

Pivot fast, and pivot proportionately. The response to a typo and the response to a data leak are not the same response.

For ordinary errors, reply to your own sent message with one clean line, such as “corrected file attached” or the corrected figure stated plainly. No apology paragraph, no explanation of how it happened. A same-minute correction reads as competence; a five-paragraph apology turns a small error into the thing people remember.

For a wrong-recipient send, say so directly to that person and ask them to delete it. It is an awkward message to write and it works far more often than any technical control, because most people are decent about it.

For sensitive content, act on the data rather than the email:

Revoke the link: If you shared a OneDrive or SharePoint file, open the file’s sharing settings and remove that person’s access. Recalling the email never touches the permission; this step does.
Revoke the encryption: If the message was protected with Advanced Message Encryption, you can revoke it from the Microsoft 365 admin centre or via PowerShell, even for external recipients. This is the closest thing to an external recall that actually exists today, and it is why encrypting genuinely sensitive mail is worth the friction.
Escalate to security or compliance: Report it as an incident. They can run message trace, check whether an attachment was opened or downloaded, and decide whether a regulator needs to hear about it. Regulatory clocks, such as 72 hours under GDPR, start at the point of discovery, not at the point you feel ready to talk about it.

Recall vs Undo Send

These two features get conflated constantly, and they solve different problems at different points in the message’s life.

Feature	Message Recall	Undo Send
When it works	After the message has been delivered	During a delay window before it leaves your mailbox
Where it runs	Exchange Online service, server-side	Your own client, before transmission
Supported accounts	Work/school Microsoft 365 and Exchange Online, same tenant	New Outlook, Outlook on the web, Outlook.com, mobile
Works with external	No (cross-tenant from Aug 2026, opt-in)	Yes, the message hasn’t been sent yet
Reliability	High inside the tenant (>90%), zero outside it	Effectively 100 percent, within the window
Best for	Internal mistakes discovered minutes or hours later	Anything you catch within a few seconds

Undo Send is a delayed send. The message sits in your mailbox for a configured window, up to 10 seconds in Outlook on the web and new Outlook, and the button simply cancels the queued send. Because the message never reached the recipient, there is nothing to recall and no report to read. It is the single highest-value setting in Outlook and it is off by default at the maximum value.

Prevent This From Happening Again

Recall is a fire extinguisher. These are the smoke detectors, and each one takes under two minutes to configure.

Set Undo Send to its maximum: Ten seconds catches the overwhelming majority of “wait, no” moments—wrong recipient, missing attachment, sent mid-sentence.
Build a one-minute delay rule in classic Outlook: In Rules → Manage Rules & Alerts, create a rule applying to all sent messages with the action defer delivery by a number of minutes. One minute is enough to spot most errors and short enough that nobody notices. The messages sit in your Outbox, where you can open, edit, or delete them.
Use Schedule Send for anything written after hours: Emails written late at night are the ones most likely to need recalling. Scheduling them for the next morning gives you a review window and spares your colleagues the 11pm notification.
Turn on the missing-attachment warning: In classic Outlook, File → Options → Mail → “Warn me when I send a message that may be missing an attachment.” It reads the body text for words like attached and stops you.
Address last: Write the message, attach the file, re-read it, and only then fill in the recipients. It feels unnatural for about a week and then it becomes the reason you never send a half-finished email again.
Apply sensitivity labels to genuinely sensitive content: Encryption travels with the file. If a labelled document reaches the wrong person, they cannot open it without authenticating. With Advanced Message Encryption you retain the ability to revoke access after the fact, including outside your organisation.
Check the distribution list before you reply-all: Expand it. Look for external contacts. Most accidental external disclosures start as an internal-looking reply.

Summary

Message recall in 2026 is a materially better tool than its reputation suggests. Since Microsoft moved it into the cloud in April 2023, it runs server-side against the recipient’s mailbox, succeeds more than 90 percent of the time inside a tenant, retrieves messages that have already been read or filed away, and can be triggered from Windows, Mac, the web, and mobile alike. From mid-August 2026, cross-tenant recall extends it, cautiously and by mutual consent between admins, to trusted partner organisations for the first time.

What has not changed is the boundary and the discipline. Recall stops at the edge of the Exchange Online service, so anything sent to Gmail, a personal account, or an unaffiliated company is gone. And the fastest fix for most mistakes remains an immediate, unfussy correction rather than a report you are refreshing your inbox waiting for. Turn on Undo Send, add a one-minute delay rule, label your sensitive documents, and treat recall as the safety net it is, not the plan.

Frequently Asked Questions

Can you recall an email after it has been opened?

Yes, in most organisations. Cloud-based Message Recall removed the read-message restriction, and Microsoft has confirmed that the warning still shown in Outlook’s recall dialog is outdated. Admins can switch this off, so it varies by tenant. Recall deletes the message but cannot “unsee” it for someone who has already read it.

Can Outlook recall emails sent to Gmail or Yahoo?

No. Recall operates only within the Exchange Online service boundary. For those recipients your only real options are a prompt correction or revoking access if you sent a link or Advanced Message Encryption–protected content.

What about email sent to a different company that also uses Microsoft 365?

Not yet, but this is changing. Cross-Tenant Message Recall rolls out from mid-August 2026 and completes by mid-September 2026. It is disabled by default; the receiving organisation’s admin must add your Microsoft Entra tenant ID to their allow list via PowerShell.

Can recipients tell you tried recalling the email?

Usually not under the cloud model. The message is hard-deleted from the mailbox by a service agent, and the recall request itself never appears as a visible email. If they had already opened or previewed it, they will notice it disappear. Assume they might, and do not rely on the recall being invisible.

Does Message Recall work on mobile?

Yes. Microsoft lists Outlook for Android and iOS among the supported clients for triggering a recall. Regardless of what the sender uses, the recipient’s device and app are irrelevant; the deletion happens in the cloud mailbox and syncs down.

How long does Outlook keep trying to recall an email?

Exchange Online retries for up to 24 hours before marking the recall failed. A status of pending within that window is expected behaviour.

Why is the Recall Message option missing from my Outlook?

The usual causes, in order: the account is a personal one rather than a work or school Microsoft 365 mailbox; the message was selected in the reading pane instead of being opened in its own window; classic Outlook is running in Online mode or has multiple Exchange accounts in the profile; or an admin has disabled the feature tenant-wide.

Does a recalled message disappear from compliance searches too?

No. Recall hard-deletes the message from the mailbox, but for mailboxes on Litigation Hold or In-Place Hold, the recalled message remains discoverable through eDiscovery. Recall is a courtesy to the recipient, not a way to erase a record.