Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 09:15 UTC Customize Public modeDiscuss ChangeIntel on Discord

Introducing cross-tenant message recall in Exchange Online

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
561330

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, with source markup removed
What and Why: We're introducing Cross-tenant Message Recall in Exchange Online, enabling organizations to allow trusted external Microsoft 365 tenants to recall messages sent to their users. Previously, Message Recall only worked within the same tenant. This enhancement improves organizational collaboration and control, allowing administrators to extend recall capabilities across partner or affiliated tenants while maintaining explicit governance through an allow list. This message is associated with Roadmap ID 561330. Rollout Schedule: General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins mid-August 2026; expected to complete by early September 2026 Impact on Your Organization: Who is affected: Exchange Online administrators Organizations collaborating with external Microsoft 365 tenants Platforms/Services: Exchange Online Outlook (web, desktop, mobile) What will happen: The feature is disabled by default. Admins can enable cross-tenant recall using Exchange Online PowerShell. Admins can control an allow-list of external tenant IDs. Once enabled:External senders from allow-listed tenants can recall messages sent to your users. Recipients experience recall the same as intra-tenant recall. If recipient recall notifications are enabled, they apply to cross-tenant recalls. Recall attempts from tenants not on the allow-list will fail. Each tenant independently controls which external organizations are allowed. Action Required/Recommendations: No action is required to keep the default behavior (disabled). If you plan to enable this feature: Review with messaging and security teams. Enable or disable the feature using Exchange Online PowerShell: Set-CrossTenantRecallConfiguration -CrossTenantRecallEnabled $true Set-CrossTenantRecallConfiguration -CrossTenantRecallEnabled $false Manage the allowed tenant list (add or remove): Set-CrossTenantRecallConfiguration -AllowedSenderTenantIds @{Add="tenantId1","tenantId2"} Set-CrossTenantRecallConfiguration -AllowedSenderTenantIds @{Remove="tenantId1","tenantId2"} Update internal documentation and notify helpdesk. Learn more: Cross-Tenant Message Recall in Exchange Online Compliance considerations: Area Explanation New cross-tenant communication capability Enables external tenants to recall messages into your organization when explicitly allow-listed, introducing a new controlled interaction between tenants. Processing of existing customer email data The recall feature operates on existing email messages and may trigger deletion actions in recipient mailboxes, but does not fundamentally change how data is stored. Admin control over feature behavior Admins can enable or disable the feature using PowerShell and explicitly allow or remove trusted tenant IDs. End-user experience changes If enabled, users may see message recall activity originating from external tenants, similar to intra-tenant recall behavior.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 09:15 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current