Sending an email to the wrong person has always been one of those mistakes where the consequences can arrive faster than the sender can react.
Microsoft is now extending Outlook's cloud-based message recall capability so that, in certain circumstances, an email sent to another Microsoft 365 organisation can be recalled.
Until now, Microsoft 365 message recall has generally been restricted to people inside the same organisation.
The new cross-tenant message recall capability changes that — but there is a significant catch.
You cannot simply recall any email you've sent outside your company.
The recipient must be using Exchange Online in another Microsoft 365 organisation, and that organisation's administrator must have explicitly allowed your Microsoft 365 tenant to perform cross-tenant recalls.
Microsoft is beginning the worldwide rollout in mid-August 2026, with completion currently expected by mid-September.
How did Outlook email recall work before?
Outlook has offered message recall for years, but the feature has changed considerably.
The older Outlook recall mechanism was heavily dependent on the recipient's Outlook client and had a reputation for being unreliable.
Microsoft subsequently moved message recall into Exchange Online itself.
With the modern cloud-based system, the recall is processed in the recipient's Microsoft 365 mailbox rather than relying on Outlook running on their computer.
That has made recall considerably more effective and introduced capabilities that weren't available with the older system.
For example, cloud-based message recall can:
- Recall messages directly from Exchange Online mailboxes
- Work regardless of which supported email client the recipient uses
- Recall messages that have already been read, unless the administrator disables that capability
- Recall messages that have been moved into many mailbox folders
- Provide the sender with a central message recall report
But there was still one major boundary: the sender and recipient normally had to belong to the same Microsoft 365 tenant.
The new cross-tenant capability is designed to remove that restriction for organisations that explicitly trust each other.
What is cross-tenant message recall?
In Microsoft 365 terminology, a tenant is effectively an organisation's own Microsoft 365 environment.
If your company uses Microsoft 365 and a customer, supplier or sister company also uses Microsoft 365, you are normally operating in two separate tenants.
Until this change, sending an email from one tenant to the other meant the message had crossed the boundary where Microsoft 365 recall normally worked.
Cross-tenant message recall allows the receiving organisation to create a list of external Microsoft 365 tenants that it trusts to perform message recalls.
Once that relationship has been configured, a sender in an approved organisation can attempt to recall a message from the recipient's Exchange Online mailbox in much the same way as an internal recall.
This could be particularly useful between:
- Parent companies and subsidiaries
- Sister companies within the same group
- Businesses that collaborate very closely
- Organisations with separate Microsoft 365 tenants following an acquisition
- Trusted partners that exchange sensitive information regularly
However, the decision does not sit with the sender.
The organisation receiving the email decides which external Microsoft 365 tenants are allowed to recall messages from its users' mailboxes.
Can I now recall any external email in Outlook?
No.
This is the most important limitation to understand.
Cross-tenant recall does not turn Outlook's Recall button into a universal way of withdrawing an email after it has been sent to the internet.
For the new capability to work:
- The recipient must have an Exchange Online mailbox in another Microsoft 365 tenant
- The receiving organisation must have enabled cross-tenant message recall
- The receiving organisation must have added the sender's Microsoft 365 tenant to its approved list
- The recall must still meet Microsoft's normal Exchange Online message recall requirements
If your organisation has not been approved by the recipient's Microsoft 365 administrator, the cross-tenant recall will not be honoured.
What about Gmail or other external email services?
An email sent to Gmail, Yahoo, a personal Outlook.com account or another email platform outside the supported Exchange Online environment cannot be pulled back using this feature.
Once an ordinary internet email has left the Microsoft 365 recall boundary, the sender cannot force the recipient's external mail provider to delete it.
So if someone asks:
“Can I recall an email I accidentally sent to someone outside the company?”
the answer remains:
Only in specific circumstances where the recipient belongs to another participating Microsoft 365 organisation.
Can Outlook recall an email after the recipient has read it?
Potentially, yes.
This is another area where modern Exchange Online message recall is very different from the old Outlook feature many users remember.
Microsoft's cloud-based recall system can recall messages that have already been marked as read.
However, administrators can choose to disable the recall of read messages within their Microsoft 365 environment.
That means a successful recall should never be treated as a guarantee that the recipient didn't already see the information.
Someone may have:
- Read the email before the recall was processed
- Seen a notification preview
- Copied information elsewhere
- Downloaded an attachment
- Forwarded the information
Message recall can remove the original email from a supported Exchange Online mailbox, but it cannot undo everything the recipient may already have done with that information.
Businesses should therefore avoid treating recall as a substitute for good email handling, data protection procedures or user training.
What happens when you recall an email?
From the sender's perspective, the process remains similar to the existing Outlook message recall experience.
After submitting a recall request, Microsoft generates a Message Recall Report so the sender can check what happened.
The report can show whether recall for individual recipients:
- Succeeded
- Is still pending
- Failed
For cross-tenant recall, Microsoft says that if the sender's organisation has not been approved by the receiving organisation, the sender will receive a notification explaining that the message cannot be recalled across organisations.
The recipient experience is also controlled partly by the receiving Microsoft 365 organisation.
Administrators can choose whether users receive notifications when messages are recalled. If recall notifications are enabled for that organisation, those settings also apply to cross-tenant recalls.
For most users, the important lesson is simple: don't assume pressing Recall means the problem has disappeared.
Check the recall report and confirm whether Microsoft was actually able to remove the message.
Who Is Keeping Track of Your Microsoft 365 Settings?
Microsoft 365 changes constantly. Features such as cross-tenant message recall may require administrator configuration before your users can benefit from them — and default settings aren't always the right settings for your business.
New features, security controls and retirements appear throughout the year. Someone needs to understand which changes matter to your business and what needs configuring.
Why Microsoft 365 management matters →Why would another organisation allow your company to recall emails?
At first glance, giving another company permission to delete messages from your employees' mailboxes might sound like something an administrator would never want to enable.
That is precisely why Microsoft has made the feature opt-in and based it around specific trusted tenants rather than enabling it for the whole internet.
There are situations where the capability could make practical sense.
Imagine two companies within the same group that operate separate Microsoft 365 environments.
Employees may exchange hundreds of messages every day, often containing commercially sensitive information, financial documents or internal discussions.
If someone accidentally sends confidential information to the wrong employee in the sister company, cross-tenant recall provides another opportunity to correct the mistake.
The same could apply between a parent company and subsidiary or between organisations with an exceptionally close working relationship.
But enabling the capability should still be a deliberate administrative decision.
Businesses should understand:
- Which external organisations are being trusted
- Why they need cross-tenant recall
- Who owns and administers the other Microsoft 365 tenant
- Whether that relationship should remain trusted over time
This isn't a feature we would recommend enabling indiscriminately for every organisation you exchange email with.
Does an administrator need to configure cross-tenant recall?
Yes.
Microsoft is not automatically creating recall relationships between Microsoft 365 organisations.
The cross-tenant feature is disabled by default.
An Exchange Online administrator in the receiving organisation must first enable cross-tenant recall and then specify the Microsoft 365 tenant IDs that are trusted to perform recalls.
Microsoft currently provides this configuration through Exchange Online PowerShell.
That distinction matters because users may begin seeing articles or Microsoft announcements saying Outlook can recall external messages and understandably assume the capability will simply appear.
In reality, whether it works between two companies depends on the Microsoft 365 configuration at the recipient's end.
For most independent customers and suppliers, there may be no cross-tenant trust relationship at all.
This is therefore likely to be most useful where two organisations have an established relationship and their IT teams have deliberately configured the feature.
Another example of Exchange Online becoming more cloud-controlled
This change also reflects a broader direction within Microsoft 365.
Modern Outlook and Exchange functionality is increasingly being handled by Microsoft's cloud services rather than depending entirely on what happens inside the desktop Outlook application.
Cloud-based message recall is a good example.
The user still initiates the recall through Outlook, but Exchange Online performs the important work in the recipient's mailbox.
That distinction is becoming increasingly important for businesses because Microsoft is also retiring older Exchange technologies and moving organisations towards newer cloud-based services and APIs.
For example, Microsoft is currently preparing for the retirement of Exchange Web Services in Exchange Online. We explain that separate change in our guide: Microsoft Is Switching Off Exchange Web Services – What Businesses Need to Know.
Microsoft is also continuing to change the limits and capabilities included with its business email services. You can follow those developments in our guide to the Microsoft 365 Business mailbox limit increasing to 100GB.
What should businesses do about cross-tenant email recall?
For most SMEs, there is no urgent requirement to switch anything on simply because Microsoft has introduced the feature.
Instead, businesses should consider whether they actually have relationships where cross-tenant recall would provide a useful benefit.
We would suggest asking:
- Do we operate more than one Microsoft 365 tenant?
- Do we have sister companies or subsidiaries with separate Microsoft 365 environments?
- Do employees regularly exchange sensitive email with a particular trusted organisation?
- Would both organisations genuinely benefit from allowing message recall?
- Who would be responsible for maintaining the tenant allow list?
If the answer is no, there may be little reason to configure it.
If the answer is yes, the relevant IT administrators should review the Microsoft configuration together and decide whether creating the trust relationship is appropriate.
It is also worth remembering that recall is a safety net, not a data-loss-prevention strategy.
Users should still check recipients before sending sensitive information, use appropriate sharing methods for confidential files and report misdirected information promptly where necessary.
Businesses that don't currently have anyone actively reviewing Microsoft 365 changes may also want to look at our guide on why Microsoft 365 management matters more than most businesses realise.
So, can you recall an email sent outside your organisation?
The answer is now sometimes.
If the recipient is in another Microsoft 365 organisation, both organisations use the supported Exchange Online environment and the recipient's administrator has explicitly trusted your Microsoft 365 tenant, cross-tenant message recall can allow the email to be withdrawn.
If you're emailing an ordinary external recipient on Gmail, Outlook.com or another unsupported mail platform, this feature does not allow you to retrieve the message.
And even where recall succeeds, it should never be assumed that nobody has already seen or acted on the information.
The new capability is nevertheless a useful improvement for groups of companies and trusted organisations that regularly work across separate Microsoft 365 environments.
For IT teams, the bigger lesson is that Microsoft 365 continues to change behind the familiar Outlook interface. New capabilities often depend on tenant-level configuration, security decisions and ongoing administration.
If you're unsure how your Microsoft 365 environment is currently configured, KES can review the tenant, security settings and wider Microsoft 365 configuration through our Microsoft 365 Security Assessment.
