The change concerns an application interface

Microsoft’s October 1 EWS retirement announcement now has a dated October 2 rollout summary from its Japanese support team.

Exchange Web Services is an interface for mailbox applications. The retirement concerns Exchange Online, including Microsoft 365 cloud environments. Microsoft says EWS is not being retired for on-premises Exchange Server mailboxes. A hybrid organisation must still examine integrations that call cloud mailboxes. The permanent Exchange Online shutdown starts April 1, 2027; Microsoft says there will be no exceptions beyond April.

For a business, our interpretation is straightforward: examine the application and the mailbox it accesses. “We use Outlook” is too broad an inventory entry. A booking service, archive connector or internal script may use a different path from the employee reading messages. This announcement does not mean that Microsoft is shutting down email or every Outlook client.

Source notes: 1, 2. Editorial interpretation and illustrative calculations are identified separately.

October 1 is not one universal switch-off moment

Microsoft’s Pacific-time schedule records Worldwide tenants with EWSEnabled=True and no EWSAllowedAppIDs by October 2’s end. Their lists are populated from 60 days’ activity on October 8–9. From October 10, True requires an AppID allow list; administrators enabling EWS after the snapshot must create one.

Later, Worldwide tenants left at Null without lists face disablement after seven days’ Message Center notice. Other clouds receive separate schedules.

Our reading is that the snapshot concerns eligibility for automatic preparation, not permission to keep a dependency indefinitely. Temporary access is a migration bridge. An organisation should record the applicable cloud, tenant notice and application list together, rather than treating an old global headline date as proof of what happened to its own account.

Source notes: 1, 2. Editorial interpretation and illustrative calculations are identified separately.

Start with an inventory that does not change settings

Microsoft’s EWS usage report identifies applications, SOAP actions and successful-call volumes. Data is aggregated weekly and can take up to ten days to appear. Its selectable windows are seven, 30 or 90 days. That makes it useful evidence, but not an instantaneous map of every dependency.

Our proposed first pass is read-only: list each application ID, its owner, mailbox location, observed actions, business purpose, run frequency and replacement status. Add the last successful business outcome, not just a login. Ask owners about quarterly exports, year-end work and disabled jobs, because a recent activity window cannot prove that those future tasks are unnecessary.

Classify each entry as ready to migrate, requiring a vendor update, requiring a redesign or still unexplained. An unfamiliar application deserves investigation before a keep-or-remove decision. Lumacta has not inspected a customer tenant, changed an allow list or measured application failures; this is a proposed decision checklist.

Source notes: 4. Editorial interpretation and illustrative calculations are identified separately.

Match the required behaviour before choosing a replacement

Microsoft Learn still lists migration capabilities with target dates, including archive access and several import/export scenarios in the fourth quarter of 2026. It warns that estimates can change. It also identifies capabilities that will not be added to Graph: generic Public Folder CRUD, generic Microsoft 365 Group mailbox CRUD and legacy Discovery Mailbox access.

CRUD means creating, reading, updating and deleting items. Importing or exporting a public folder is therefore not the same promise as managing its contents through a general application interface. A roadmap row cannot establish that a particular replacement is available, supported in the organisation’s cloud or suitable for its exact operations.

Our recommendation is to describe the business outcome before selecting an API. If a service needs to preserve an archive’s item fidelity, record which properties and attachments matter. If a missing capability is essential, obtain a supported alternative or redesign the process. A future target date should remain an open dependency in the migration plan.

Source notes: 3. Editorial interpretation and illustrative calculations are identified separately.

A pilot should prove the workflow, not just authentication

Consider a hypothetical booking integration that reads availability and creates calendar entries. A staged test would use approved test mailboxes and synthetic events. Compare the old and proposed paths for time zones, recurring appointments, changed attendees and cancelled meetings. Confirm that retries do not create duplicate bookings and that expected failures are visible to the operator.

Then test the permitted scope: the replacement should reach the intended mailboxes and fail when it attempts an unauthorised one. Agree in advance on the acceptance criteria, rollback method and owner who can stop the pilot. These are Lumacta’s proposed checks, not results from a migration we performed.

Close an inventory entry only when the replacement completes its business task and the old dependency has been removed from the deployed version. A successful sign-in, a converted script or a vendor’s roadmap statement is useful intermediate evidence. None establishes that the organisation’s operating process has already migrated.

Source notes: 3, 4. Editorial interpretation and illustrative calculations are identified separately.

Sources & Methods

Prepared October 2, 2026. October stages use Microsoft Japan’s dated, AI-assisted support translation. The English announcement body was unavailable to our retrieval. Separate Microsoft guidance supports retirement scope, the final deadline, reporting limits and Graph gaps. The inventory and booking pilot are Lumacta’s analysis; no tenant access, settings change or hands-on migration is claimed.

  1. Microsoft Japan support: EWS rollout summary — Primary support-team summary dated October 2, 2026; AI-assisted translation of the October 1 announcement
  2. Microsoft Exchange Team: Exchange Online EWS, Your Time is Almost Up — Primary announcement dated February 5, 2026, with subsequent updates; retirement scope, April 1, 2027 shutdown and no-extension FAQ checked October 2
  3. Microsoft Learn: Deprecation of Exchange Web Services in Exchange Online — Primary documentation marked updated September 4, 2026, checked October 2; capability targets are estimates and several generic operations will not receive Graph equivalents
  4. Microsoft Learn: Exchange Web Services usage report — Primary documentation marked updated May 21, 2026, checked October 2; reporting fields, weekly aggregation and possible ten-day delay