Exchange Online EWS retirement: dates and what to do

Microsoft is switching Exchange Web Services off in Exchange Online, tenant by tenant, and for good on April 1, 2027. Until then an administrator can keep named applications on EWS with an allow list while they move to Microsoft Graph.

October 1, 2026
Microsoft announces that the retirement has started and gives the dates of the first changes. It switches nothing off that day: “We have made no changes at all yet,” a member of the Exchange team wrote in a comment.
October 10, 2026
The list becomes required in the Worldwide cloud: with EWSEnabled set to True, an application that is not on the list loses EWS access. Tenants in other clouds get their dates through Message Center.
October 10 and 11, 2026
For Worldwide tenants that have EWSEnabled set to True and no EWSAllowedAppIDs list, Microsoft creates the list and fills it with the application IDs that used EWS in the previous 60 days. An application that runs less often can be missing from it. After October 11, an administrator who sets EWSEnabled to True has to create the list too.
Second phase, from October 2026
Microsoft is switching EWS off in Worldwide tenants that never set EWSEnabled, where the value is still Null. Its post of October 21, 2026 says the switch-off is in progress. A tenant gets a 7-day warning in Message Center when it is selected. Shortly before the switch, Microsoft fills the tenant's list from 60 days of usage, then sets EWSEnabled to False. EWS stays blocked for every application until an administrator turns it back on.
April 1, 2027
EWS in Exchange Online is switched off for good. Administrators lose the EWSEnabled setting, and Microsoft's post of February 5, 2026 says there will be no exceptions. None of the October posts moves this date. MC1485116 expects the whole rollout to complete by early July 2027, but no tenant is promised EWS after April 1.

If EWS has already stopped for your application

An application that has lost EWS either asks for the user name and password again and again or reports that EWS is not available. Code gets 403 Forbidden. Until April 1, 2027 a tenant administrator can bring it back; Microsoft support cannot do it for you. Start by reading the two settings:

Connect-ExchangeOnline
Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Format-List EwsEnabled, EwsAllowedAppIDs

If EwsEnabled is False, EWS is off for every application. When Microsoft switched it off, Message Center has a post titled “Action may be required: EWS will be disabled in your tenant in 7 days” or “EWS has been disabled in your tenant” with the date. Before the switch Microsoft filled the list from 60 days of usage, so turning EWS back on is enough. In Microsoft 365 admin center, open Baseline security mode and select “Block access to Exchange Web Services”. Clear “Block your entire organization from using EWS” and apply the change, then select the box again and apply again. Although the box still reads Block, EWSEnabled is now True and the applications under Scope summary keep EWS. In PowerShell it is one command. Leave out -EwsAllowedAppIDs so that the list stays as it is:

Set-OrganizationConfig -EwsEnabled $true

If EwsEnabled is True and the application is missing from the list, add its ID. The command stores the whole list, so give every ID from the output above as well as the new one:

Set-OrganizationConfig -EwsEnabled $true -EwsAllowedAppIDs "<every ID on the list>,<new app ID>"

Either way you only buy time until the final date: the applications on the list still have to be migrated. A change to the list can take up to 24 hours to apply, and a change to EWSEnabled usually applies within an hour but can take up to 4 hours. Microsoft's own applications need an entry too when they appear in your EWS usage report; classic Outlook for Mac, for example, needs the “Microsoft Office” application ID. EWSAllowList is a different, older setting and plays no part in the retirement.

Migration checklist

  1. Find the applications that still use EWS

    Start with the EWS usage report in Microsoft 365 admin center (Reports, Usage, Exchange, EWS usage) and look at 90 days, because a quiet week can miss monthly or quarterly jobs. New activity can take days to show up there, so an empty report does not mean nothing calls EWS. Two more places help. In Microsoft Entra admin center, filter the sign-in logs, both user and service principal sign-ins, by the resource Office 365 Exchange Online: apart from Outlook and other Microsoft clients, an application that gets tokens for Exchange Online rather than Microsoft Graph usually calls EWS. In your source code, search for Microsoft.Exchange.WebServices, ExchangeService and /EWS/Exchange.asmx. Then ask the application owners. A script combines the usage report with the allow list and the EWS permissions in Microsoft Entra ID, and gives each application ID a name and an owner. Without the script, paste the IDs into the free EWS app ID lookup, or load the report into the usage checker: both name the Microsoft and vendor apps they know and tell you who has to move them.

  2. Check EWSEnabled and the allow list

    Run the Get-OrganizationConfig command above. With EWSEnabled set to True, every application from step 1 has to be on the list, because from October 10, 2026 the others lose EWS. A list that Microsoft created holds only the application IDs seen in the previous 60 days, so compare it with what you found. If EWSEnabled is not set, EWS keeps working until the second phase, which started in October 2026, reaches the tenant, and then stops for every application. Watch Message Center for the 7-day warning, or set EWSEnabled to True with your own complete list before it comes: Microsoft says it will not change the setting before April 2027 in a tenant that has both.

  3. Separate Exchange Online from on-premises Exchange

    The retirement concerns Exchange Online. On-premises Exchange keeps EWS, so a hybrid application ends up with both. Exchange hybrid itself still needs EWS in Exchange Online for some features: in the table for the dedicated hybrid application, Microsoft Graph covers free/busy and profile pictures, only automatic replies of MailTips, and not moving items to an archive mailbox in the cloud. If mailboxes on Exchange Server have their archive in Exchange Online, Microsoft says to keep the application's EWS permission, EWSEnabled set to True and the application, named ExchangeServerApp- and your organization's GUID, on the list. An on-premises organization with an organization relationship to another tenant needs EWSEnabled set to True in that tenant.

  4. Decide per application: rewrite or keep the code

    A small integration is often quickest to rewrite for Microsoft Graph. For .NET code built on the EWS Managed API there is a second route: keep the code and swap the package. We do either for a fixed price through the migration service. Compare the routes. Found an in-house .NET application in the list? Send us its row and we check it for free.

  5. Check the operations you depend on

    Public folders in Exchange Online have no Microsoft Graph API, whichever route you take. Run your report through the usage checker to see what Sunsetless EWS covers in the code you own.

  6. Test before the tenant's switch-off

    Verify Graph permissions, mailbox scope, stored IDs, sync, search and notifications with your own mailboxes, while you can still compare with EWS.

Common questions

Is the EWS NuGet package deprecated?

No. NuGet.org shows no deprecation notice on Microsoft.Exchange.WebServices, and the latest version, 2.2.0, is from 2015. The retirement concerns EWS in Exchange Online: code built on the package still compiles, and its calls to Exchange Online fail once the tenant blocks EWS. For on-premises Exchange Server nothing changes. The package on NuGet.org ↗

Will my apps be migrated to Microsoft Graph automatically?

No. Each application has to be moved to Microsoft Graph by whoever maintains it: your own developers for in-house code, the vendor for a product you bought. Microsoft updates only its own applications, such as Outlook, and those updates still have to be installed. Excel workbooks that use the Exchange Online connector in Power Query do not move either: each has to be reconnected by hand to Microsoft’s new Mail connector, which is not available yet. Microsoft's reply in the comments, October 2, 2026 ↗

Sources