Message Recall

Message recall in Outlook is the feature for retracting an already-sent email — useful when you realised you sent to the wrong person, attached the wrong file, or sent an embarrassing typo. The modern cloud-based recall introduced in 2023 is significantly more reliable than the legacy version: it works inside Microsoft 365 tenants regardless of whether the recipient has opened the message, and provides status reporting on success per recipient. Accessed in Outlook by opening the sent message → File → Info → Message Recall. The legacy recall (still operative for some scenarios) only worked if the recipient hadn't opened the message and was in the same Exchange organisation. For cross-tenant or external recipients, recall doesn't work — once it's left your tenant, it's outside Microsoft's reach.

Worked example

An employee sends a message containing an unredacted salary spreadsheet to the wrong internal distribution list, realises within seconds, and opens the sent item to trigger a recall. Because both sender and every recipient are inside the same Microsoft 365 tenant, the modern cloud-based recall succeeds even for the handful of recipients who had already opened the message on their phones — a scenario the legacy recall would have failed on outright. The sender gets a per-recipient status report confirming which mailboxes the recall actually reached.

Common pitfalls

Assuming recall works once a message has left the organisation entirely — to a client's external email domain, or to a personal Gmail account — is the most damaging misunderstanding, since recall has no reach at all outside the sending tenant; the moment a message crosses that boundary, there's no technical mechanism to retract it, only asking the recipient directly. Confusing the modern cloud-based recall with the older, much less reliable legacy version leads some users to assume recall "never really works" based on years-old experience, when the current version is meaningfully more capable for same-tenant recipients. And treating recall as a substitute for double-checking the recipient list and attachment before hitting send is backwards — recall is a safety net for genuine mistakes, not a reason to be less careful, since even a successful recall can't guarantee a recipient hasn't already read or forwarded the content.