Microsoft has confirmed that all SharePoint Remote Event Receivers will be fully retired by July 1, 2027.
If you’re on Azure ACS-based RERs, that clock already ran out; they stopped functioning correctly on April 2, 2026.
This retirement is happening in two phases:
✅ Phase 1 (Completed): Azure ACS-registered RERs stopped functioning correctly on April 2, 2026, as part of the Azure ACS retirement.
⏳ Phase 2 (July 1, 2027): RERs registered via Microsoft Entra ID applications also stop firing. After that, no Remote Event Receivers will work, and Microsoft has confirmed there won’t be an extension.
Many SharePoint customizations still rely on RERs to trigger workflows, integrations, and event-driven business processes. Organizations that don’t migrate before the deadline risk breaking these solutions once event notifications stop.
Microsoft recommends replacing RERs with SharePoint webhooks or Microsoft Graph change notifications.
One important architectural difference is that RERs support synchronous event processing, which allows solutions to validate, block, or cancel actions before they’re completed. In contrast, SharePoint webhooks and Graph change notifications are asynchronous by design; they notify after an event occurs. Solutions built around synchronous processing will likely require a redesign rather than a simple migration.
Another challenge is identifying affected solutions. Microsoft doesn’t currently provide a tenant-wide discovery capability for Remote Event Receivers, so organizations must manually review in-house customizations and work with third-party vendors to determine whether their SharePoint integrations depend on RERs.
Rather than treating this as a last-minute migration, identify dependencies, assess the impact, and create a modernization plan for affected solutions soon.