Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 13:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Migrate Free/Busy, MailTips, and Calendar Sharing before EWS deprecation

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Action date

18d ago Act by , as Microsoft's metadata states
Microsoft's start date
3 Aug 2026
Last changed by Microsoft
5 Oct 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

Updated October 5, 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 mid-October 2026 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 October 15, 2026 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

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

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.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
  • 2 linked pages have 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 19 Oct 13:25 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current