Loading...

Introducing cross-tenant message recall in Exchange Online

Introducing cross-tenant message recall in Exchange Online

Exchange Online will support cross-tenant message recall, allowing trusted external Microsoft 365 tenants to recall messages sent to your users. This feature, disabled by default, can be enabled and managed by admins via PowerShell with an allow list of tenant IDs. Rollout starts mid-August 2026. 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 $trueSet-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, […]

The post Introducing cross-tenant message recall in Exchange Online appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Introducing cross-tenant message recall in Exchange Online

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Dynamics 365 Sales: Choose the data sources AI-powered Data Enrichment uses, including CRM notes

AI-powered Data Enrichment now lets admins choose which data sources the agent uses to enrich records. Outlook emails, Teams meetings, and the...

1 day ago

Microsoft Teams: Pro Management portal Analytics & Reports Design Refresh

We are refreshing the way we organize the Analytics & Reports area in the Pro Management portal to make it more user-friendly. Product Mic...

1 day ago

Copilot: Audio overviews on PDF Reteirement

Microsoft 365 Copilot mobile app’s Audio Overviews on PDFs, which create AI-generated podcast-style summaries for commercial users, will...

1 day ago

Public CDN is becoming optional during Brand Center setup

Brand Center setup will no longer require enabling Public CDN by default, allowing organizations to use branding governance without it. Public...

1 day ago

Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com

Microsoft is retiring the App Builder agent and vibe.powerapps.com by November 30, 2026, consolidating app creation into Copilot Cowork and Mi...

1 day ago

Outlook: Reply With a Template in Rules

New Outlook for Windows and Outlook on the web will let users create inbox rules that auto-reply with saved templates, automating routine resp...

1 day ago

Microsoft Purview Audit: AuditLogQuery API generally available and Search-UnifiedAuditLog retiring

The Microsoft Graph AuditLogQuery API will be generally available in October 2026, replacing the Search-UnifiedAuditLog PowerShell cmdlet, whi...

1 day ago

Dynamics 365 Sales – Information regarding the retirement of the Dynamics 365 Sales Insights standalone add-on

Starting November 1, 2026, Dynamics 365 Sales Insights as a standalone add-on will have reached end of support. Sales Insights is a legacy off...

1 day ago

Work IQ: Updating documents in Office

Work IQ enables agents to create and edit Microsoft Office documents using organizational context, helping users produce and update content mo...

1 day ago

Microsoft Purview: Information Protection – Apply default SharePoint library labels to data at rest

Enables auto‑labeling of existing SharePoint files to match the default sensitivity label configured on their document library. This helps org...

1 day ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.