Skip to main content

Microsoft Exchange Web Services (EWS) change and impact on mailbox migrations

Explains the EWS deprecation, how it will affect ShareGate Migrate, and how to avoid disruptions with Copy mailbox

Updated today

Starting October 1, 2026, Microsoft will block EWS requests by default across all Exchange Online tenants, with a full, permanent shutdown planned for April 1, 2027.

ShareGate Migrate currently uses EWS for some mailbox migration features.

To avoid disruptions to your mailbox migrations, we recommend configuring your tenant to allow EWS for ShareGate before August 31, 2026.

What's changing

Microsoft's timeline

August 31, 2026

Deadline to configure your tenant to keep EWS enabled. Tenants that set EWSEnabled to True and configure an AppID allow list before this date will be excluded from the automatic October 1 block.

October 1, 2026

EWS is blocked by default in all Exchange Online tenants that have not opted in. Microsoft will set EWSEnabled to False for any tenant still on the default setting.

Tenant administrators can still re-enable EWS after this date, but there will be a service interruption.

April 1, 2027

EWS is permanently shut down in Exchange Online. No re-enablement will be possible after this date.

ShareGate Migrate's plan

ShareGate Migrate currently uses EWS for the following features:

  • In-place archive mailbox migration

  • Microsoft 365 Group mailbox migration (emails and calendar)

For all other migration scenarios, this change has no impact. Standard mailbox migrations do not rely on EWS and will continue to work as expected.

What you need to do

To keep the above features working after October 1, 2026, you can add ShareGate Migrate to your tenant's EWS AppID allow list before August 31, 2026.

Note: These steps must be performed in both your source and destination tenants.

What you'll need

Add ShareGate Migrate to your EWS allow list

  1. Open PowerShell.

  2. Run the following command:

    Set-OrganizationConfig -EWSEnabled $true -EWSAllowList @{Add="ce9858bf-0093-4723-9742-3af3b3c5e25a"}

    This enables EWS for your tenant and adds ShareGate Migrate to your AppID allow list in a single step.

  3. To confirm the change was applied successfully, run:

    Get-OrganizationConfig | Select-Object EWSEnabled, EWSAllowList

    The output should show EWSEnabled as True and the ShareGate Migrate App ID listed under EWSAllowList.

  4. Repeat these steps in your destination tenant if it is a different Microsoft 365 organization.

Important: This configuration is temporary. After April 1, 2027, Microsoft will permanently disable EWS in Exchange Online regardless of tenant settings.

We are working with Microsoft to ensure ShareGate Migrate no longer requires EWS.

Did this answer your question?