Favorite your Message Center and Roadmap items. Access them anytime via your Profile. Export and share with your team or your LLM.

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

Message ID
MC1446796
View in Message Center
Service
Exchange Online
Category
Plan for Change
Tags
Major Change User impactAdmin impactRetirement
Act By
October 1, 2026
Rollout
August 2026September 2026October 2026

Summary

Exchange Web Services (EWS) deprecation starts October 1, 2026, affecting cross-tenant Free/Busy, MailTips, and Calendar Sharing. Migration to Microsoft 365 Cross-Tenant Access Policy begins September 2026, with rollout completing by October 2026. Organizations must migrate to avoid service disruption. Hybrid/on-premises scenarios are excluded.

Details

Updated August 25, 2026: We have updated the content and timeline. Thank you for your patience. 

[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, and Calendar Sharing via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration, will be available starting September 2026.

[Rollout Schedule:]

  • Worldwide: We will begin rolling out in August 2026 and expect to complete by September 15, 2026.
  • GCC: We will begin rolling out early September 2026 (previously mid-August) and expect to complete by September 30, 2026 (previously mid-September).
  • GCC High: We will begin rolling out early September 2026 and expect to complete by September 30, 2026.
  • DoD: We will begin rolling out early September 2026 and expect to complete by October 30, 2026 (previously end of September).

[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, MailTipsAccessScope
    • If 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, Default
    • If 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:]

Change History

Show
August 25, 2026 at 10:30 PM Updated
Summary
Previous
Exchange Web Services (EWS) deprecation starts October 1, 2026, affecting cross-tenant Free/Busy, MailTips, and Calendar Sharing. Migration to Microsoft 365 Cross-Tenant Access Policy begins September 2026. Check your tenant’s configurations and migrate before EWS shutdown on April 1, 2027, to avoid service disruption.
New
Exchange Web Services (EWS) deprecation starts October 1, 2026, affecting cross-tenant Free/Busy, MailTips, and Calendar Sharing. Migration to Microsoft 365 Cross-Tenant Access Policy begins September 2026, with rollout completing by October 2026. Organizations must migrate to avoid service disruption. Hybrid/on-premises scenarios are excluded.
Last Updated Date
Previous
2026-08-11T16:40:11.430Z
New
2026-08-25T20:19:17.493Z
Body Content
Previous
<p>Updated August 7, 2026: We have updated the content. Thank you for your patience.&nbsp;</p><p>[What and Why:]</p><p>Exchange Web Services (EWS) deprecation begins <b>October 1, 2026</b>. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS.</p><p>Cross-tenant Free/Busy, MailTips, and Calendar Sharing via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration, will be available starting <b>September 2026</b>.</p><p>[Rollout Schedule:]</p><ul><li>Worldwide: We will begin rolling out in August 2026 and expect to complete by September 1, 2026.</li><li>GCC: We will begin rolling out mid-August 2026 and expect to complete by mid-September 2026.</li><li>GCC High: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li><li>DoD: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li></ul><p>[Impact on your organization:]</p><p>Sharing Free/Busy, Calendars, and MailTips (e.g., out of office message) with another Microsoft 365 organization via Organization Relationship, Availability Address Space, 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.</p><p>Your tenant is affected if it uses any of the following Exchange Online configurations:</p><ul><li><b>Organization Relationships</b> — sharing Free/Busy or MailTips with other Microsoft 365 tenants&nbsp;</li><li><span><b>Availability Address Spaces</b> — sharing Free/Busy with other Microsoft 365 tenants (AccessMethod: OrgWideFBToken)&nbsp;</span></li><li><span><span><b>Sharing Policies</b> — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL</span></span></li></ul><p>Run these commands in Exchange Online PowerShell to check if your tenant is affected:&nbsp;</p><ul><li><code>Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScope</code><span></span><ul><li><span>If 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.</span>&nbsp;</li></ul></li><li><code>Get-AvailabilityAddressSpace | Format-List ForestName, AccessMethod</code><span></span><span>&nbsp;</span><ul><li><span>If results show (1) AccessMethod: OrgWideFBToken, and (2) the external organization is hosted in Microsoft 365, your tenant is affected and in scope to migrate. Else, no action is needed.</span>&nbsp;</li></ul></li><li><code>Get-SharingPolicy | Format-List Name, Domains, Enabled, Default</code><span></span><ul><li> If 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.</li><li>Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL - these also appear in this output.</li></ul></li></ul><p><i><u>What happens if I do nothing:</u></i></p><p>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.&nbsp;</p><p>If your organization <b>is not ready to migrate</b>, you can retain EWS access by following the guidance of the latest blog we published: <a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">ExchangeOnline EWS, Your Time is Almost Up</a> (<b><i>EWSEnabled</i></b><i>&nbsp;set to&nbsp;<b>True</b></i>) 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.&nbsp;</p><p>[Action Required/Recommendations:]</p><ul><li><b>Follow the Roadmap post</b> for updates to the rollout schedule. To avoid impact, <b>plan to migrate after the rollout reaches your tenant and before EWS deprecation</b>.</li><li><b>Review the migration guide linked below</b> 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.&nbsp;</li><li><b>Hybrid and on-premises scenarios are not in scope</b>. 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 <a href="https://learn.microsoft.com/exchange/hybrid-deployment/deploy-dedicated-hybrid-app" target="_blank">Dedicated Hybrid App</a>. 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.&nbsp;</li></ul><p>[Additional information:]</p><ul><li><b>Migration guide:</b> <a href="https://learn.microsoft.com/exchange/sharing/migrate-to-m365-xtap" target="_blank">Migrating to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips</a>.</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">Exchange Online EWS, Your Time is Almost Up</a></li><li><a href="https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online" target="_blank">Deprecation of EWS in Exchange Online&nbsp;</a></li><li><a href="https://www.microsoft.com/en-us/security/blog/2025/07/08/enhancing-microsoft-365-security-by-eliminating-high-privilege-access/" target="_blank">Enhancing Microsoft 365 security by eliminating high-privilege access</a>&nbsp;</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/cross-tenant-freebusy-mailtips-and-calendar-sharing-are-moving-to-cross-tenant-a/4545169" target="_blank">Cross-tenant Free/Busy, MailTips, and Calendar Sharing are moving to Cross-Tenant Access Policy</a></li></ul>
New
<p>Updated August 25, 2026: We have updated the content and timeline. Thank you for your patience.&nbsp;</p><p>[What and Why:]</p><p>Exchange Web Services (EWS) deprecation begins <b>October 1, 2026</b>. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS.</p><p>Cross-tenant Free/Busy, MailTips, and Calendar Sharing via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration, will be available starting <b>September 2026</b>.</p><p>[Rollout Schedule:]</p><ul><li>Worldwide: We will begin rolling out in August 2026 and expect to complete by September 15, 2026.</li><li>GCC: We will begin rolling out early September 2026 (previously mid-August) and expect to complete by September 30, 2026 (previously mid-September).</li><li>GCC High: We will begin rolling out early September 2026 and expect to complete by September 30, 2026.</li><li>DoD: We will begin rolling out early September 2026 and expect to complete by October 30, 2026 (previously end of September).</li></ul><p>[Impact on your organization:]</p><p>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.</p><p>Your tenant is affected if it uses any of the following Exchange Online configurations:</p><ul><li><b>Organization Relationships</b> — sharing Free/Busy or MailTips with other Microsoft 365 tenants&nbsp;</li><li><span><span><b>Sharing Policies</b> — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL</span></span></li></ul><p>Run these commands in Exchange Online PowerShell to check if your tenant is affected:&nbsp;</p><ul><li><code>Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScope</code><span></span><ul><li><span>If 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.</span>&nbsp;</li></ul></li><li><code>Get-SharingPolicy | Format-List Name, Domains, Enabled, Default</code><span></span><ul><li> If 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.</li><li>Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL - these also appear in this output.</li></ul></li></ul><p><i><u>What happens if I do nothing:</u></i></p><p>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.&nbsp;</p><p>If your organization <b>is not ready to migrate</b>, you can retain EWS access by following the guidance of the latest blog we published: <a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">ExchangeOnline EWS, Your Time is Almost Up</a> (<b><i>EWSEnabled</i></b><i>&nbsp;set to&nbsp;<b>True</b></i>) 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.&nbsp;</p><p>[Action Required/Recommendations:]</p><ul><li><b>Follow this Message center post</b> for updates to the rollout schedule. To avoid impact, <b>plan to migrate after the rollout reaches your tenant and before EWS deprecation</b>.</li><li><b>Review the migration guide linked below</b> 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.&nbsp;</li><li><b>Check the blog post linked below</b> for additional information and answers to frequently asked questions.&nbsp;</li><li><b>Hybrid and on-premises scenarios are not in scope</b>. 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 <a href="https://learn.microsoft.com/exchange/hybrid-deployment/deploy-dedicated-hybrid-app" target="_blank">Dedicated Hybrid App</a>. 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.&nbsp;</li></ul><p>[Additional information:]</p><ul><li><b>Migration guide:</b> <a href="https://learn.microsoft.com/exchange/sharing/migrate-to-m365-xtap" target="_blank">Migrating to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips</a>.</li><li><a href="https://learn.microsoft.com/graph/api/resources/m365-cross-tenant-access-policy-overview?view=graph-rest-1.0" target="_blank">Microsoft 365 Cross-Tenant Access Policy Microsoft Graph API Overview</a></li><li><a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">Exchange Online EWS, Your Time is Almost Up</a></li><li><a href="https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online" target="_blank">Deprecation of EWS in Exchange Online&nbsp;</a></li><li><a href="https://www.microsoft.com/en-us/security/blog/2025/07/08/enhancing-microsoft-365-security-by-eliminating-high-privilege-access/" target="_blank">Enhancing Microsoft 365 security by eliminating high-privilege access</a>&nbsp;</li><li><b>Blog Post:</b>&nbsp;<a href="https://techcommunity.microsoft.com/blog/exchange/cross-tenant-freebusy-mailtips-and-calendar-sharing-are-moving-to-cross-tenant-a/4545169" target="_blank">Cross-tenant Free/Busy, MailTips, and Calendar Sharing are moving to Cross-Tenant Access Policy</a></li></ul>
August 11, 2026 at 6:31 PM Updated
Last Updated Date
Previous
2026-08-07T20:28:44.487Z
New
2026-08-11T16:40:11.430Z
Body Content
Previous
<p>Updated August 7, 2026: We have updated the content. Thank you for your patience.&nbsp;</p><p>[What and Why:]</p><p>Exchange Web Services (EWS) deprecation begins <b>October 1, 2026</b>. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS.</p><p>Cross-tenant Free/Busy, MailTips, and Calendar Sharing via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration, will be available starting <b>September 2026</b>.</p><p>[Rollout Schedule:]</p><ul><li>Worldwide: We will begin rolling out in August 2026 and expect to complete by September 1, 2026.</li><li>GCC: We will begin rolling out mid-August 2026 and expect to complete by mid-September 2026.</li><li>GCC High: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li><li>DoD: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li></ul><p>[Impact on your organization:]</p><p>Sharing Free/Busy, Calendars, and MailTips (e.g., out of office message) with another Microsoft 365 organization via Organization Relationship, Availability Address Space, 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.</p><p>Your tenant is affected if it uses any of the following Exchange Online configurations:</p><ul><li><b>Organization Relationships</b> — sharing Free/Busy or MailTips with other Microsoft 365 tenants&nbsp;</li><li><span><b>Availability Address Spaces</b> — sharing Free/Busy with other Microsoft 365 tenants (AccessMethod: OrgWideFBToken)&nbsp;</span></li><li><span><span><b>Sharing Policies</b> — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL</span></span></li></ul><p>Run these commands in Exchange Online PowerShell to check if your tenant is affected:&nbsp;</p><ul><li><code>Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScope</code><span></span><ul><li><span>If 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.</span>&nbsp;</li></ul></li><li><code>Get-AvailabilityAddressSpace | Format-List ForestName, AccessMethod</code><span></span><span>&nbsp;</span><ul><li><span>If results show (1) AccessMethod: OrgWideFBToken, and (2) the external organization is hosted in Microsoft 365, your tenant is affected and in scope to migrate. Else, no action is needed.</span>&nbsp;</li></ul></li><li><code>Get-SharingPolicy | Format-List Name, Domains, Enabled, Default</code><span></span><ul><li> If 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.</li><li>Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL - these also appear in this output.</li></ul></li></ul><p><i><u>What happens if I do nothing:</u></i></p><p>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.&nbsp;</p><p>If your organization <b>is not ready to migrate</b>, you can retain EWS access by following the guidance of the latest blog we published: <a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">ExchangeOnline EWS, Your Time is Almost Up</a> (<b><i>EWSEnabled</i></b><i>&nbsp;set to&nbsp;<b>True</b></i>) 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.&nbsp;</p><p>[Action Required/Recommendations:]</p><ul><li><b>Follow the Roadmap post</b> for updates to the rollout schedule. To avoid impact, <b>plan to migrate after the rollout reaches your tenant and before EWS deprecation</b>.</li><li><b>Review the migration guide linked below</b> 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.&nbsp;</li><li><b>Hybrid and on-premises scenarios are not in scope</b>. 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 <a href="https://learn.microsoft.com/exchange/hybrid-deployment/deploy-dedicated-hybrid-app" target="_blank">Dedicated Hybrid App</a>. 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.&nbsp;</li></ul><p>[Additional information:]</p><ul><li><b>Migration guide:</b> <a href="https://learn.microsoft.com/exchange/sharing/migrate-to-m365-xtap" target="_blank">Migrating to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips</a>.</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">Exchange Online EWS, Your Time is Almost Up</a></li><li><a href="https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online" target="_blank">Deprecation of EWS in Exchange Online&nbsp;</a></li><li><a href="https://techcommunity.microsoft.com/blog/microsoft-entra-blog/enhancing-microsoft-365-security-by-eliminating-high-privilege-access/4326671" target="_blank">Enhancing Microsoft 365 security by eliminating high-privilege access</a>&nbsp;</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/cross-tenant-freebusy-mailtips-and-calendar-sharing-are-moving-to-cross-tenant-a/4545169" target="_blank">Cross-tenant Free/Busy, MailTips, and Calendar Sharing are moving to Cross-Tenant Access Policy</a></li></ul>
New
<p>Updated August 7, 2026: We have updated the content. Thank you for your patience.&nbsp;</p><p>[What and Why:]</p><p>Exchange Web Services (EWS) deprecation begins <b>October 1, 2026</b>. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS.</p><p>Cross-tenant Free/Busy, MailTips, and Calendar Sharing via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration, will be available starting <b>September 2026</b>.</p><p>[Rollout Schedule:]</p><ul><li>Worldwide: We will begin rolling out in August 2026 and expect to complete by September 1, 2026.</li><li>GCC: We will begin rolling out mid-August 2026 and expect to complete by mid-September 2026.</li><li>GCC High: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li><li>DoD: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li></ul><p>[Impact on your organization:]</p><p>Sharing Free/Busy, Calendars, and MailTips (e.g., out of office message) with another Microsoft 365 organization via Organization Relationship, Availability Address Space, 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.</p><p>Your tenant is affected if it uses any of the following Exchange Online configurations:</p><ul><li><b>Organization Relationships</b> — sharing Free/Busy or MailTips with other Microsoft 365 tenants&nbsp;</li><li><span><b>Availability Address Spaces</b> — sharing Free/Busy with other Microsoft 365 tenants (AccessMethod: OrgWideFBToken)&nbsp;</span></li><li><span><span><b>Sharing Policies</b> — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL</span></span></li></ul><p>Run these commands in Exchange Online PowerShell to check if your tenant is affected:&nbsp;</p><ul><li><code>Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScope</code><span></span><ul><li><span>If 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.</span>&nbsp;</li></ul></li><li><code>Get-AvailabilityAddressSpace | Format-List ForestName, AccessMethod</code><span></span><span>&nbsp;</span><ul><li><span>If results show (1) AccessMethod: OrgWideFBToken, and (2) the external organization is hosted in Microsoft 365, your tenant is affected and in scope to migrate. Else, no action is needed.</span>&nbsp;</li></ul></li><li><code>Get-SharingPolicy | Format-List Name, Domains, Enabled, Default</code><span></span><ul><li> If 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.</li><li>Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL - these also appear in this output.</li></ul></li></ul><p><i><u>What happens if I do nothing:</u></i></p><p>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.&nbsp;</p><p>If your organization <b>is not ready to migrate</b>, you can retain EWS access by following the guidance of the latest blog we published: <a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">ExchangeOnline EWS, Your Time is Almost Up</a> (<b><i>EWSEnabled</i></b><i>&nbsp;set to&nbsp;<b>True</b></i>) 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.&nbsp;</p><p>[Action Required/Recommendations:]</p><ul><li><b>Follow the Roadmap post</b> for updates to the rollout schedule. To avoid impact, <b>plan to migrate after the rollout reaches your tenant and before EWS deprecation</b>.</li><li><b>Review the migration guide linked below</b> 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.&nbsp;</li><li><b>Hybrid and on-premises scenarios are not in scope</b>. 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 <a href="https://learn.microsoft.com/exchange/hybrid-deployment/deploy-dedicated-hybrid-app" target="_blank">Dedicated Hybrid App</a>. 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.&nbsp;</li></ul><p>[Additional information:]</p><ul><li><b>Migration guide:</b> <a href="https://learn.microsoft.com/exchange/sharing/migrate-to-m365-xtap" target="_blank">Migrating to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips</a>.</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">Exchange Online EWS, Your Time is Almost Up</a></li><li><a href="https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online" target="_blank">Deprecation of EWS in Exchange Online&nbsp;</a></li><li><a href="https://www.microsoft.com/en-us/security/blog/2025/07/08/enhancing-microsoft-365-security-by-eliminating-high-privilege-access/" target="_blank">Enhancing Microsoft 365 security by eliminating high-privilege access</a>&nbsp;</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/cross-tenant-freebusy-mailtips-and-calendar-sharing-are-moving-to-cross-tenant-a/4545169" target="_blank">Cross-tenant Free/Busy, MailTips, and Calendar Sharing are moving to Cross-Tenant Access Policy</a></li></ul>
August 7, 2026 at 10:32 PM Updated
Title
Previous
Migrate Free/Busy, MailTips, and Calendar Sharing before EWS deprecation
New
(Updated) Migrate Free/Busy, MailTips, and Calendar Sharing before EWS deprecation
Summary
Previous
Exchange Web Services (EWS) deprecation starts October 1, 2026, affecting cross-tenant Free/Busy, MailTips, and Calendar Sharing. Migrate to Microsoft 365 Cross-Tenant Access Policy by September 2026 to avoid disruption. Rollout begins August 2026 worldwide; check tenant settings and follow migration guidance.
New
Exchange Web Services (EWS) deprecation starts October 1, 2026, affecting cross-tenant Free/Busy, MailTips, and Calendar Sharing. Migration to Microsoft 365 Cross-Tenant Access Policy begins September 2026. Check your tenant’s configurations and migrate before EWS shutdown on April 1, 2027, to avoid service disruption.
Last Updated Date
Previous
2026-08-03T22:19:08.723Z
New
2026-08-07T20:28:44.487Z
Tags
Previous
User impact,Admin impact,Retirement
New
Updated message,User impact,Admin impact,Retirement
Body Content
Previous
<p>[What and Why:]</p><p>Exchange Web Services (EWS) deprecation begins <b>October 1, 2026</b>. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS.</p><p>Cross-tenant Free/Busy, MailTips, and Calendar Sharing via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration, will be available starting <b>September 2026</b>.</p><p>[Rollout Schedule:]</p><ul><li>Worldwide: We will begin rolling out in August 2026 and expect to complete by September 1, 2026.</li><li>GCC: We will begin rolling out mid-August 2026 and expect to complete by mid-September 2026.</li><li>GCC High: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li><li>DoD: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li></ul><p>[Impact on your organization:]</p><p>Sharing Free/Busy, Calendars, and MailTips (e.g., out of office message) with another Microsoft 365 organization via Organization Relationship, Availability Address Space, 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.</p><p>Your tenant is affected if it uses any of the following Exchange Online configurations:</p><ul><li><b>Organization Relationships</b> — sharing Free/Busy or MailTips with other Microsoft 365 tenants&nbsp;</li><li><span><b>Availability Address Spaces</b> — sharing Free/Busy with other Microsoft 365 tenants (AccessMethod: OrgWideFBToken)&nbsp;</span></li><li><span><span><b>Sharing Policies</b> — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL</span></span></li></ul><p>Run these commands in Exchange Online PowerShell to check if your tenant is affected:&nbsp;</p><ul><li><code>Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScope</code><span></span><ul><li><span>If 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.</span>&nbsp;</li></ul></li><li><code>Get-AvailabilityAddressSpace | Format-List ForestName, AccessMethod</code><span></span><span>&nbsp;</span><ul><li><span>If results show (1) AccessMethod: OrgWideFBToken, and (2) the external organization is hosted in Microsoft 365, your tenant is affected and in scope to migrate. Else, no action is needed.</span>&nbsp;</li></ul></li><li><code>Get-SharingPolicy | Format-List Name, Domains, Enabled, Default</code><span></span><ul><li> If 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.</li><li>Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL - these also appear in this output.</li></ul></li></ul><p><i><u>What happens if I do nothing:</u></i></p><p>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.&nbsp;</p><p>If your organization <b>is not ready to migrate</b>, you can retain EWS access by following the guidance of the latest blog we published: <a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">ExchangeOnline EWS, Your Time is Almost Up</a> (<b><i>EWSEnabled</i></b><i>&nbsp;set to&nbsp;<b>True</b></i>) 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.&nbsp;</p><p>[Action Required/Recommendations:]</p><ul><li><b>Follow the Roadmap post</b> for updates to the rollout schedule. To avoid impact, <b>plan to migrate after the rollout reaches your tenant and before EWS deprecation</b>.</li><li><b>Review the migration guide linked below</b> 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.&nbsp;</li><li><b>Hybrid and on-premises scenarios are not in scope</b>. 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 <a href="https://learn.microsoft.com/exchange/hybrid-deployment/deploy-dedicated-hybrid-app" target="_blank">Dedicated Hybrid App</a>. 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.&nbsp;</li></ul><p>[Additional information:]</p><ul><li><b>Migration guide:</b> <a href="https://learn.microsoft.com/exchange/sharing/migrate-to-m365-xtap" target="_blank">Migrating to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips</a>.</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">Exchange Online EWS, Your Time is Almost Up</a></li><li><a href="https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online" target="_blank">Deprecation of EWS in Exchange Online&nbsp;</a></li><li><a href="https://techcommunity.microsoft.com/blog/microsoft-entra-blog/enhancing-microsoft-365-security-by-eliminating-high-privilege-access/4326671" target="_blank">Enhancing Microsoft 365 security by eliminating high-privilege access</a>&nbsp;</li></ul>
New
<p>Updated August 7, 2026: We have updated the content. Thank you for your patience.&nbsp;</p><p>[What and Why:]</p><p>Exchange Web Services (EWS) deprecation begins <b>October 1, 2026</b>. Cross-tenant collaboration features — Free/Busy, MailTips, and Calendar Sharing — currently rely on EWS.</p><p>Cross-tenant Free/Busy, MailTips, and Calendar Sharing via Microsoft 365 Cross-Tenant Access Policy, which replaces EWS-based cross-tenant collaboration, will be available starting <b>September 2026</b>.</p><p>[Rollout Schedule:]</p><ul><li>Worldwide: We will begin rolling out in August 2026 and expect to complete by September 1, 2026.</li><li>GCC: We will begin rolling out mid-August 2026 and expect to complete by mid-September 2026.</li><li>GCC High: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li><li>DoD: We will begin rolling out early September 2026 and expect to complete by end of September 2026.</li></ul><p>[Impact on your organization:]</p><p>Sharing Free/Busy, Calendars, and MailTips (e.g., out of office message) with another Microsoft 365 organization via Organization Relationship, Availability Address Space, 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.</p><p>Your tenant is affected if it uses any of the following Exchange Online configurations:</p><ul><li><b>Organization Relationships</b> — sharing Free/Busy or MailTips with other Microsoft 365 tenants&nbsp;</li><li><span><b>Availability Address Spaces</b> — sharing Free/Busy with other Microsoft 365 tenants (AccessMethod: OrgWideFBToken)&nbsp;</span></li><li><span><span><b>Sharing Policies</b> — sharing calendars externally, either via invitations sent to recipients in other Microsoft 365 organizations or calendars published for anonymous access via an internet URL</span></span></li></ul><p>Run these commands in Exchange Online PowerShell to check if your tenant is affected:&nbsp;</p><ul><li><code>Get-OrganizationRelationship | Format-List Name, DomainNames, Enabled, FreeBusyAccessEnabled, FreeBusyAccessLevel, FreeBusyAccessScope, MailTipsAccessEnabled, MailTipsAccessLevel, MailTipsAccessScope</code><span></span><ul><li><span>If 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.</span>&nbsp;</li></ul></li><li><code>Get-AvailabilityAddressSpace | Format-List ForestName, AccessMethod</code><span></span><span>&nbsp;</span><ul><li><span>If results show (1) AccessMethod: OrgWideFBToken, and (2) the external organization is hosted in Microsoft 365, your tenant is affected and in scope to migrate. Else, no action is needed.</span>&nbsp;</li></ul></li><li><code>Get-SharingPolicy | Format-List Name, Domains, Enabled, Default</code><span></span><ul><li> If 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.</li><li>Note: rules that begin with Anonymous: represent calendar publishing to anonymous internet recipients via a published URL - these also appear in this output.</li></ul></li></ul><p><i><u>What happens if I do nothing:</u></i></p><p>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.&nbsp;</p><p>If your organization <b>is not ready to migrate</b>, you can retain EWS access by following the guidance of the latest blog we published: <a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">ExchangeOnline EWS, Your Time is Almost Up</a> (<b><i>EWSEnabled</i></b><i>&nbsp;set to&nbsp;<b>True</b></i>) 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.&nbsp;</p><p>[Action Required/Recommendations:]</p><ul><li><b>Follow the Roadmap post</b> for updates to the rollout schedule. To avoid impact, <b>plan to migrate after the rollout reaches your tenant and before EWS deprecation</b>.</li><li><b>Review the migration guide linked below</b> 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.&nbsp;</li><li><b>Hybrid and on-premises scenarios are not in scope</b>. 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 <a href="https://learn.microsoft.com/exchange/hybrid-deployment/deploy-dedicated-hybrid-app" target="_blank">Dedicated Hybrid App</a>. 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.&nbsp;</li></ul><p>[Additional information:]</p><ul><li><b>Migration guide:</b> <a href="https://learn.microsoft.com/exchange/sharing/migrate-to-m365-xtap" target="_blank">Migrating to Microsoft 365 Cross-Tenant Access Policy for sharing Free/Busy, Calendars, and MailTips</a>.</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361" target="_blank">Exchange Online EWS, Your Time is Almost Up</a></li><li><a href="https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online" target="_blank">Deprecation of EWS in Exchange Online&nbsp;</a></li><li><a href="https://techcommunity.microsoft.com/blog/microsoft-entra-blog/enhancing-microsoft-365-security-by-eliminating-high-privilege-access/4326671" target="_blank">Enhancing Microsoft 365 security by eliminating high-privilege access</a>&nbsp;</li><li><a href="https://techcommunity.microsoft.com/blog/exchange/cross-tenant-freebusy-mailtips-and-calendar-sharing-are-moving-to-cross-tenant-a/4545169" target="_blank">Cross-tenant Free/Busy, MailTips, and Calendar Sharing are moving to Cross-Tenant Access Policy</a></li></ul>

Never Miss a Microsoft 365 Update

Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.