{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibsttzv7yc4ivbq3hrgyas5uu2cu3z6sszy4cx7wbrudioo67x34u",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3me5pc5newpw2"
  },
  "description": "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 remo...",
  "path": "/m365-message-center/message/mc1227454/",
  "publishedAt": "2026-02-06T01:00:05.000Z",
  "site": "https://blog.tophhie.cloud",
  "tags": [
    "Deprecation of Exchange Web Services in Exchange Online",
    "EWS Retirement Process overview"
  ],
  "textContent": "🚨\n\n**Major Update:** This post contains a significant change that may impact your organisation.\n\n**[Introduction]**\n\nWe'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**.\n\n**[When this will happen:]**\n\n  * **Phased EWS disablement begins:** October 1, 2026\n  * **Full and permanent EWS retirement:** April 1, 2027\n  * **EWS App AllowList feature availability:** Coming soon (before retirement milestones)\n\n\n\n**[How this affects your organization:]**\n\n**Who is affected:**\n\n  * Organizations using **custom or vendor applications** that rely on EWS\n  * Workflows involving mail, calendar, or integrations that use EWS\n  * This change only impacts **Exchange Online; Exchange Server (on-premises)** is not affected\n\n\n\n**What will happen:**\n\n  * Beginning **October 1, 2026** , EWS will be **blocked** unless the tenant configures an `AppID AllowList` and sets `EWSEnabled=True.`\n  * Without admin action, Microsoft will set `EWSEnabled=False` and EWS apps will stop working. Tenant admins will be able to re-enable EWS if necessary.\n  * Temporary “scream tests” may occur before **October 2026** to help identify dependencies.\n  * After **April 1, 2027** , EWS access will be permanently removed with no re-enablement.\n  * No changes are being made to EWS in **Exchange Server (on-premises)**.\n\n\n\n**[What you can do to prepare:]**\n\n  * Review EWS usage in the **Microsoft 365 admin center** or using published scripts to identify dependent applications.\n  * Begin migrating any remaining EWS-based workflows to **Microsoft Graph** , which provides near-complete API parity.\n  * If EWS is required after **October 2026** , configure an `AppID AllowList` and set `EWSEnabled=True` before end of **August 2026.**\n  * Communicate these changes internally and update documentation.\n\n\n\nLearn more:\n\n  * Deprecation of Exchange Web Services in Exchange Online\n  * EWS Retirement Process overview\n\n\n\n**[Compliance considerations:]**\n\nNo compliance considerations identified, review as appropriate for your organization.",
  "title": "MC1227454: Exchange Web Services (EWS) retirement update",
  "updatedAt": "2026-02-06T01:00:05.000Z"
}