# EWS Retirement: Loop Backup Is Ready for Microsoft Graph > Microsoft is retiring Exchange Web Services (EWS) in Exchange Online, with shutdown beginning October 1, 2026 and permanent removal on April 1, 2027. Loop Backup is already Graph-first, here is what administrators need to know, and why Loop Backup customers do not need to take action. Source: https://loopbackup.com/blog/ews-retirement-loop-backup-microsoft-graph Publisher: Loop Backup Content language: en --- _Last updated May 23, 2026 · ~7 min read_ ## At a Glance - Exchange Web Services (EWS) in Exchange Online will be **disabled by default on October 1, 2026**, with **permanent shutdown on April 1, 2027**. - Microsoft recommends all vendors and customers migrate mailbox integrations to **Microsoft Graph**. - Microsoft 365 administrators should begin auditing EWS-dependent applications now using the built-in **EWS Usage Report**. - **[Loop Backup](/) customers do not need to take action.** Loop Backup already uses a Graph-first architecture for Microsoft 365 backup and recovery. --- Microsoft is officially retiring Exchange Web Services (EWS) for Exchange Online. Any product, script, migration platform, or backup system still relying on EWS must transition to Microsoft Graph before the final shutdown deadline. For many businesses, this matters more than they realise. EWS has historically powered mailbox backup, migration, archiving, and automation tools across Microsoft 365 environments. Once Microsoft disables EWS, applications that have not migrated may stop functioning entirely. If you are a Loop Backup customer, there is no action required. Loop Backup is already built around modern Microsoft 365 APIs and is actively completing the remaining migration work ahead of Microsoft's deadlines. ## EWS Retirement Timeline Microsoft updated the EWS retirement schedule in February 2026 with a phased shutdown plan and stricter enforcement deadlines. ### Key Dates | Date | Change | Impact | |------|--------|--------| | 2018 | EWS stopped receiving major feature updates | Legacy status began | | Sept 19, 2023 | Microsoft announced EWS retirement | Migration planning started | | Jul 1, 2026 | EWS blocked for some Kiosk/F1/F3 mailboxes | Early impact for some tenants | | End of Aug 2026 | Deadline for AppID AllowList configuration | Required to temporarily keep EWS active | | Oct 1, 2026 | EWS disabled by default | Applications may stop working | | Apr 1, 2027 | EWS permanently removed | No re-enablement possible | Microsoft also plans temporary "scream tests" before October 2026, where EWS may be disabled for short periods to expose hidden dependencies. ## AppID AllowList: Temporary Grace Period Only Microsoft introduced a temporary AppID AllowList mechanism for organisations that still depend on EWS. From **October 1, 2026**: - EWS will be disabled by default. - Administrators must explicitly set `EWSEnabled=True`. - Administrators must maintain an approved AppID AllowList for applications still using EWS. This is not a long-term solution. After **April 1, 2027**, EWS access is permanently removed regardless of configuration. Any vendor still depending on EWS after that date represents operational risk. ## How to Identify EWS Usage in Microsoft 365 Most organisations are unaware how many tools still rely on EWS behind the scenes. Microsoft provides a built-in **EWS Usage Report** inside the Microsoft 365 Admin Center: **Path:** Microsoft 365 Admin Center → Reports → Usage → Exchange → EWS Usage The report shows: - Application IDs - Service principals - SOAP actions - Usage volume - Last activity timestamps This allows administrators to identify: - Legacy backup tools - Old migration utilities - Internal scripts - Compliance or archive software - Third-party integrations ## Microsoft Graph Gaps to Be Aware Of Although Microsoft Graph now covers most mailbox workloads, there are still several areas Microsoft continues improving. Known areas include: - Online Archive mailbox coverage - Recoverable Items handling - Certain mailbox configuration settings - Public folder access - Some Exchange management operations These areas particularly affect: - Backup vendors - Compliance platforms - Migration systems - Enterprise archive products Any vendor claiming "Graph support" should also explain how they handle these edge cases. ## Questions to Ask Any Backup Vendor If you use Microsoft 365 backup software, now is the time to ask direct technical questions. ### Important Questions 1. Do you still use EWS anywhere today? 2. Which workloads still rely on EWS? 3. Is Microsoft Graph the primary API or only partial coverage? 4. How do you handle Graph throttling? 5. What happens during API interruptions? 6. Is Online Archive support fully migrated? 7. Will your platform still function after April 1, 2027? 8. Can you provide a dated migration roadmap? If a vendor cannot answer clearly, that should be treated as a warning sign. ## How Loop Backup Is Preparing Loop Backup already operates with a **Graph-first Microsoft 365 backup architecture**. ### Already Using Microsoft Graph Loop Backup already uses Microsoft Graph and modern Microsoft authentication for: - [Exchange Online mailbox backup](/exchange-backup) - Contacts - Calendars - [OneDrive backup](/onedrive-backup) - [SharePoint backup](/sharepoint-backup) - [Microsoft Teams data protection](/teams-backup) - Tasks and Microsoft Planner workloads This removes dependency on legacy impersonation models and aligns with Microsoft's long-term platform direction. ### Built for Operational Resilience Loop Backup is designed to handle: - Microsoft Graph throttling - Temporary API failures - Retry operations - Resume-from-checkpoint processing - Large-scale Microsoft 365 environments Rather than failing backup jobs entirely, workloads pause and resume safely while maintaining backup consistency. This becomes increasingly important as Microsoft shifts more workloads onto Graph-only APIs. ### Remaining Migration Work Some Microsoft 365 edge-case workloads across the wider industry still require transition planning. Loop Backup is actively completing migration work ahead of Microsoft's October 2026 enforcement deadlines, including: - Group mailbox handling - Recoverable Items processing - Extended retention workflows - Online Archive roadmap alignment The goal is a seamless customer transition with no disruption to backup operations. ## What Loop Backup Customers Need to Do For existing Loop Backup customers: **No action is required.** Loop Backup will continue operating normally throughout Microsoft's EWS retirement process. Customers do not need to: - Configure AppID AllowLists - Change authentication methods - Reconfigure backup jobs - Modify Microsoft 365 permissions manually All migration work is being handled behind the scenes. ## Final Thoughts EWS retirement is no longer a future problem. The shutdown process begins in 2026, with full removal in April 2027. Businesses should now: - Inventory all EWS-dependent applications - Review backup and compliance vendors - Confirm Microsoft Graph readiness - Plan around known Graph limitations - Remove unsupported legacy tooling Most importantly, organisations should ensure their backup provider has a real migration strategy already underway. Modern Microsoft 365 protection requires modern APIs. **Loop Backup is already prepared.** Explore [Microsoft 365 backup](/microsoft-365-backup) or [start a free trial](/pricing) today.