Exchange Recall Report Confusion

John Rey Toston 60 Reputation points
2026-09-05T00:36:11.2833333+00:00

Dear Experts,

Good day. I would like to ask your opinion about this matter.

One of my exchange user initiated the "Message Recall", as per web-based report on her recall the results says "Failed" (see Figure 1).

Her recipients are within our organization.

Figure 1: Message Recall ReportUser's image

However, after manually confirming it to her recipients via telephone call it was successfully recalled.

Now my question is why web-based recall report says different? It may cause confusion on Sender's side.

Thanks in advance.

Exchange Online
Exchange Online

A cloud-based service included in Microsoft 365, delivering scalable messaging and collaboration features with simplified management and automatic updates.

0 comments No comments

Answer accepted by question author
Teddie Dang 1,185 Reputation points Independent Advisor
2026-09-05T01:27:40.6+00:00

Hi @John Rey Toston

Based on the information provided, if all recipients are Exchange Online mailboxes within the same Microsoft 365 tenant and the original message was successfully removed from recipient mailboxes, there appears to be a discrepancy between the reported recall status and the observed outcome.

The message shown in the recall report Messages to recipients outside your organization or on-premises can't be recalled would normally apply to unsupported recipient locations. Since the recipients are internal Exchange Online users, this reported result seems unexpected.

If this behavior can be reproduced, I recommend opening a support case with Microsoft Support, they can review the backend processing to determine why the recall report displays this status despite the recipients indicating that the message was successfully recalled.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.