Business Events with Service Bus Endpoint do not send the session id in the BrokeredMessage.Header. When the Service Bus Queue or Subscription require a sessionid, this results in the message getting lost or going to the dead letter queue directly.
It is very import therefore that for these kinds of endpoints, it should be possible to send the sessionid.
The SessionId is very important because it is a way how we can make sure events in the same session are picked up sequentially by Azure Functions and not in parallel.
In the past I had developed an extension on how we can add this manually using the user's session id, and this was very helpful. Documentation here:
However, as of recently - 10.0.21 upwards, although this extension has stopped working in Tier 2 environments that are connected to PowerApps. It still works on Tier 1 and on Tier 2 environments without the connection to PowerApps.
I have contact Microsoft and was notified by the engineers who own the Dataverse logic to send to Service bus that there is currently no support for modifying the direct properties of the BrokeredMessage in Dataverse, so there is no mitigation/workaround.
My idea is to either have the possibility at Endpoint level to enable session id, or to reenable the logic to be able to modify the direct properties of the brokered message.