It would be great if you can define Create/Update/Delete actions from Event Processing. So depending of a field you can say i.e. "if this is field contains "delete" it's a delete operation, use the ...
THANKS @Uri for the feedback. This is an interesting approach but it would require that you keep the full history of data in the KQL DB which is probably not the best idea, considering large volumes of data and the availability of standard SQL endpoints etc., a warehouse/lakehouse based approach might make more sense. But anyway, a step in the right direction :-)
