The properly from the SPItem Event Receiver class is The above class, I made it as sealed to avoid exceptions on the MSOCAF report generation. As long as the Scope is active, no other events will get triggered.(MSOCAF – Microsoft Share Point Online Code Analysis Framework). Note: This will cause the Event Firing disabled on the Site Collection Level.The address for the remote event receiver currently uses the same address that hosts the add-in Installed remote event receiver by using the host address.This is done to facilitate easy debugging using Windows Azure Service Bus.This scenario shows how an add-in can use the add-in Installed event to perform additional work in the host web, such as attaching event receivers to lists in the host web.
The solution is a provider-hosted add-in (remote event receivers are not supported with Share Point-hosted apps).Edit Form Scenario: The Item Updating event worked without a hitch.I was able to grab and work with all values coming from the property bag. public override void Item Updating(SPItem Event Properties properties) Datasheet Scenario: Running the same code, the Item Updating event would cause errors in the Datasheet view and forces the user to discard their changes.Visit the video on Channel 9 - Point-Host-Webs-Office-365-Develo Important As of January 2017 Share Point Online does support list webhooks which you can use instead of "-ed" remote event receivers.Checkout Overview of Share Point webhooks to learn more about webhooks.