Microsoft’s Exchange Web Services retirement in Exchange Online, the phased shutdown of the older EWS protocol, began on October 1, 2026, and the protocol gets shut off for good on April 1, 2027. If your business runs a CRM sync, a scan-to-email printer, a backup tool, or a scheduling add-in that was set up more than a couple of years ago, there is a real chance it talks to Microsoft 365 through EWS and will quietly stop working. The fix is not hard, but somebody has to find the affected app before Microsoft finds it for you.
- EWS access to Exchange Online started getting blocked for tenants that had not configured it on October 1, 2026, with full shutdown on April 1, 2027.
- Tenants that set up an EWS AppID allow list before the deadline could delay the automatic block, but that window has now passed for anyone who did not act by late August.
- Common SMB casualties: multifunction printer scan-to-email, older CRM and accounting sync tools, legacy backup software, and some scheduling or fax-to-email services.
- Microsoft’s replacement is the Graph API, and most mainstream software vendors already support it. The ones at risk are older or niche tools nobody has touched since they were installed.
- A 20-minute app inventory this week is cheaper than an outage discovered when a vendor sync silently stops updating records.
What is actually changing on October 1?
EWS is the older programming interface Exchange and Exchange Online used to let outside applications read mail, calendars, and contacts. Microsoft has been pushing developers toward Microsoft Graph for years, and it is now closing the door on the old path. Per the Microsoft 365 Message Center notice MC676299, tenants that did not explicitly configure an EWS AppID allow list and set EWSEnabled to true had the protocol switched off automatically starting October 1, 2026. Petri’s coverage of the rollout confirms the hard stop lands April 1, 2027, after which Microsoft says there will be no exceptions or extensions.
This only affects Exchange Online and Microsoft 365. If you still run on-premises Exchange Server, this specific change does not touch you, though Microsoft has separately been winding down older on-prem versions.
Which of your tools are quietly using EWS?
Most business owners have never heard of EWS because it works in the background. The usual suspects are the integrations nobody remembers configuring:
- Office copiers and multifunction printers with a scan-to-email or scan-to-mailbox feature
- Older CRM or practice-management software that syncs calendar and contact data with Outlook
- Third-party backup or archiving tools that pull mailbox data directly
- Fax-to-email gateways and some appointment-reminder services
- Custom scripts or macros an outgoing IT person built years ago and never documented
If any of these were installed before 2022 and nobody has touched the connection since, treat it as a suspect until the vendor confirms otherwise.
How do you find out if you are affected?
Start with your Microsoft 365 admin center and check whether EWS is already reporting blocked requests for your tenant. If you have an IT provider, ask them directly whether they have reviewed your EWS AppID allow list against MC676299. If you manage Microsoft 365 yourself, the practical approach is to list every piece of hardware and software that touches your email system, then call each vendor and ask one question: does this product use Exchange Web Services, and if so, when is the Graph API-based update available? This is the same exercise we walk clients through during an IT asset inventory, and it is worth doing now even if you think you dodged this particular change.
Why does this matter more during a Florida hurricane season?
Southwest Florida businesses already lean on automated notifications, scan-to-email for storm documentation, and remote access tools when a location closes ahead of a storm. An integration that fails quietly in October looks like a minor annoyance until you need that scanned document trail or automated alert in a crunch next summer. Pair this check with the review you already do around Patch Tuesday changes, like the one we covered after the October 2026 Patch Tuesday Exchange Server updates, so you are not tracking Microsoft changes in two separate places.
What should you do before April 2027?
Give your IT provider or in-house admin a specific task: audit every app and device with mailbox access, confirm each one’s EWS dependency with the vendor, and get a timeline for any Graph API update or replacement. If a vendor has no answer, that is your signal to start shopping for a replacement rather than wait for a bounced email or a printer that stops scanning to your inbox.
Frequently asked questions
Does this affect Gmail or other non-Microsoft email?
No. This retirement only applies to Exchange Online and Microsoft 365 mailboxes. Google Workspace and other platforms are not affected by this specific change.
Will my email stop working entirely?
No. Core Outlook, Outlook on the web, and mobile mail access are unaffected. Only third-party applications and devices that connect through the older EWS protocol are at risk, and only for the specific feature that depends on it.
What if we missed the August 2026 allow-list deadline?
You can still configure the EWS AppID allow list and request re-enablement for specific applications while Microsoft works through the phased rollout, but do not wait. The permanent shutdown on April 1, 2027 applies regardless of when you act.
How do we know if our printer or CRM uses EWS?
Check the vendor’s documentation or support page for mentions of Exchange Web Services or Microsoft Graph, or contact their support line directly. Most mainstream vendors have already published guidance for this transition.
If you want help running this audit instead of guessing which of your tools are affected, SWFIT offers a free 15-minute IT review to walk through your Microsoft 365 integrations and flag anything at risk before April 2027. Reach out to schedule yours.
SWFIT
