Not clear if sessions are supported for Azure Service Bus Queues as a pub/sub broker.
- Dominant language
- SCSS
- Stars
- 1k
- Forks
- 794
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 7
Description
**What content needs to be created or modified?**
Session support for Azure Service Bus Queues as a pub/sub broker is not clear.
For the Azure Service Bus Topics section, there is a section explaining how to [Subscribe to a session enabled topic](https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-azure-servicebus-topics/#subscribe-to-a-session-enabled-topic), along with a reference to the `SessionId` as a valid metadata property ([Sending a message with metadata](https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-azure-servicebus-topics/#sending-a-message-with-metadata)).
For the Azure Service Queues section, there is a matching reference to the `SessionId` as a valid metadata property ([Sending a message with metadata](https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-azure-servicebus-topics/#sending-a-message-with-metadata)), but no corresponding subsequent section about how to subscribe to a session enabled queue.
**Describe the solution you'd like**
Explicitly indicate if sessions are supported with Azure Service Bus Queues as a pub/sub broker. If supported, provide clear instructions on how to enable sessions, similar to the corresponding section for Azure Service Bus Topics ([Subscribe to a session enabled topic](https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-azure-servicebus-topics/#subscribe-to-a-session-enabled-topic)). If not, explicitly state the lack of support.
**Where should the new material be placed?**
If sessions are supported, the section on how to enable it should be placed after [Sending a message with metadata](https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-azure-servicebus-topics/#sending-a-message-with-metadata) section.
If not supported, a note should be added indicating the lack of support.
**The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos**
**Additional context**
Contributor guide
Assessment
This issue has not been assessed yet.