ChangeIntelIT change radar
Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 14:26 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC1411726 Plan for changeMajor changeUser impactAdmin impactRetirement

Remote Event Receivers in SharePoint Online will be retired

SharePoint OnlineMicrosoft 365 admin center

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Action date

Microsoft tags this a retirement but gives no action date in the notice metadata. Any date is in the text below.

Microsoft's start date
1 Jul 2026
Last changed by Microsoft
1 Jul 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and Why

Microsoft is retiring Remote Event Receivers (RERs) in SharePoint Online as part of the Azure ACS retirement and ongoing modernization of the SharePoint extensibility platform. Remote Event Receivers registered using Azure ACS stopped functioning correctly on April 2, 2026. Remote Event Receivers registered using Microsoft Entra applications will continue to function until July 1, 2027, after which all Remote Event Receivers will stop working. Microsoft recommends migrating affected solutions to SharePoint webhooks or Microsoft Graph change notifications.

Rollout Schedule

  • April 2, 2026: Azure ACS-registered Remote Event Receivers stopped functioning correctly.
  • July 1, 2027: All remote event receivers, including those registered using a Microsoft Entra application, will stop working. No RER will fire events after this date.

Impact on Your Organization

Who is affected

  • Organizations using SharePoint Online Remote Event Receivers.
  • Developers, solution owners, and third-party vendors supporting SharePoint customizations.

Platforms/Services

  • SharePoint Online
  • Microsoft Entra ID applications
  • SharePoint Add-ins
  • SharePoint webhooks
  • Microsoft Graph change notifications

What will happen

  • Azure ACS-based Remote Event Receivers have already stopped functioning correctly.
  • All remaining Remote Event Receivers will stop firing events after July 1, 2027.
  • Applications and workflows that depend on Remote Event Receivers will no longer receive SharePoint event notifications.
  • Business processes that rely on those events may stop working unless migrated.
  • SharePoint webhooks and Microsoft Graph change notifications are the recommended replacement technologies.
  • SharePoint webhooks are asynchronous. Solutions that depend on synchronously blocking or cancelling actions will need to be redesigned.
  • There will not be an option to extend Remote Event Receivers beyond July 1, 2027.
  • Microsoft currently does not provide a tenant-wide method for administrators to discover Remote Event Receiver usage. We will update this Message Center post, and the associated developer blog post, as soon as a discovery capability is available.

Action Required / Recommendations

  • Identify any in-house applications or solutions that use Remote Event Receivers.
  • Work with developers to determine whether Remote Event Receivers are in use.
  • Contact third-party vendors to determine whether their solutions rely on Remote Event Receivers.
  • Request updated webhook-based versions of affected third-party solutions.
  • Plan migration to SharePoint webhooks or Microsoft Graph change notifications before July 1, 2027.
  • Review internal documentation and operational procedures that reference Remote Event Receivers.
  • Communicate this retirement to application owners, developers, support teams, and help desk personnel.
  • Monitor future Message Center updates for Microsoft’s planned Remote Event Receiver discovery capability.
  • Review Overview of SharePoint webhooks.
  • Review Microsoft Graph change notifications guidance.
  • Review the Azure ACS retirement FAQ.
  • Review guidance for using Remote Event Receivers without an Azure ACS dependency.
  • Review the SharePoint team retirement update blog.

Learn more

Compliance Considerations

AreaExplanation
Does the change alter how existing customer data is processed, stored, or accessed?Organizations migrating from Remote Event Receivers to SharePoint webhooks or Microsoft Graph change notifications may need to redesign how SharePoint event data is retrieved and processed.
Does the change modify, interrupt, or disable capabilities?Remote Event Receivers are being retired. Applications, workflows, and integrations that depend on them will stop receiving SharePoint events after July 1, 2027 unless migrated.
Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Microsoft currently does not provide a tenant-wide discovery capability for identifying Remote Event Receiver usage. Administrators must work with developers and solution vendors to assess exposure until a discovery capability becomes available.
Does the change add any integration to 3rd party software products?Organizations using third-party solutions built on Remote Event Receivers may require updated vendor versions that use supported technologies such as SharePoint webhooks or Microsoft Graph change notifications.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 14:26 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.