SharePoint Server SE will start blocking orphaned Remote Event Receivers

If you use custom solutions with Remote Event Receivers on SharePoint Server Subscription Edition, check how they are registered. Starting with the March 2027 CU, SharePoint will block receivers that were registered without an application identity. Microsoft originally planned to start blocking them in November 2026 and gives the revised date in KB5002945.

Which solutions are affected?

A Remote Event Receiver (RER) lets SharePoint call a service outside the farm when an event occurs, for example when an item is added, updated, or deleted. An orphaned receiver in this context is one registered without an application identity. Even if the service is available and works today, SharePoint can stop calling the receiver after the update. Checking service availability alone is therefore insufficient to determine the impact. Microsoft Support, KB5002945 · Microsoft Learn, using Remote Event Receivers

A typical example is a library that fills in metadata from an external system after a document is uploaded. If the receiver for that event was registered without an application identity, users can still upload documents, but the metadata will no longer be filled in. When testing, verify the result the receiver is supposed to produce as well.

How to find affected registrations

Run Get-SPOrphanedRemoteEventReceiver in the SharePoint Management Shell. Microsoft lists this cmdlet for finding orphaned registrations at the list level. Even if it returns no results, check solutions that register receivers at other scopes, such as the web level. Microsoft Support, KB5002945 · Microsoft Learn, registering receivers on the host web

For each result, record the list or library, event type, target URL, and solution owner.

What to check before installing the March CU

  1. Find out which receivers are still in use. Confirm with the solution owner what each receiver does and which lists or libraries use it. Use that information to decide which registrations need to be fixed and which can be removed once you have verified they are no longer needed.
  2. Update the deployment process as well. For receivers still in use, make sure they are registered in an application context and update the installation procedure accordingly. Review the installation and configuration scripts too. If you fix the registration only in the existing library, the original script can recreate the same problem when you deploy the solution to another site. For custom solutions running on an on-premises farm, Microsoft documents how to register a receiver in a provider-hosted SharePoint Add-in and how to configure trust for a high-trust add-in. Microsoft Learn, creating a receiver in a SharePoint Add-in · Microsoft Learn, high-trust SharePoint Add-ins
  3. Test the full scenario in a test farm. After deploying the fix, repeat the action using a regular user account and verify the result in the downstream service as well. Once the March CU is available, repeat the same test on the updated farm before deploying the CU to production.