[BUG] Remote Event Receiver is not called when created with Add-PnPEventReceiver

[nils-a]

Reporting an Issue or Missing Feature

Remote Event Receiver web service is not called when created with Add-PnPEventReceiver and the event is happening.

Expected behavior

RER should call it's external url web service

Actual behavior

Nothing happens. It seems RER are simply not working, when they are added via Add-PnPEventReceiver

Steps to reproduce behavior

• create a simple endpoint
• publish via ngrok to have a public url
• Add-PnPEventReceiver -List [List] -Url [endpoint] -EventReceiverType ItemAdded -Synchronization Asynchronous -Name [Some Name]
• Add an item to the list

What is the version of the Cmdlet module you are running?

2.1.1

Which operating system/environment are you running PnP PowerShell on?

• Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

Additional information

#581 and #464 reported the same problem. Both have been closed without any solution.
I suggest that Add-PnPEventReceiver at least write out some warning that success of that operation is rather unlikely, to spare others from searching days long on what the problem might be.

[Tanddant]

The issue is that this has nothing to do with PnP PowerShell - adding a remote event receiver with CSOM doesn't work either when you're connected with an app registration.

ReRs are tied to a user Id (if you add a ReR with UseWebLogin it will work, but the second that user is closed the ReR stops firering.

What you can to is to connect using an App registration that you own, and register as an ACS app on the https://{tenant}-admin.sharepoint.com/_layouts/15/appinv.aspx page with the following permissions

<AppPermissionRequests AllowAppOnlyPolicy="true">
    <AppPermissionRequest Scope="http://sharepoint/content/tenant" 
     Right="FullControl" />
 </AppPermissionRequests>

Connect with PowerShell and that app, and you're off to the races.

This is super annoying, but it's simply due to Microsoft not updating ReRs anymore (they've been stated as being a legacy technology several times unfortunately)

[gautamdsheth]

Thanks @Tanddant , not much we can do from PnP PowerShell side of things.