MC1227454 High Major change
Exchange Web Services (EWS) retirement update
Summary AI-generated
Exchange Web Services (EWS) in Exchange Online will be phased out starting October 1, 2026, with permanent shutdown on April 1, 2027; migrate workflows to Microsoft Graph.
Suggested actions AI-generated
- Review EWS usage and dependent apps
- Migrate workflows to Microsoft Graph
- Configure AppID AllowList and set EWSEnabled=True if EWS needed post-October 2026
- Communicate changes internally
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1469960 (Updated) Microsoft Exchange Online: Review and configure EWSAllowedAppIDs before Exchange Web Services access changes
- MC1469565 Microsoft Purview | Data Lifecycle Management - Graph API Support for archive mailboxes
- MC1447678 (Updated) Microsoft Exchange Online: Prepare for Exchange Web Services retirement with EWSAllowedAppIDs
- MC1446796 (Updated) Migrate Free/Busy, MailTips, and Calendar Sharing before EWS deprecation
- MC1191578 (Updated) Update to EWS Access for Kiosk / Frontline Worker Licenses
- MC1418559 Action required: Retirement of EWS-based Personal Bookings controls (Microsoft Bookings)
Original post from Microsoft
[Introduction]
We're updating the timeline and process for the retirement of Exchange Web Services (EWS) in Exchange Online. As previously announced, EWS will be retired in favor of Microsoft Graph, which offers improved security, modern authentication, and broader capability support. A phased disablement begins October 1, 2026, with permanent shutdown starting April 1, 2027.
[When this will happen:]
- Phased EWS disablement begins: October 1, 2026
- Full and permanent EWS retirement: April 1, 2027
- EWS App AllowList feature availability: Coming soon (before retirement milestones)
[How this affects your organization:]
Who is affected:
- Organizations using custom or vendor applications that rely on EWS
- Workflows involving mail, calendar, or integrations that use EWS
- This change only impacts Exchange Online; Exchange Server (on-premises) is not affected
What will happen:
- Beginning October 1, 2026, EWS will be blocked unless the tenant configures an
AppID AllowListand setsEWSEnabled=True. - Without admin action, Microsoft will set
EWSEnabled=Falseand EWS apps will stop working. Tenant admins will be able to re-enable EWS if necessary. - Temporary “scream tests” may occur before October 2026 to help identify dependencies.
- After April 1, 2027, EWS access will be permanently removed with no re-enablement.
- No changes are being made to EWS in Exchange Server (on-premises).
[What you can do to prepare:]
- Review EWS usage in the Microsoft 365 admin center or using published scripts to identify dependent applications.
- Begin migrating any remaining EWS-based workflows to Microsoft Graph, which provides near-complete API parity.
- If EWS is required after October 2026, configure an
AppID AllowListand setEWSEnabled=Truebefore end of August 2026. - Communicate these changes internally and update documentation.
Learn more:
[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization.
Additional details from Microsoft
- Summary
- Exchange Web Services (EWS) in Exchange Online will be phased out starting October 1, 2026, with full retirement by April 1, 2027, replaced by Microsoft Graph. Organizations must migrate workflows, configure AppID AllowList to continue EWS use after October 2026, or face permanent EWS access removal.