Why Outlook's Recall This Message Doesn't Always Work
What actually happens when you try to unsend an email, and when it's worth trying it at all
By Shehryar Hassan, Microsoft 365 & Azure Consultant
Someone hits send on an email, realizes the mistake ten seconds later, and reaches for Recall This Message like it's an undo button. It isn't, and the way it fails catches people off guard almost every time.
How recall actually works
Recall only works inside Exchange Online, between two mailboxes on the same tenant. If you're emailing someone at another company, or even a personal Gmail or Outlook.com account, recall does nothing useful. The message already left your organization the moment you hit send, and there's no way to pull it back once it crosses that boundary.
Even inside your own tenant, recall isn't instant. Outlook quietly sends a second message asking the recipient's mailbox to delete the original. If the recipient has already opened the email, Outlook shows them a notice that you tried to recall it, which often draws more attention to the message than if you'd said nothing at all. If it's still sitting unread, the recall usually succeeds and the original disappears before they see it.
A few things break recall even within the same tenant. If the recipient reads mail through Outlook on the web instead of the desktop app, recall generally doesn't work, the message stays put no matter what you try. Mobile apps behave the same way. A rule that moves the message out of the inbox before the recall request arrives, like a rule filing it into a subfolder, can also stop the recall from finding it.
What to do instead
If you catch the mistake within a few seconds, Outlook's Undo Send delay (Settings > Mail > Compose and reply > Undo Send) is more reliable than recall, because it stops the message from ever leaving your outbox. Turning on a delay of 10 to 20 seconds costs you almost nothing and saves you from most of these situations before they happen.
If the email already went out and contains something sensitive, don't count on recall to fix it. Send a short, direct follow-up instead: "Ignore my last email, wrong attachment, correct one below." People respond better to that than to a recall notice, and it works no matter which app the recipient uses or which company they work for.
Recall is worth trying when it's an internal, same-tenant slip, sent seconds ago, to someone who's likely still at their desk reading unread mail in the desktop app. Outside of that narrow case, don't count on it, and have your follow-up message ready instead.
Get new posts by email
One note when there is something worth reading. No spam, unsubscribe anytime.
Related articles
SharePoint Version History, How It Actually Works and How to Restore an Old File
Every SharePoint library and OneDrive keeps version history automatically. Here's how to find an old version and restore it without calling IT.
What Viva Engage Actually Is and Whether Your Team Needs It
Viva Engage is Microsoft's rebrand of Yammer, built for open company-wide conversation rather than project work. Here's what it actually does and when it's worth switching on.
Windows 365 Cloud PC, What It Actually Is and When You'd Use One
Windows 365 gives each user a dedicated cloud desktop at a flat monthly price, no Azure portal required. Here's how it actually differs from Azure Virtual Desktop and when it's worth the seat cost.