Exchange Online to Add Cross-Tenant Message Recall with Admin-Controlled Trust

Microsoft is adding Cross-Tenant Message Recall to Exchange Online, allowing organizations to recall mistakenly sent emails across trusted Microsoft 365 tenants. The new capability extends one of Exchange Online’s most requested features while giving IT administrators full control over which external organizations can participate.

In 2023, Microsoft released the cloud-based Message Recall feature for Exchange Online. Previously, message recall only worked when both sender and recipient belonged to the same organization. If an employee accidentally sent an email to someone in a different Microsoft 365 tenant, the message could not be recalled. This limitation created frustration for businesses that regularly work across multiple tenants.

With this release, organizations will be able to allow message recalls from trusted external Microsoft 365 tenants, such as partners, subsidiaries, or affiliated companies. The receiving organization will maintain full control through an allow list. A recall request from another tenant will succeed only if the recipient’s tenant administrator has explicitly approved the sender’s tenant.

“A cross-tenant recall is only honored when the receiving tenant’s admin has explicitly allow-listed the sender’s tenant. This keeps the receiving organization in full control of which external tenants are permitted to recall messages from its users’ mailboxes. The feature is disabled by default; no cross-tenant recall occurs until an admin adds at least one tenant to the allow list,” the Exchange team explained.

How does Cross-Tenant Message Recall work?

The Cross-Tenant Message Recall feature will work through an administrator-controlled trust model. The recipient organization’s IT admin will first add a trusted Microsoft 365 tenant to an allow list. Once that trust relationship is established, users from the approved tenant will be able to initiate a message recall for emails sent to recipients in the other organization. Exchange Online will then handle the recall request similarly to how it does for messages exchanged within a single tenant.

If the sender’s organization has not been added to the recipient tenant’s allow list, the recall request will not be processed, and the sender will receive a notification indicating that cross-organization message recall is not permitted. When a recall is allowed, recipients will experience it just as they would a standard internal recall.

Microsoft notes that administrators will be able to manage this feature through Exchange Online PowerShell. It will allow IT admins to enable/disable cross-tenant recall and manage trusted tenant IDs.

Microsoft plans to roll out the Cross-Tenant Message Recall feature in mid-August 2026. The company expects to make this capability generally available for commercial and government customers by mid-September 2026.