Cloud-based Message Recall in Exchange Online
Published Feb 16 2023 08:34 AM 199K Views

At Microsoft Ignite several years ago we announced that we were working on a new cloud-based message recall feature for Exchange Online. Today we’re thrilled to announce that the new Exchange Online Message Recall feature has finally arrived! It’s starting to roll out now and should be available to all Exchange Online tenants worldwide by mid-March.

You may be familiar with the classic Outlook for Windows message recall feature that gives senders an opportunity to recall messages. The classic message recall feature enables senders to at least partially recall an email, but because it is client-based, it has a number of restrictions, and its average success rate is only about 50%. So, for most message recall requests, it’s been a best-effort or better-than-nothing action, rather than a full sigh-of-relief experience.

We took the opportunity to improve on many of the classic feature's shortcomings, and drastically increase its recall success rates. The new message recall feature is more than twice as effective (based on its use by Microsoft employees over the last several months -- and oh boy, do we use it a lot!). In addition to improved performance, we’ve also improved usability by creating an aggregate recall status report to replace the potentially hundreds or thousands of individual recall status email notifications (one for each message recipient).

What's new with Message Recall

  • On average, it’s more than twice as effective at successfully recalling messages than the classic feature.
  • Recipients no longer must have Outlook for Windows open for recalls taken from their mailboxes to be processed – the recall happens within the cloud mailbox, not on the client.  This way recipients can use any email client that syncs with an Exchange Online mailbox, and the client doesn’t have to be open for the recall to process.
  • It can now recall 'read' messages (tenant admins can disable this ability if they prefer).
  • It can also recall messages from any folder or sub-folder within the mailbox and not just the Inbox.
  • It offers a simple web-based status report, one per recalled message, to quickly see your overall recall results and determine the status for each recipient. No more multiple status notifications – just a single recall status email message that includes a single link to the recall status report.

How to recall a message using the Message Recall feature

While recipients are no longer required to use Outlook, at this time senders still need to use Outlook for Windows to trigger a message recall, using the same “Recall This Message” capability in the Outlook UI that the classic message recall feature uses. You can request to recall a message in Outlook for Windows via one of several entry points – below is just one of them (see Recall or replace an email message that you sent for more information).

Recall using File > Info > Resend or Recall

  1. From the Sent folder in Outlook for Windows open a message that you want to recall.
  2. In the open message go to the File menu and choose Info > Resend or Recall > Recall This Message.
  3. newrecall01.pngIn the dialog box that pops up select either the option to Delete the copies of this message or Delete and replace them with a new message, and then click OK.

And that’s it! Outlook will generate a “Recall” message (message class IPM.Outlook.Recall) that it sends to all the recipients. If the recipient has a mailbox hosted in Exchange Online, the Message Recall feature agent in the cloud will intercept the “Recall” message, attempt to recall (hard delete) the original message from the recipient’s mailbox in the cloud, and then it drops the recall message since it’s no longer needed. When the recipient’s email client (any email client) syncs with their cloud mailbox, the message should be gone.

The flow looks like this:

newrecall02.png

Track recall results with a single recall status report

After submitting a recall request, usually less than 30 seconds later, the sender will get an email notification from the service with the subject "Message Recall Report for message [original message subject]", like this one:  

newrecall03.png

Just click on the View Message Recall Report link to view the report in your browser. If you’re prompted, log in with your mailbox credentials to view the report:

newrecall04.png

Recall actions are usually quick, regardless how many recipients are involved. But if the recall request can’t be executed right away for some reason (e.g., the recipient’s mailbox is temporarily unavailable) we'll continue to retry for up to 24 hours before marking the recall as failed.

Status updates are usually pretty quick as well, but can sometimes take up to 5 minutes for a message with up to a few hundred recipients. For a large number of recipients (tens of thousands) the recall itself is still fast, but it can take up to 30+ minutes to retrieve the recall status for all recipients.

Feature comparison

Many long-time users of the classic Message Recall have commiserated over the feature’s inability to recall messages that have been flagged as read in the recipient’s mailbox, as well as the fact it recalled messages only from the Inbox and not from sub-folders. You will be pleased to know that the new Message Recall addresses both these scenarios: It can recall both read messages and messages in sub-folders! Support for these two new capabilities, plus the removal of the restriction for recipients having to use Outlook for Windows, contributes significantly to the increased recall success rate that the new Message Recall feature provides.

The table below compares some of the key characteristics of the new Message Recall compared to the classic Outlook for Windows feature:

Capability

Classic Message Recall

New Message Recall

Average recall success rate

40%

> 90%

Recalls are performed in the cloud

No

Yes

Recipients can use any email client to be eligible for recalls

No

Yes

Can recall read messages

No

Yes

Can recall messages from sub-folders (except Draft and Sent Items by design)

No

Yes

Single recall status report for all recipients

No

Yes

Frequently Asked Questions

Will the new Message Recall allow me to trigger recalls using email clients other than Outlook for Windows?
Not yet, but we’re working on an API that other email clients can adopt to submit recall requests for Exchange Online recipients.

Can I recall messages sent outside my organization?
No. For privacy and legal reasons the new Message Recall won’t recall messages sent to recipients outside your organization.

Can I recall messages from recipients inside my organization but who have mailboxes hosted on-premises?
No. The new Message Recall can only recall from mailboxes that are hosted in Exchange Online.

Can I disable the recalling of read messages for my tenant?
Yes. While having the ability to recall read messages has been an enormously popular request for years, a tenant admin can also disable this capability under Settings > Mail flow in the Exchange admin center, or via Remote PowerShell with Set-OrganizationConfig -RecallReadMessagesEnabled $false.

Can a tenant admin completely disable the new cloud-based Message Recall feature?

Yes, a tenant admin can use the following Remote PowerShell cmdlet to disable the new Message Recall feature for their entire tenant. Using this setting to disable the new cloud-based Message Recall will re-enable the legacy Message Recall for users of Outlook for Windows in your tenant.

Set-OrganizationConfig -MessageRecallEnabled $false

Will the recipient be informed that a message was recalled, especially for read messages?
No, not at this time. It’s under consideration for a future update.

Can I recall messages sent to mail enabled public folders?
No. Just like the classic Message Recall in Outlook for Windows, the Exchange Online Message Recall won’t recall messages sent to mail enabled public folders. This is by design.

Will recalls show up for eDiscovery?
For users/mailboxes that have a Litigation or Mailbox Hold, the recalled message will show up in eDiscovery.

Will recalls show up in the mailbox audit logs?
No, not at this time. We plan to address this in a future update.

Will forward messages get recalled?
Messages automatically forwarded via the SMTP forwarding by a recipient to another mailbox within the same organization will get recalled. However, messages forwarded manually by the recipient, or forwarded via Inbox rules (forward or redirect), will not.

Is there a time limit past which you can’t recall a message?
No, there is no time limit, just like the classic message recall feature. Providing tenant admins the ability to customize a time limit for their organization is under consideration for a future update.

Are the recall results stored in the sender’s mailbox?
No, the recall results are not stored in the sender’s mailbox, so it has no effect on the user’s mailbox quota or space.

Is there a limit on the number of recipients I can recall from with a single recall request?
Theoretically no – for a message you successfully sent, the recall action will be attempted and usually succeed for all eligible recipients regardless how many there are. However, the recall status report itself is currently limited to ~50k recipients. We plan to increase that significantly later this year.

The message recall dialog box in Outlook still has a checkbox to receive a recall notification for each recipient. Does that do anything with the new Message Recall?
No, it doesn’t. The Outlook dialog box hasn’t yet been updated to detect when the new Message Recall feature will be used instead of the classic Outlook message recall. We expect this to happen later this year.

The message recall dialog box says it’s only for unread messages. Is that still true with the new Message Recall?
Not necessarily. The tenant admin can control whether to allow recalling read messaging (enabled by default) or not. The Outlook dialog box hasn’t yet been updated to reflect the capabilities of the new Message Recall feature. We expect this to happen later this year.

Can I share my recall status report with others?
Yes, you can export the status report to a CSV file and share that with others. But sharing the link to the report itself won’t work. Logging in to the report requires the sender’s login credentials.

Does the recall work when the sender is a shared mailbox?

Yes, the new Message Recall supports triggering a recall from a shared mailbox and you can expect it will get recalled from most recipients.

Note there is a known issue with recall and shared mailboxes: Messages sent via shared mailboxes in Outlook Win32 are stored in the Sent Items of the authenticated user that generated the email. In this situation, recall initiated from the message resting within the Sent Item folder of the authenticated user will be successful (the same status report issue will exist). Messages sent via shared mailboxes opened from within OWA (Open another mailbox) are stored in the Sent Items of the shared mailbox, not the Sent Items of the authenticated user. In this scenario, if the shared mailbox is accessed within the same Outlook profile as the authenticated user either via automapping or via Open these additional mailboxes, when recall is attempted from the Sent Items of the shared mailbox the recall option will be greyed out. The workaround is to open the shared mailbox in its own Outlook profile.

Does the new recall work when sending as a delegate?
Similar to the shared mailbox scenario, the recall will work, but you won’t be able to login to view the report. We expect to provide that capability later this year.

Conclusion

The new Message Recall won’t stop you from accidentally sending “Oops” email messages, but with its high success rate and ease of tracking with the new recall status report, it should help bring you a lot more peace of mind for when you do. We hope you find it useful and look forward to hearing your feedback or suggestions for future improvements.

Kevin Shaughnessy

101 Comments
Copper Contributor

Thank you Kevin: 

Do you have a ETA on when this will be available within OWA?

 

Hi Steve,

We're currently working on the API for it and hope to have it ready later this year; then it'll be up to the OWA team to decide when to get it on their roadmap. 

What a PowerShell cmdlet to trigger a recall on behalf of a (technically challenged) user? Or will the API provide a delegate option?

With respect to the missing audit log events, will we at least be able to see a message trace entry for the incoming "recall" message, or is it all handled server-side, transparent to us?

Hi Vasil,

No PS cmdlet. We're looking at the delegate option for the API. Yes you can see in message trace detail the recall failure or success on the "RECALL:<original message subject>" message DROP event where "Result:[Success|Fail]" indicates if the recall itself succeeded or failed. Incidentally, this is the same indicator we use for the recall status report.

RecipientStatus         : {[Stage: OnPromotedEvent][Agent: Transport Message Recall Agent];Message recall process complete, dropping the recall email. Result:Success, NotificationRequested:False, Mbx:<redacted>}

Brass Contributor

Will this new recall work with cached-mode Outlook?  I have read articles that say the old one does not work in this configuration.

Copper Contributor

This is great improvement over the classic message recall. Well Done

@praveenkba Thank you so much! We hope you find it useful. 


@Rob Hupf reports from Microsoft colleagues using cached-mode say the new recall works great for them. Are there any specific scenarios with cached-mode you're concerned about? 


@Vasil Michev and @SteveRubin sorry didn't at mention you before so doing it now so you get notification that I replied to you. :)

Copper Contributor

Hi,

will this be coming to on-premises Exchange as well?

 

Brass Contributor

Thanks for this update. I was under the impression that this feature was already active.

 

3 questions:

 

- Can a sender recall any message from the past, read or unread by the recipient? So if I want to recall a message sent 1 year ago, that would be possible? If so, this can be a legal issue.

 

- Will this only work for messages sent since this feature is active? Or older messages too?

 

- You say that the success rate is over 90%. When will it not work? Only if the recipient mailbox is unavailable? Or other situations too?

 

Thanks.

Brass Contributor

Great approach and long awaited upgrade.

Feedback: Below option can be enabled with mutual trust or federation settings of some sort, would be highly useful.  

Can I recall messages sent outside my organization?
No. For privacy and legal reasons the new Message Recall won’t recall messages sent to recipients outside your organization.

Maybe a default with Admins having ability to turn if off. Reporting would be bit 
challenging though.

Set-OrganizationConfig -ExternalRecallReadMessagesEnabled $false.

Brass Contributor

would this new recall feature also allow recalls if the message went through a 3rd party connector? In our case, we are sending the mail to a vendor system (hosted in Azure/M365) through a dedicated connector, let it process whatever it needs to process and they then send it back to our tenant to then be delivered to internal or external recipients. Up to now, MS does not support those recalls due to the connector involvement.

 

Vendor support states:

= = =

Scenario

If you recall an email that has been routed to XXX to do YYY, you receive a Recall notice informing you that the email message failed to recall successfully (despite the email being unread in the recipient's Outlook mailbox).

Reason

Microsoft has confirmed that any emails routed via a connector are likely to fail to be recalled. This is because the SearchKey property, which is used to locate the email message, is modified during the routing process.

This is not unique to XXX, but it affects any route or service utilizing connectors - according to Microsoft, this is behaviour by design. As a result, recall email messages cannot be guaranteed when emails are routed to XXX.

Resolution

Unfortunately, there is no workaround, and you'll need to raise this issue with Microsoft. 

 

 

= = =

 

I still get why external emails can not be recalled at all, but the mails internal to the Org - even if they go through a connector - should be able to be recognized. (this was initially working when we moved to O365, but was changed somewhen which then broke the desired functionality for us.)

@TGecko no it won't be coming to Exchange on-prem. The architecture utilizes various components and microservices only available in the M365, and as I'm sure you've heard before our strategic focus of our development investments is the cloud. 

 

@hatsikidee three questions:

1) Can a sender send any message from the past. 
A: As noted in the above FAQ: Is there a time limit past which you can’t recall a message?
No, there is no time limit, just like the classic message recall feature. Providing tenant admins the ability to customize a time limit for their organization is under consideration for a future update.

 

2) Will this only work for messages sent since this feature is active? Or older messages too?
A: Older messages too. 

 

3) You say that the success rate is over 90%. When will it not work? Only if the recipient mailbox is unavailable? Or other situations too?

A: Messages sent to external recipients won't be recalled by design. That's the most common one. A few other corner case examples (not comprehensive):
* If the recipient mailbox isn't available (and remains unavailable for 24 hours for some reason)

* If the recipient has a Hard Delete rule that acts on the message,

* An ETR drops the original message before it reaches the mailbox

* The original message gets quarantined

* The original (or Recall) message is under moderation

 

@Satyajit321 

>>[recall externally sent messages] can be enabled with mutual trust or federation settings of some sort, would be highly useful. 

 

A: I think that's a great idea and would seem a reasonable way to address the ownership/privacy concerns about recalling externally that we're trying to honor with this release. Thanks!

 

@MatthiasMichl 

>>allow recalls if the message went through a 3rd party connector?

A: No, sorry. For the new Message Recall if it leaves the service at all we won't recall, even in a scenario like yours where it's just roundtripping out to Azure then back again. But I agree it's a scenario we should take a look at potentially supporting in the future. Thanks for the feedback. 

 

 

 

Copper Contributor

Old method "average success rate is only about 50%".

 

"The new message recall feature is more than twice as effective."

 

So, it is >100% effective?

Iron Contributor

Is it available in OWA?

 

@ScottO >>more than twice as effective. . .legacy recall 50% effective. . .so new recall > 100%?

According to the data I have, classic recall is ~40% effective on average, the new recall is > 90% effective. See the table mid-article which shows these numbers, derived from tens of millions of classic recalls in EXO and several months of Microsoft employees using the new recall (which actually averaged 97% success over two months). 

 

@Andrew_Woo >>is it available in OWA?
Triggering a recall from OWA is not yet possible. Recipients no longer have to use Outlook for Windows for recalls to work, but senders/recallers still do. As noted in the FAQ in the post above:
Will the new Message Recall allow me to trigger recalls using email clients other than Outlook for Windows?
Not yet, but we’re working on an API that other email clients can adopt to submit recall requests for Exchange Online recipients.

Steel Contributor

@KevinShaughnessy - Will this work in the Outlook Desktop that's part of Office 2021 LTSC or only in the Click 2 Run version? Typically, when things don't work in the LTSC version, we go to Outlook on the web to use the feature. Since this post says that "at this time senders still need to use Outlook for Windows to trigger a message recall," I'm worried we won't be able to take advantage of this feature at all.

 

If it won't work in the LTSC version of Outlook, can you please add that information to the support article you referenced? Is adding the feature to Outlook on the web on the backlog?

@m36five it doesn't require the Click 2 Run version, you can trigger a recall with any version of Outlook for Windows since 2003 so far as I know, including legacy versions of Outlook - any version of Outlook for Windows that supports the classic Recall This Message feature, which I believe is all of them since at least 2003 (unless the admin has disabled the feature through config settings like a Group Policy). However, both the sender and recipients need their mailboxes hosted in Exchange Online and within the same organization.

 

As noted in the FAQ we're working on an API that other email clients can use to trigger a recall. Once that's done, later this year, it'll be up to the Outlook on the Web team to decide if/when to integrate the functionality into their client. I can't speak for them, but they're very aware there is strong user interest in this functionality, so. . . .

Iron Contributor

Noted.

 

This means that OWA can just put it in their dream only.

 

Brass Contributor

When will this be enabled across tenants? Can admins proactively disable this before it rolls out? 

@KevinCallanan 

>>Enabled across tenants?

No.

>>Proactively disable?

Yes.

 

From the FAQ above:
Can I recall messages sent outside my organization?
No. For privacy and legal reasons the new Message Recall won’t recall messages sent to recipients outside your organization.

 

Can a tenant admin completely disable the new Message Recall feature?
Yes, a tenant admin can use the following Remote PowerShell cmdlet to disable the new Message Recall feature for their entire tenant: Set-OrganizationConfig -MessageRecallEnabled $false.

Copper Contributor

I guess its not available yet, I've made test email with same tenant and tried to recall but the original emails remains in recipients mailbox and they get new email saying sender trying to recall the email with original email subject.

@abhiisawant It's rolling out but it won't finish in all forests until mid-to-late March. 

* Mar 23, 2023 update: While rollout is progressing, due to the related service incident I mentioned in a later comment below the rollout WW won't complete until first week of April, although most tenants should see it enabled by end of March.

Copper Contributor

Hi Kevin, Outlook for Mac - Am i right to assume that will be part of the 'API for other clients' that comes later?  Just thinking that the community that benefits the most from this in our org are VIP's and they're all using Mac's/iPads/iPhones.  Just want to make sure I get the messaging right!

Thanks

Hi @MarkRussell, yes that's the notion that once we (Transport team) has the API available for any email client (3rd party as well) the Outlook for Mac and Outlook mobile teams can integrate it into their respective clients. I can't speak for those teams, but I do know that they're very aware of customer interest in this feature for those clients. :)

Brass Contributor

How long can a message be recalled after it has been received?

Copper Contributor

Its great to see an update on this feature, it looks like it will be much improved.

 

Will the recall report show which recipients had read the message?

This would be a useful feature in case something needs reporting to the Data Protection officer for example.

Copper Contributor

First of all, thank you for the good news!

 

"Will the recipient be informed that a message was recalled, especially for read messages?
No, not at this time. It’s under consideration for a future update."

 


As I understand it, it is not possible to inform the recipients of read AND unread messages that a message has been called back?

Does this only apply to read messages or also to unread messages?

This is an important criterion for us whether we switch the function on or off, for legal reasons this could lead to problems for us.

@Sektorsync >>How long can a message be recalled after it has been received?

As per the FAQ above: Is there a time limit past which you can’t recall a message?
No, there is no time limit, just like the classic message recall feature. Providing tenant admins the ability to customize a time limit for their organization is under consideration for a future update.

 

@Colin_Millins >>Will the recall report show which recipients had read the message?

Yes, it will show which recipients read the message for both recalled messages and messages that failed to recall. You can sort the Details column in the report's recipient table to more easily identify those that read the message.

 

@Sebjogro >>it is not possible to inform the recipients of read AND unread messages that a message has been called back?

That's correct, at this time the recipient does not receive any notification that the message was recalled; true for both read and unread messages. However, if for legal reasons you especially want that for read messages but it's not necessary for unread messages you can disable the recalling of read messages so that unread messages still get recalled but read messages don't. You can do this via the  checkbox in the Exchange Admin Center > Settings > Mail flow section, or using the Remote PowerShell cmdlet: Set-OrganizationConfig -RecallReadMessagesEnabled $false.

 

 

Copper Contributor

We are currently in an Hybrid exchange, will this recall function work if I tried to recall a message sent from my M365 account to an OnPrem 2016 account? 

 

@The_Exchange_Team 

@KevinShaughnessy 

@Jayride90 >>will this recall function work if I tried to recall a message sent from my M365 account to an OnPrem 2016 account?

As per the FAQ above: Can I recall messages from recipients inside my organization but who have mailboxes hosted on-premises?
No. The new Message Recall can only recall from mailboxes that are hosted in Exchange Online.

Copper Contributor

Will this feature work for recalling emails sent to DL's and Dynamic DL's? 

Use case is we have sent global coms with incorrect road map date (a past date) will this work? 

@Ashutosh-Microsoft >>Will this feature work for recalling emails sent to DL's and Dynamic DL's?

Yes.

Copper Contributor

 

My tenant is getting  the below after pressing on the Recall Report Link.

 

ManuelMesa_1-1678291763194.png

Any suggestions?.  Maybe someone encounter same issue already. 

Copper Contributor

We are also getting the same message and looking in MS Message center did not find any reported issues with it so assume it just started happening. 

 

@ManuelMesa @glujan72 there are a few common reasons folks hit this: 1) As noted in the error someone tries to log in to the report with an account other than the one they used when recalling - try an in private session, paste the URL into the address bar and when prompted make sure they're logging in with the same account that was used when they recalled the message; I've actually been bitten by this myself many times as I switch between accounts quite often. 2) If the recipient count for the recall is high (e.g. > 10k) you can also see this error - come back in a few minutes and refresh. If neither of those are relevant here, please open a support ticket for it. 

Copper Contributor

@ManuelMesa @KevinShaughnessy Thanks for the suggestion but still getting the error. I read that it's something MS recently rolled out and if you are going to have to open private sessions in order to view the report then it's not something most users will want to use. I have reported the issue to MS, may look into disabling this new recall feature and go back to the old one.

Steel Contributor

@KevinShaughnessy - I just want to thank you. If every Microsoft blog author was as responsive to comments/questions as you are, we'd all be so much happier as Microsoft costumers! :smile: So many people publish their blog and then seem to disappear. You've been awesome. Thank you so much.

@m36five Very kind of you, thank you so much! :smiling_face_with_smiling_eyes:

@glujan72 The suggestion to use in-private is for troubleshooting purposes to eliminate the possibility the user is logged in as someone other than the sender/recaller (the only one who's granted access to the report). We host the recall report in the OWA namespace specifically to make it as easy as possible for most users so they can use their service account login credentials and/or are already logged in with them. Thanks for opening a ticket with Support - as this is just rolling out any new issue they see about it will most likely get escalated to us on the product team soon. 

Copper Contributor

@KevinShaughnessy 

Thanks for your quick and clear answer!
I hope that it also comes with rule-read messages, we would like to use the function, but only with notification, which we can also enforce from admin point of view

Copper Contributor

@KevinShaughnessy  I tried as incognito even cleaning cache of browser still facing the same issue and whole tenant users are having the same issue is not only 1 user issue

 

ManuelMesa_0-1678352820043.png

 

we are thinking about doing the below

Can a tenant admin completely disable the new cloud-based Message Recall feature?

Yes, a tenant admin can use the following Remote PowerShell cmdlet to disable the new Message Recall feature for their entire tenant. Using this setting to disable the new cloud-based Message Recall will re-enable the legacy Message Recall for users of Outlook for Windows in your tenant.

Set-OrganizationConfig -MessageRecallEnabled $false

 

 

unless you can advise something else please? 

 

@Sebjogro >>I hope that it also comes with rule-read messages, we would like to use the function, but only with notification, which we can also enforce from admin point of view

 

Can you elaborate on that? What do you mean by rule-read messages, notification, and enforcem from admin point of view?

 

@ManuelMesa It turns out there's a bug in the feature that we discovered last night. We've disabled the feature entirely for the dozen or so forests for which it was enabled, halted further enablement, and hope to get the fix deployed and the feature re-enabled in the next week, maybe two. So sorry for the troubles and inconvenience. 

PS - by "disabled the feature entirely" I just mean the cloud-based Recall. It will fall back to the classic Outlook-based message recall while the cloud-based recall is disabled.

Copper Contributor

We're getting some strange issues with our Tenant.

 

Some users get the newer "message Recall" email when recalling a message, but others do not.  The ones that get the message recall message get an error when they click on "view message recall status" 

 

Also, is this enabled by default or does it have to be enabled per Tenant?MessageRecall.PNGMessageRecall1.PNG

@Beeemarman >>Some users get the newer "message Recall" email when recalling a message, but others do not.  The ones that get the message recall message get an error when they click on "view message recall status"

 

We discovered a bug accessing the recall status report and have temporarily disabled the feature while fixing it - we expect to re-enable it again starting on March 22nd. This is discussed in Service Health Dashboard item EX526084. 

* March 22 update - the fix has rolled out and the feature has been re-enabled for the sub-set of EXO forests that were enabled at the time of the regression. We now expect worldwide rollout to complete by April 7th. 

 

>>Also, is this enabled by default or does it have to be enabled per Tenant?

 

It's enabled by default (although right now we've temporarily disabled it). As noted in the FAQ above, there are two settings you can toggle: 1) one to disable/enable the entire feature; 2) disable/enable the recalling of read messages. The switch to toggle the recalling of read messages is available in the EAC as shown in your screen shot. The switch to toggle the entire feature off/on is via remote powershell: Set-OrganizationConfig -MessageRecallEnabled $false. 


Copper Contributor

@KevinShaughnessy

  1. If any mails moved to Online Archive mailbox, we are unable to re-all the messages. We get "The message wasn't found in the recipient’s mailbox". Will I be able to re-call if any emails moved "Online Archive Mailbox" in the future?
  2. We can only see subject and "To" address of the recalled message in “Message Recall Report” and it would be nice to see the date and time of the recalled email to the addressee.

           Raja_Chinnadurai_0-1679415022135.png

  1. Most users do not receive a "message recall" email when the sender attempts to recall.

@Raja_Chinnadurai 

>>Will I be able to re-call if any emails moved "Online Archive Mailbox" in the future?

A: By design for Privacy/legal reasons, probably not. However, if enough customers would like this option we can revisit this topic with our Privacy and Legal teams. 

>>it would be nice to see the date and time of the recalled email to the addressee

Agreed - that was our original intention but we ran into a surprisingly formidable technical hurdle to do it, so we tabled it for now. We'll revisit it in the future. 

>>Most users do not receive a "message recall" email when the sender attempts to recall.

The feature isn't fully rolled out yet - check first week of April and see if the behavior is still happening and if so please raise a support ticket for it. 

Thanks!

Copper Contributor

Will the recipient be informed that a message was recalled, especially for read messages?
No, not at this time. It’s under consideration for a future update.

 

Please DO NOT inform the recipient, not least re instant recalls (e..g, within 30 minutes), otherwise it will defeat the purpose.  Thanks. 

Copper Contributor

Hi @KevinShaughnessy , thanks for this article, it's substantially more helpful than the generic Microsoft Support pages.

I work at the IT support department at my company (not directly dealing with Outlook/Exchange issues though) and received a user prompt about this new recall method.

I've tried it myself and the results are a bit confusing: I was able to recall a mail, my colleague first saw it in his inbox and then after I recalled, it disappeared. However, the Recall Report indicates that this was unsuccessful. (Translation: Messages sent to external or on-premise recipients cannot be recalled)

Both of us have an Exchange profile of course.

 

PearlDiver_0-1680595516757.png


Any idea why this is happening..?

Copper Contributor

@KevinShaughnessy 

 

Can you elaborate on that? What do you mean by rule-read messages, notification, and enforcem from admin point of view?

 

Exactly, from admin point of view we need more control.

E.g.
- Settings until how many days an email can be called back
- Force the recipients to be informed about a message recall (server side or Outlook policy)

 

Unfortunately, due to the missing features, the function is not allowed for us. Even if many have been waiting for this update.

I have tried the new Message Recall in our test environment.

It is really very well implemented and works wonderfully, thank you!

 

Thank you also for your detailed communication, it's rare to have that with a new blog post!

 

Co-Authors
Version history
Last update:
‎Jan 05 2024 11:39 AM
Updated by: