Skip to content
Submit support ticket
  • There are no suggestions because the search field is empty.

Retirement of Basic Authentication and EWS for Microsoft Exchange Online

This article explains Microsoft's retirement of Basic Authentication and Exchange Web Services (EWS) for Exchange Online, and what it means for your AskCody integration.

Microsoft has retired Basic Authentication for Exchange Online, and is now retiring Exchange Web Services (EWS) as a whole. Microsoft started blocking EWS requests in Exchange Online on October 1, 2026. The block is rolling out tenant by tenant, and Microsoft completes it in April 2027, when EWS is permanently removed from Exchange Online.

You can read Microsoft's official announcement.

This timeline is set by Microsoft and applies to every application using EWS with Exchange Online, not just AskCody.

This article is written for the IT Admin responsible for the AskCody integration.

What this means for your AskCody integration

AskCody's Exchange Online integration now runs on Microsoft Graph, which replaces both Basic Authentication and Modern Authentication over EWS. The upgrade to Microsoft Graph is the single step that resolves both retirements.

If your integration still uses Basic Authentication (a service account with username and password): your integration is affected by both retirements. Upgrade to Microsoft Graph now. Microsoft is already blocking EWS in Exchange Online, so an EWS integration can stop syncing at any time. Follow How to upgrade your Exchange Online integration to Microsoft Graph. Your Microsoft 365 Global Administrator will need to grant consent to the AskCody enterprise application as part of the upgrade.

If your integration uses Modern Authentication (OAuth 2.0) over EWS: Modern Authentication solved the Basic Auth retirement, but EWS itself is now being retired. Upgrade to Microsoft Graph now, following the same guide.

If your integration already runs on Microsoft Graph: you are done. Nothing in these retirements affects you.

Note: Exchange Server (on-premises and hybrid setups) is not affected by the EWS retirement in Exchange Online. On-premises integrations continue to run on EWS. See How to handle Hybrid Exchange Setups if you run both.

Why Microsoft Graph

Microsoft Graph is Microsoft's supported API for Microsoft 365 data going forward. For your organization, the practical differences are:

  • No service account. No stored credentials, no password rotation, no account to audit separately.
  • Narrower permissions. The Graph integration uses application permissions scoped to calendars and directory basics (Calendars.Read, Calendars.ReadWrite, GroupMember.Read.All, User.Read.All), instead of the full mailbox access EWS applications required. The full list is maintained in Permissions used and required connecting AskCody with MS Graph and Entra ID.
  • No EWS URL or Exchange version configuration. The integration is established through one admin consent.

The deadline in short

  1. October 1, 2026: Microsoft started blocking EWS in Exchange Online, rolling out tenant by tenant.
  2. April 2027: Microsoft completes the rollout and EWS is permanently removed from Exchange Online.
If your integration in the AskCody Management Portal still shows the connection type Exchange Online (Office 365), it is still on EWS. Upgrade it now following these steps: How to upgrade your Exchange Online integration to Microsoft Graph.



If you have questions about your organization's migration, please submit a support ticket.