Edit 8/22/2024: please see our new blog post on the subject for updates on the Message Recall feature.
At Microsoft Ignite several years ago we announced that we were working on a new cloud-based m...
Updated Oct 04, 2024
Version 14.0
Blog Post
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.)