
Exchange Web Services, or EWS, has long allowed applications to access Microsoft 365 mailboxes, calendars, and contacts. Countless business tools, from scheduling platforms and CRMs to backup and migration utilities, were built on it. However, the situation in Exchange Online has changed significantly. Microsoft is retiring EWS in Office 365, with tenant-by-tenant blocking that began on October 1, 2026 and a permanent shutdown scheduled for April 1, 2027. If an application in your organization has stopped connecting, this guide explains how to check and enable EWS in Exchange Online during the remaining window, how to restrict it safely, and how to plan your migration to Microsoft Graph.
Modernize Your Integrations with AAMAX.CO
The EWS retirement means many organizations must rebuild or update integrations quickly. AAMAX.CO is a full service digital marketing company offering web development, digital marketing, and SEO services worldwide. Their developers build modern integrations with Microsoft 365 using Microsoft Graph and connect them to websites, client portals, and internal tools. If your business relies on legacy EWS-based workflows, their web application development services can help you migrate to a secure, future-proof architecture.
Understanding the EWS Retirement Timeline
Microsoft announced that EWS in Exchange Online would be retired in favor of Microsoft Graph. Starting October 1, 2026, Microsoft began disabling EWS for tenants in phases. Administrators who configured the EWSEnabled setting and an application allow list in advance could keep approved applications working. Tenants that did not prepare may find EWS requests failing. EWS can still be re-enabled after blocking, though there may be a delay before access resumes. On April 1, 2027, EWS will be permanently disabled in Exchange Online with no exceptions. On-premises Exchange Server is not affected by this cloud retirement.
Prerequisites
You will need a Global Administrator or Exchange Administrator role, the Exchange Online PowerShell module installed on your computer, and a list of the applications in your organization that still depend on EWS. Connect to Exchange Online by running Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com and signing in.
Step 1: Identify Applications Using EWS
Before changing settings, find out what relies on EWS. Review sign-in logs and enterprise applications in Microsoft Entra ID, check Microsoft's usage reports for EWS activity, and ask vendors of your third-party tools whether they still use EWS or have moved to Graph. Record each application's ID so you can add only the necessary ones to an allow list.
Step 2: Check Organization-Level EWS Settings
Run Get-OrganizationConfig | Format-List EwsEnabled, EwsApplicationAccessPolicy, EwsAllowList, EwsBlockList. These settings control whether EWS is available in your tenant and which applications can use it. Under the retirement process, explicitly configuring these values signals that your organization intends to keep EWS for specific applications until the final cutoff.
Step 3: Enable EWS for the Organization
To enable EWS, run Set-OrganizationConfig -EwsEnabled $true. Changes can take time to propagate across Microsoft's infrastructure, so allow time before testing. If your tenant was already blocked, re-enabling may involve a short interruption before access is restored.
Step 4: Restrict EWS with an Application Allow List
Rather than allowing every application, restrict EWS to the specific tools that need it. Use the EwsApplicationAccessPolicy and allow list parameters on Set-OrganizationConfig to permit only approved applications. Microsoft has also introduced a dedicated setting for allowed application IDs as part of the retirement process. Consult current Microsoft documentation for the exact parameter names, as they have been updated during the transition. Limiting access reduces security risk and helps you track remaining dependencies.
Step 5: Check Mailbox-Level Settings
EWS can also be disabled for individual mailboxes. Run Get-CASMailbox -Identity user@yourdomain.com | Format-List EwsEnabled. If it is disabled, run Set-CASMailbox -Identity user@yourdomain.com -EwsEnabled $true. Both organization and mailbox settings must allow EWS for an application to work with that mailbox.
Step 6: Confirm Authentication Requirements
Exchange Online no longer supports Basic authentication for EWS. Applications must use OAuth 2.0 through Microsoft Entra ID. Ensure each application is registered in Entra ID with the appropriate API permissions and admin consent. If an older tool still uses a username and password, it will fail regardless of EWS settings and must be updated or replaced.
Step 7: Test Connectivity
Use Microsoft's Remote Connectivity Analyzer to test EWS access to a mailbox. Check the application's own logs for error messages. Common errors include unauthorized responses from missing permissions or consent, and access denied responses when EWS is blocked at the tenant or mailbox level.
Plan Your Migration to Microsoft Graph
Enabling EWS now is only a temporary measure. Microsoft Graph is the long-term replacement, offering a modern REST API for mail, calendars, contacts, files, Teams, and more. Start migration planning immediately:
- Map each EWS operation your applications use to its Graph equivalent.
- Check with vendors for Graph-compatible versions of their products.
- Register new app permissions in Entra ID using least-privilege scopes.
- Use change notifications in Graph to replace EWS streaming and push subscriptions.
- Test thoroughly before the April 2027 cutoff.
Security Best Practices
Keep EWS access limited to essential applications, use application access policies to scope service accounts to specific mailboxes, monitor sign-in and audit logs, and remove EWS permissions as soon as each application is migrated. Treat the remaining time as a transition period rather than a permanent setup.
Connecting Microsoft 365 to Your Website
Many businesses use Microsoft 365 data on their websites, for example to show booking availability, route contact form submissions, or power staff portals. When rebuilding these features with Microsoft Graph, it is a good opportunity to modernize the public-facing experience too. Professional website development can integrate Graph-based features smoothly with your site's design and performance goals.
Conclusion
Enabling Exchange Web Services in Office 365 is still possible during the retirement window by configuring EwsEnabled at the organization and mailbox levels, restricting access with an application allow list, and using OAuth authentication. However, EWS will be permanently disabled in Exchange Online on April 1, 2027. Use the remaining time to keep critical tools running while migrating every integration to Microsoft Graph for a secure, supported future.