We have configured our IoT Hub to route deviceLifecycleEvents messages to the builtin IoT Hub "events" endpoint. We have also configured an EventHubTrigger function app to listen for events from that route.
When using "cardinality":"one", the deviceLifecycleEvent properties object does not contain an 'opType' to identify whether the deviceLifecycleEvent is a deleteDeviceIdentity or createDeviceIdentity.
context.bindingData.properties with "cardinality":"one"
We have configured our IoT Hub to route deviceLifecycleEvents messages to the builtin IoT Hub "events" endpoint. We have also configured an EventHubTrigger function app to listen for events from that route.
function.json
When "cardinality":"one" is set in the function.json, the deviceLifecycleEvent received by the function shows incorrect properties object:
context.bindingData for deviceLifecycleEvent when "cardinality":"one"
When using "cardinality":"one", the deviceLifecycleEvent properties object does not contain an 'opType' to identify whether the deviceLifecycleEvent is a deleteDeviceIdentity or createDeviceIdentity.
context.bindingData.properties with "cardinality":"one"
When "cardinality":"many" is set in the function.json, the deviceLifecycleEvent contains correct properties->opType information:
function.json with "cardinality":"many"
deviceLifecycleEvent context.bindingData with "cardinality":"many"
context.bindingData.properties with "cardinality":"many"