MC1446796: Exchange Online Pauses Gov Rollout of Cross-Tenant Collaboration Migration Before EWS Deprecation

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
62
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Exchange AdminsMicrosoft 365 AdminsIT ManagersService OwnersSecurity Teams
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This update confirms a temporary pause on the government rollout of cross-tenant collaboration migration features tied to EWS deprecation. The core change remains active for worldwide tenants, so teams must still plan migration before EWS shutdown in 2027. Admin effort and urgency remain high due to required validation, PowerShell checks, and reconfiguration of sharing policies, though the pause reduces immediate time pressure for affected government environments.
75
🛡️ Admin Impact
40
👥 User Impact
55
⚡ Urgency
70
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Exchange Web Services is being deprecated. Admins need to migrate cross-tenant Free/Busy, MailTips, and Calendar Sharing to the Microsoft 365 Cross-Tenant Access Policy to keep these features working.
👥

END USERS

Users may lose shared calendar or Free/Busy visibility if migration is not completed.
🛡️

IT ADMINS

Review tenant configuration and follow the migration guide to move from EWS to the Cross-Tenant Access Policy before deprecation.
📅

ROLLOUT TIMELINE

Start:
August 2026

📢 Official Microsoft Message Center Announcement


(Updated) Migrate Free/Busy, MailTips, and Calendar Sharing before EWS deprecation
Message ID: MC1446796 (Updated)

Updated October 30, 2026: Gov rollout of this feature is paused at this time. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience.

[What and Why:]

Exchange Web Services (EWS) deprecation begins October 1, 2026. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS.

Cross-tenant Free/Busy, MailTips will be available by September 2026 and Calendar Sharing will be available by early November 2026 (previously end-October) via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration.

[Rollout Schedule:]

  • Worldwide: We will begin rolling out in August 2026 and expect to complete by September 15, 2026 for Free/Busy, Mailtips and November 6, 2026 (previously October 30) for Calendar Sharing.
  • GCC, GCC High, DoD: We will communicate via Message center when we are ready to proceed.

[Impact on your organization:]

Sharing Free/Busy, Calendars, and MailTips (e.g., out of office message) with another Microsoft 365 organization via Organization Relationship or Sharing Policy relies on Exchange Web Services (EWS), which is being deprecated. To preserve these cross-tenant collaboration scenarios, you will need to start migrating to Microsoft 365 Cross Tenant Access Policy.

Your tenant is affected if it uses any of the following Exchange Online configurations:

  • Organization Relationships — sharing Free/Busy or MailTips with other Microsoft 365 tenants 
  • Sharing Policies — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL

Run these commands in Exchange Online PowerShell to check if your tenant is affected: 

    • Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScopeIf results show (1) Enabled: True, and (2) either FreeBusyAccessEnabled: True or MailtipsAccessEnabled: True, and (3) the external organization is hosted in Microsoft 365, your tenant is affected and in scope to migrate. Else, no action is needed. 
    • Get-SharingPolicy | Format-List Name, Domains, Enabled, DefaultIf results show (1) Enabled: True, and (2) the Domains property contains at least one rule with a CalendarSharingFreeBusy access level (Simple, Detail, or Reviewer), and (3) the targeted external organization is hosted in Microsoft 365, and (4) the policy is assigned to one or more mailboxes, your tenant is affected and in scope to migrate. Else, no action is needed.
    • Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL – these also appear in this output.

What happens if I do nothing:

Starting October 1, 2026, Exchange Web Services (EWS) will be gradually disabled in line with previous communications linked to this message. As this rollout reaches your tenant, cross-tenant Free/Busy, MailTips, and Calendar Sharing that rely on EWS will be affected — recipients in partner organizations may no longer see Free/Busy, MailTips, or shared calendars from your tenant. 

If your organization is not ready to migrate, you can retain EWS access by following the guidance of the latest blog we published: ExchangeOnline EWS, Your Time is Almost Up (EWSEnabled set to True) while you prepare and execute the migration steps attached to this message. EWS access through this extension will remain available until the final EWS shutdown on April 1, 2027. 

[Action Required/Recommendations:]

  • Follow this Message center post for updates to the rollout schedule. To avoid impact, plan to migrate after the rollout reaches your tenant and before EWS deprecation.
  • Review the migration guide linked below for step-by-step instructions to understand your current configurations, set up new Microsoft 365 Cross Tenant Access Policies, validate the new configurations, and remove unused configurations. 
  • Check the blog post linked below for additional information and answers to frequently asked questions. 
  • Hybrid and on-premises scenarios are not in scope. This update applies to fully cloud-hosted (Exchange Online ↔ Exchange Online) cross-tenant and cross-cloud configurations only. For organizations running on-premises Exchange and Exchange Online in a Hybrid Deployment, migrate to Dedicated Hybrid App. For organizations hosted in Exchange Online sharing with another organization running Exchange on-premises, kindly monitor future Message Center posts for guidance on migration paths as they become available. 

[Additional information:]

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1446796] Archive
Tooltip: View earlier revisions of this post

Share This Update