Quick Answer
No — recalling a message in Outlook does not delete it from the recipient’s mailbox. It only attempts to remove or replace it if both sender and recipient use Exchange accounts in the same organization, the message hasn’t been read yet, and the recipient hasn’t opened it in Outlook desktop (or Outlook for Mac). To try it: open Sent Items > right-click the message > Recall This Message… > choose Delete unread copies or Delete unread copies and replace with a new message.Step-by-Step Walkthrough
- Open Sent Items. In Outlook desktop (365, 2021, or 2019), go to your Sent Items folder — not Drafts, not a search result. The message must be there, unmodified, and sent within the last 120 minutes (Outlook 365/2021) or 60 minutes (Outlook 2016).
- Right-click the message. Don’t double-click. Don’t select and press Enter. Right-click directly on the message line — not the preview pane. You’ll see Recall This Message… in the context menu.
- Click Recall This Message… A dialog opens. Two options appear: Delete unread copies and Delete unread copies and replace with a new message. Select one. Do not check ‘Tell me if recall succeeds or fails’ unless you want noisy notifications — it won’t change outcome.
- Confirm and wait. Click OK. Outlook sends a recall request to the Exchange server. You’ll see a small status bar at the bottom: “Recall request sent.” That’s it. No success guarantee. No automatic follow-up.
- Check results manually. Go to your Deleted Items folder and look for a system-generated message titled “Recall report for [Subject]”. Open it. It lists each recipient and says either Successful, Failed, or Pending. ‘Pending’ means the message is still unread and unopened — but recall hasn’t completed yet.
Common Pitfalls
- You try to recall after 120 minutes — Outlook blocks the option entirely in version 365. In Outlook 2016, the button disappears after 60 minutes. No warning. Just gone.
- You’re sending to Gmail, Yahoo, or another external domain. Recall is disabled in the UI — the option simply doesn’t appear. Even if you force it via VBA or PowerShell, it fails silently.
- The recipient opened the message in Outlook Web App (OWA) or Outlook for iOS/Android. Recall only works reliably in Outlook desktop (Windows or Mac) — and only if the user hasn’t clicked into the message body.
- You sent from a shared mailbox or delegate account. If your permissions are set to “Send As” (not “Send on Behalf”), recall fails silently. Only the mailbox owner can initiate a recall — even if you sent it.
Pro Tips
The beauty of this approach is how quietly it operates — no alerts to recipients, no log entries in their mailbox audit trail. But here’s what most people don’t realize: you can recall multiple messages at once. Select 2–7 messages in Sent Items (Ctrl+click), right-click, and choose Recall This Message…. Outlook processes each individually — and generates one combined recall report.
Second: if you choose “replace with a new message”, Outlook reuses the original subject line and To/Cc fields — but ignores Bcc. Any Bcc recipients get neither the original nor the replacement. They keep the first version forever.
Third: recall works with Teams channel emails — but only if the channel email address resolves to an internal Exchange mailbox (e.g., marketing@company.com), not a generic teams@company.com alias. Test this with a low-stakes message first.
Troubleshooting
If the Recall This Message… option is grayed out or missing:
- You’re using Outlook Web App (OWA). Recall is not available in OWA — full stop. You must use Outlook desktop (Windows or Mac). Microsoft has never added it, despite repeated feature requests since 2018.
- Your admin disabled recall. In Exchange Online, admins can block recall globally via PowerShell:
Set-OrganizationConfig -AllowMessageRecall $false. Check with IT if the option vanishes overnight. - You’re on Outlook 2013 or earlier. Recall exists, but only works with Exchange 2010 or newer. If your org runs Exchange 2007, recall always fails — even if the UI lets you click it.
- The message was sent to a distribution group where some members are external. Outlook treats the whole recall as failed — even if 9 of 10 recipients are internal. No partial success.
One surprising fact: recall works with archived messages — but only if they’re still in Sent Items. If you moved the message to an archive PST or OneDrive folder, recall is impossible. The message must reside in the live Exchange Sent Items folder.
| Your Situation | Best Method | Why |
|---|---|---|
| Sent to internal team, unread, 45 minutes ago | Recall + Replace | Highest success rate; preserves thread context |
| Sent to client (Gmail), 2 mins ago | Send apology + correction | Recall unavailable — external domains ignore request |
| Sent from shared mailbox, 'Send As' permissions | Ask mailbox owner to recall | Only mailbox owner can trigger recall — delegate rights don’t extend here |
| Message opened in OWA, unread in desktop | No reliable method | OWA users receive recall requests but don’t process them — message stays |
| Attached wrong file, 90 mins ago | Use Ctrl+R to reply-all with correction | Recall blocked after 60 min in 2016, 120 min in 365 — reply is faster and traceable |
| Sent to Teams channel email (internal) | Recall — if resolved to Exchange mailbox | Works only if channel email maps to real mailbox, not alias |
| Recipient uses Outlook for iOS | Assume recall failed | iOS app doesn’t process recall requests — message remains |
