EWS blocking began 1 October 2026: fix the allow list before April 2027

EWS blocking started on 1 October 2026. Tenants that left EwsEnabled at its default are being switched off one by one, admins can re-enable it until April, and EWS ends for every tenant on 1 April 2027.

Read time
17 min
Word count
2.8K
Sections
11
FAQs
8
Share
Timeline graphic showing EWS blocked on 1 October 2026 and disabled on 1 April 2027
EWS blocking began on 1 October 2026; it ends for every tenant on 1 April 2027.
On this page · 11 sections
  1. The retirement dates and where things stand now
  2. What EwsEnabled and the allow list actually do
  3. Find every caller before you write the list
  4. Mapping EWS operations to Microsoft Graph
  5. Where Microsoft Graph still does not reach
  6. Deciding per application: migrate, allow-list, or decommission
  7. India-specific considerations
  8. What to do in the next four weeks
  9. FAQ
  10. How eCorpIT can help
  11. References

Summary. Microsoft began blocking Exchange Web Services (EWS) requests in Exchange Online in phases on 1 October 2026 and removes access permanently on 1 April 2027, per the Microsoft Learn deprecation page. The published opt-out date has passed, although Microsoft still leaves alone any tenant that sets EWSEnabled to True with an allow list before its switch-off reaches it. Message Center notice MC1227454, published 5 February 2026, said that tenants which had not configured an AppID AllowList and set EWSEnabled=True by the deadline (the end of August 2026 in that notice, later moved by Microsoft to the end of September) would be switched to EWSEnabled=False, at which point every EWS application in the tenant stops working. Those switch-offs were under way by late October: each affected tenant gets a seven-day Message Center warning first, and an admin can still turn EWS back on until April 2027. The protocol has been on notice since July 2018, the shutdown date was fixed in 2023, and EWS itself has shipped since Exchange Server 2007. The cost context has moved too: Microsoft raised Office 365 E3 by 13% from $23.00 to $26.00 per user per month on 1 July 2026, and Microsoft 365 F3 by 25% to $10.00, so the frontline SKUs most exposed to EWS licence changes are also the ones that repriced most steeply. Microsoft Graph is the replacement, and the parity gaps are documented rather than hypothetical.

This runbook covers the retirement dates and where the rollout stands in November 2026, the exact PowerShell surface, how to find every caller, the operation-level mapping to Microsoft Graph, and the workloads where Graph still does not reach.

The retirement dates and where things stand now

Microsoft has published the retirement in stages rather than as a single cutover. The timeline below is drawn from the Microsoft Learn deprecation article, Message Center notices MC1227454 and MC1485116, and the Exchange Team blog.

Date What Microsoft does What you have to do first
July 2018 Announces that EWS will receive no further functionality updates in Exchange Online Treat any EWS code path as frozen
2023 Fixes the disablement date at October 2026 and announces blocking of non-Microsoft app requests Start the application inventory
End of September 2026 Published cut-off for setting an AppID AllowList with EWSEnabled=True to stay out of the automatic switch-off (moved from the end of August) Passed; check what your tenant is set to now
1 October 2026 Begins the phased rollout; tenants still on Null get a seven-day Message Center warning, then EWSEnabled=False (switch-offs under way by late October) Confirm allow-listed apps still authenticate
10 October 2026 Requires an AppID allow list whenever EWSEnabled=True in the worldwide cloud, after filling empty lists from 60 days of usage Review any list Microsoft generated and remove apps you no longer want
1 April 2027 Disables EWS in Exchange Online permanently; admins lose the EWSEnabled control and Microsoft grants no extensions Every remaining app must already run on Graph

Two details of the rollout are easy to miss. The first is that Microsoft announces each switch-off in Message Center, with a warning seven days ahead and a second post once EWS is disabled, so search Message Center before treating a sudden EWS failure as an incident. The second is the wording of the default: without admin action Microsoft sets EWSEnabled=False, and only a tenant admin can turn EWS back on; Microsoft support cannot do it. Setting the switch back to True, in Baseline Security Mode or PowerShell, usually works within an hour and occasionally takes up to four hours, using an allow list Microsoft pre-fills from the last 60 days of usage. That makes the outage recoverable until April 2027, but it is still an outage across every EWS application at once, and recovery depends on someone knowing which switch to throw.

The scope is narrower than the panic suggests. The 2023 announcement on the Microsoft 365 Developer Blog states that the change applies only to Microsoft 365 and Exchange Online, with no changes to EWS in Exchange Server. It also covers the EWS SDKs for Java and .NET, which is where most in-house code sits. Hybrid tenants need to work out which side of the boundary each dependency runs against before they classify it. Microsoft's September 2026 hybrid guidance adds one case to keep on EWS for now: on-premises mailboxes with archives in Exchange Online, where the tenant should keep EWSEnabled at True and add the hybrid application to the allow list.

What EwsEnabled and the allow list actually do

The control surface is Exchange Online PowerShell, and it predates the retirement. Microsoft Learn documents the current cmdlet behaviour on the EWS access control page, including a note that the way EWSEnabled operates changed in October 2026 because of the deprecation.

There are two distinct mechanisms and they get confused constantly. The older one filters by user agent string. The newer one filters by Microsoft Entra application ID, and it is the one the retirement uses.


            # Application-ID allow list: only these AppIDs may call EWS when EWSEnabled is True. Each call replaces the whole list
Set-OrganizationConfig -EwsAllowedAppIDs "11111111-2222-3333-4444-555555555555,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"

# Tenant switch. Null still allows all EWS, but Microsoft began moving Null tenants to False in October 2026
Set-OrganizationConfig -EwsEnabled:$true

# Read the AppID list back; it is only returned with this switch
Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Format-List EwsAllowedAppIDs

# Legacy user-agent controls, still present, not the retirement mechanism
Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceAllowList -EwsAllowList:"OWA/*"
Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceBlockList -EwsBlockList:"OWA/*"

# Per-mailbox override. Disabling EWS at the organization level also disables these
Set-CASMailbox -Identity adam@contoso.com -EwsEnabled:$false
          

Three behaviours matter operationally. Setting EwsAllowedAppIDs restricts EWS to the listed GUIDs only when EWSEnabled is True, so the switch and the list are a pair rather than alternatives. Disabling EWS at the organization level also disables per-user overrides, which means a tenant-wide $false is absolute. And Microsoft's Set-OrganizationConfig reference records that the parameter applies to direct EWS SOAP connections only, so it does not affect Microsoft Graph or REST endpoint requests; you cannot use it to throttle a Graph migration by accident.

Two verification habits are worth building now. Read the configuration back with Get-OrganizationConfig after every change (add the -RetrieveEwsOperationAccessPolicy switch to see the AppID list, and allow 24 hours for list changes to apply), and keep the resulting AppID list in source-controlled tenant documentation rather than in an admin's notes. The allow list is an access grant; it deserves the same change control as a firewall rule.

The temptation is to set the switch, add every AppID the usage report shows, and move on. Tiago Carvalho, a Microsoft 365 architect who published an EWS retirement discovery playbook in June 2026, puts the objection plainly: "The Allow List is a stopgap, not a strategy." Everything on that list still has to be off EWS before 1 April 2027, and the list is the thing that tells you how much work you deferred.

Find every caller before you write the list

An allow list built from an incomplete inventory is worse than no allow list, because it looks finished. Microsoft ships a first-party discovery tool, and its limits are documented.

The Exchange Web Services usage report sits in the Microsoft 365 admin center under Reports, then Usage, then Exchange, then the EWS usage tab. Microsoft Learn describes what it returns:

  • Two summary headers: Active apps, the number of unique applications that sent at least one EWS request in the period, and Daily average call volume.
  • A usage details table with four columns you cannot customise: Application ID, SOAP Action, Call Volume, and Last Activity date (UTC).
  • Filters for the last 7, 30, or 90 days, with an explicit note that usage data is collected and aggregated weekly, not daily.
  • An Export control that writes the data to an Excel .csv file for sorting and filtering.

The Application ID column is the point of the exercise. That GUID is what goes into EwsAllowedAppIDs, and it is what a migration ticket needs. Microsoft also points admins at its published list of commonly used first-party application IDs so that legitimate Outlook or Teams traffic is not logged as a rogue custom integration.

The weekly aggregation and the 90-day ceiling are the two constraints that break a naive inventory. A quarterly reconciliation job that runs on the first working day of each quarter can fall outside a 90-day window depending on when you look, and the report will show nothing. Carvalho's playbook adds three complementary sources for exactly this reason: the Unified Audit Log activity EwsAccess, which reaches further back subject to audit retention; Microsoft Entra ID sign-in logs filtered on the Office 365 Exchange Online resource, which catch applications that authenticated even if the call failed; and a static inventory of app registrations holding EWS-relevant grants such as the full_access_as_app application role or the EWS.AccessAsUser.All delegated scope. Permissions granted do not prove usage, and usage inside 90 days does not prove the full set. Run all four.

Code-side discovery is separate again. Microsoft publishes an EWS Analyzer tool and an AI-assisted code analysis and refactoring tutorial, both linked from the deprecation page, for the case where a scheduled task or an old .NET service contains EWS calls that have not fired inside any log window.

Mapping EWS operations to Microsoft Graph

Most of the migration is mechanical. Microsoft publishes an operation-level mapping table, and the common mail, folder, attachment, and synchronisation paths have direct equivalents.

EWS operation Microsoft Graph replacement Migration note
FindItem List messages Direct list call; rework paging and filter syntax
GetItem Get message Direct; property selection replaces shape definitions
CreateItem / SendItem Create message, then Send message or Send mail Two Graph shapes for one EWS operation
SyncFolderItems Get messages delta Delta tokens replace sync state blobs
SyncFolderHierarchy Get mail folder delta Same delta pattern at folder level
Subscribe (push) Create subscription Webhook lifecycle with explicit renewal
GetEvents (pull) Get messages delta Graph requires a subscription only for push
GetUserOofSettings Get user mailbox settings Out-of-office moves into mailbox settings
GetUserAvailability Get free/busy schedule Availability collapses into one call
ConvertId Translate Exchange IDs Needed when both stacks run in parallel

The mapping table is the fastest way to size an in-house application: pull the SOAP Action column from the usage report export, join it against the mapping, and the rows that match are the ones a competent developer can port in days. The rows that do not match are the project.

Pull notifications deserve a specific call-out. Microsoft's note on the mapping page is that Graph requires a subscription only for push notifications, and that applications currently using EWS pull notifications should move to the delta query instead. Teams that try to recreate a pull loop on top of Graph subscriptions are solving a problem they no longer have.

Authentication changes with it. The Graph migration overview states the reason plainly: Graph applies OAuth with granular scoping to limit data access within a mailbox, against what Microsoft calls the all or none access model in EWS. Graph is also REST rather than SOAP, which Microsoft cites for faster JSON serialisation and lower network usage. A migration that copies the old broad permission shape into Graph keeps the security posture that made EWS a liability after the January 2024 Midnight Blizzard incident, which the deprecation page names as the event that widened the retirement scope from third-party applications to Microsoft's own.

Where Microsoft Graph still does not reach

The deprecation page carries a roadmap table of the feature gaps Microsoft plans to close, each with a target quarter that Microsoft says may change, and a short list of capabilities that will never reach Graph. The table below reflects the page as updated in October 2026. This is the list that decides which applications need the allow list rather than a sprint.

EWS capability Current Graph position Practical consequence
Mailbox import and export In preview, excluding Microsoft 365 Groups and public folder mailboxes; archive mailboxes targeted for Q4 2026 Migration and backup vendors are the exposed class
Import and export of public folders Targeted for Q4 2026 Public folder tooling has no clean target yet
Import and export of Microsoft 365 Groups Targeted for Q4 2026 Group mailbox archival needs a redesign
In-place Archive Generic item access in an existing archive targeted for Q4 2026 Validate each archive workflow against a test mailbox
Event delta for recurring events No longer listed on the roadmap; Microsoft says not to count on unlisted items before EWS ends Calendar sync with recurrence needs testing before cutover
Sticky Notes CRUD Listed with a Q3 2026 target that has passed; confirm before relying on it Small surface, but it blocks the apps that use it
User configuration Targeted for Q4 2026 Folder-associated settings storage is not yet stable
Administration APIs In preview; folder permissions and more recipient settings targeted for Q4 2026 Admin automation on EWS is the slowest track
Contact lists, report message, non-draft MIME, mark all as read Added to the roadmap with Q3 or Q4 2026 targets Check each against your SOAP Action export
Generic public folder and Group mailbox item access, Discovery mailboxes Will not be added to Graph Redesign, or move discovery work to Microsoft Purview eDiscovery

Microsoft's guidance on the same page is not to wait for the gaps to close. The sequencing that follows from the table is to migrate everything the mapping covers now, put the roadmap-blocked applications on the allow list with a named owner and a date, and treat preview APIs as a signal to build a proof of concept rather than a production commitment.

Backup, archiving, and mailbox migration tooling sits almost entirely in the blocked column, because import and export is the capability those products are built on. If a vendor tells you their Graph-based release is coming, ask which of the roadmap items above it depends on.

Deciding per application: migrate, allow-list, or decommission

Every application in the inventory resolves to one of four outcomes. The comparison below is the one to take into a change board, because it prices the decision in the vectors that actually differ.

Decision Time to deliver Ongoing overhead When it is the right call
Port to Microsoft Graph now Days for a script, weeks for a service Lowest; supported API surface Every SOAP action has a mapping-table equivalent
Upgrade to the vendor's Graph release Days, plus a pilot window Vendor-managed Third-party product with a shipped Graph version
Allow-list as a stopgap Hours Monthly review until removed Roadmap gap, or the original author has left
Decommission Hours, plus stakeholder confirmation None Last Activity date is stale and no owner claims it
Rebuild on a different pattern Weeks Depends on target EWS impersonation or extended properties are load-bearing

The cheapest outcome is the fourth one, and it is the one teams skip. Sort the usage report export by Last Activity date, then by call volume ascending, and the bottom of that list is usually two or three integrations nobody has thought about since 2019. Confirming they are dead costs an afternoon and removes them from every future audit.

The real cost here is rarely the code. It is finding the owner.

The same discipline applies to any deprecation with a hard date, which is why the pattern repeats across vendors: the Bing Webmaster Tools SOAP and POX API retirement and the Content API for Shopping move to the Merchant API both turned on inventory quality rather than developer effort. If you have run one of those, the shape of this work will look familiar. It is the same discipline that runs through the wider web platform and API developer guide: the standard changes on a published date, and the inventory decides whether that date hurts.

India-specific considerations

Indian enterprises and global capability centres carry a specific version of this problem. A large share of EWS integrations in Indian delivery estates were written by vendor teams under fixed-scope contracts that ended years ago, which means the application exists, the AppID is live, and the contractual owner does not. Start the vendor conversation now rather than after EWS is switched off in your tenant, because an escalation into a partner who no longer staffs the account is slow, and Microsoft has said there will be no extensions past 1 April 2027.

The licensing angle is sharper in India too. Frontline SKUs are heavily used across retail, logistics, and manufacturing floors here, and those are the SKUs that repriced hardest on 1 July 2026: Microsoft 365 F1 rose 33% from $2.25 to $3.00 per user per month and F3 rose 25% from $8.00 to $10.00, against 8% for Microsoft 365 E3 at $39.00. Any remediation plan that quietly assumes moving frontline users to a richer SKU should be costed at the new rates.

Data protection sits on top. EWS applications typically hold broad mailbox access, and mailbox contents are personal data under the Digital Personal Data Protection Act 2023. A Graph migration is the natural moment to narrow that access, because Graph supports scoping to specific mailboxes rather than the all-or-nothing model EWS used. Teams running an API integration modernisation programme should fold the EWS work into it rather than running a parallel project, and the same access-narrowing logic behind Entra ID risk policies and conditional access migration applies here to application permissions.

What to do in the next four weeks

The work splits cleanly into discovery, decision, and configuration, and only the last of those is technical.

Week one is discovery. Export the EWS usage report at the 90-day filter, query the Unified Audit Log for EwsAccess across the longest window your audit retention allows, filter Entra sign-in logs on the Office 365 Exchange Online resource, and enumerate app registrations holding EWS grants. Merge the four into a single register keyed on AppID.

Week two is ownership. Every row needs a named person inside your organisation, not a vendor name. Rows with no owner after a week of asking are decommission candidates by default, and saying so in writing tends to produce the owner.

Week three is decision. Join the SOAP Action column against the Microsoft Graph mapping table, mark each application against the five outcomes above, and confirm vendor Graph release status in writing with a reference number.

Week four is configuration. Set EWSEnabled to $true, populate EwsAllowedAppIDs with only the GUIDs that survived the decision pass (each update replaces the whole list, including one Microsoft generated, so include every app you still need), read the configuration back with Get-OrganizationConfig, and commit the list to tenant documentation with a review date. Then watch the usage report over the following weeks to confirm that allow-listed applications still call successfully and that nothing else does.

One habit to carry into 2027: the allow list should shrink every month. If it is the same length in January that it was in November, the migration is not happening, and 1 April 2027 arrives without a second stopgap behind it.

FAQ

How eCorpIT can help

eCorpIT builds and modernises Microsoft 365 integrations for enterprises in India and abroad, and the EWS work is a familiar shape: inventory first, ownership second, code last. Our senior engineering teams run the four-source discovery pass, produce an AppID register with a decision against every row, configure and document the allow list, and port the applications that have a Graph equivalent. We are CMMI Level 5, MSME certified and ISO 27001:2022 certified, and we design application permissions to the narrowest scope the workload needs rather than reproducing the EWS access model in Graph. If you need the allow list reviewed and the migration finished before April 2027, talk to our team.

References

  1. EWS Deprecation Is Here: What This Means To You — Microsoft Exchange Team Blog
  1. Exchange Online EWS application stopped working? Do this. — Microsoft Exchange Team Blog
  1. Exchange Online EWS, Your Time is Almost Up — Microsoft Exchange Team Blog
  1. MC1485116: Exchange Web Services (EWS) enforcement update for EWSAllowedAppIDs — Microsoft 365 Message Center Archive
  1. Impact of Exchange Online EWS Deprecation on Hybrid Rich Coexistence and Cross-org Sharing — Microsoft Exchange Team Blog
  1. Deprecation of Exchange Web Services in Exchange Online. Microsoft Learn, retirement timeline and Graph parity roadmap.
  1. MC1227454: Exchange Web Services (EWS) retirement update. Microsoft 365 Message Center archive, published 5 February 2026.
  1. Retirement of Exchange Web Services in Exchange Online. Microsoft 365 Developer Blog, the 2023 announcement.
  1. Control access to EWS in Exchange. Microsoft Learn, cmdlet reference for EwsAllowedAppIDs and EWSEnabled.
  1. Set-OrganizationConfig (ExchangePowerShell). Microsoft Learn, parameter reference.
  1. Exchange Web Services (EWS) usage report. Microsoft Learn, report columns, filters and export.
  1. Migrate Exchange Web Services (EWS) apps to Microsoft Graph. Microsoft Learn, security and REST rationale.
  1. Exchange Web Services (EWS) to Microsoft Graph API mappings. Microsoft Learn, operation-level mapping tables.
  1. EWS Retirement 2026: How to Find Legacy Exchange Integrations Before They Break. Tiago S. Carvalho, Microsoft 365 architect, June 2026.
  1. Microsoft 365 Pricing and Packaging Updates. Microsoft Licensing Resources, commercial pricing effective 1 July 2026.
  1. Microsoft 365 Packaging and Pricing Updates Public FAQ. Microsoft Licensing Resources.
  1. Prepare for EWS retirement in Exchange Online. Microsoft Learn, hybrid-specific preparation guidance.

Last updated: 11 November 2026.

Frequently asked

Quick answers.

01 When did Microsoft start blocking EWS in Exchange Online?
Phased blocking began on 1 October 2026 and is reaching tenants one at a time, according to the Microsoft Learn deprecation page, Message Center notice MC1227454 and the Exchange Team blog. EWS is then disabled permanently on 1 April 2027 with no re-enablement. Exchange Server on premises is not affected by either date, and hybrid tenants must identify which side each dependency runs against.
02 What happens to tenants that missed the allow list deadline?
Microsoft sets EWSEnabled=False for tenants that left the switch at its default (Null) instead of setting it to True with an AppID AllowList. By late October it had started doing this tenant by tenant, after a seven-day Message Center warning, and every EWS application in the tenant then stops working. A tenant admin can re-enable EWS until April 2027, so the outage is recoverable but disruptive.
03 Which PowerShell command sets the EWS application allow list?
Microsoft Learn documents Set-OrganizationConfig -EwsAllowedAppIDs with a comma-separated list of Microsoft Entra application GUIDs. Those applications can use EWS only when EWSEnabled is set to True. The parameter applies to direct EWS SOAP connections and does not affect Microsoft Graph or REST endpoint requests at all.
04 Does the allow list let us keep using EWS after April 2027?
No. The allow list only keeps EWS running through the phased switch-off that began on 1 October 2026. Microsoft removes EWS access permanently on 1 April 2027 with no re-enablement path. Microsoft 365 architect Tiago Carvalho describes it as a stopgap rather than a strategy, and every allow-listed application still needs a delivered migration plan.
05 How do I find every application in my tenant that calls EWS?
Start with the EWS usage report in the Microsoft 365 admin center, which lists Application ID, SOAP Action, Call Volume, and Last Activity date across 7, 30, or 90 days. Because data aggregates weekly and stops at 90 days, add the Unified Audit Log, Entra sign-in logs, and app registration grants.
06 Which EWS operations map cleanly to Microsoft Graph today?
Microsoft publishes an operation-level mapping table. FindItem, GetItem, CreateItem, SendItem, SyncFolderItems, SyncFolderHierarchy, Subscribe, GetUserOofSettings and GetUserAvailability all have documented Graph equivalents. Applications using EWS pull notifications should move to the delta query rather than recreating polling on top of Graph subscriptions.
07 Which EWS scenarios still have no Microsoft Graph equivalent?
The Microsoft Learn roadmap, updated in October 2026, targets Q4 2026 for archive, public folder and Microsoft 365 Groups import and export, in-place archive access, user configuration and more admin APIs. Generic public folder and Group mailbox item access and Discovery mailbox access will never come to Graph, and event delta for recurring events is no longer listed. Backup and migration tooling is the most exposed category.
08 Does the EWS retirement affect Exchange Server on premises?
No. The 2023 announcement on the Microsoft 365 Developer Blog states that the retirement applies only to Microsoft 365 and Exchange Online across all environments, with no changes to EWS in Exchange Server. Hybrid deployments keep on-premises EWS for as long as that Exchange Server version supports it.

About the author

Manu Shukla

Founder & Director

Founder of eCorpIT. Hands-on engineer leading senior-only delivery for AI apps, custom software, and cloud systems for global clients.

Subscribe

One engineering note a week. No fluff, no spam.

Senior-architect playbooks on AI agents, mobile apps, cloud, security, data, and marketing — delivered every Wednesday.

Past the reading

Read enough. Let's build something.

A senior architect responds in 24 working hours with scope, indicative cost, and a timeline. NDA before any technical conversation.

Loading search…

Browse all guides