Azure Service Bus output binding for Azure Functions is limited to message body

[ChuckJonas]

The way the service bus output bindings are implement seem to only support the message body... You can't set messageId, sessionId, applicationProperties, etc. This makes it useless almost any real world use cases.

Are there plans to properly implement this binding?

Found these related "User Voice" issues, but they are stale and have no comments addressing this issue:

https://feedback.azure.com/d365community/idea/eea36d62-f224-ec11-b6e6-000d3a4f0da0 https://feedback.azure.com/d365community/idea/df849c4f-f224-ec11-b6e6-000d3a4f0da0

[ramya894]

@ChuckJonas We will check this with our next level team and update you with the information.

[chrisaliotta]

I would love for this issue to get some attention. We use sessions with Azure Service Bus messaging and would like to use the attribute output binding functionality.

I'd like to propose that returning an object of type ServiceBusMessage with those attributes set would be one possible solution when considering how to implement this with output bindings.