Azure Service Bus integration

Configure a queue or topic

Use an existing public Azure Service Bus namespace and queue or topic. Enter the namespace without its domain and the entity name without a path. Create an entity-scoped SAS authorization policy with Send permission only; configure its policy name and primary or secondary key. Do not use RootManageSharedAccessKey.

The adapter creates a short-lived SAS token for each request and sends HTTPS POST /ENTITY/messages. BrokerProperties carries MessageId=delivery UUID, CorrelationId=event UUID and JSON content type. A 201 response is provider acceptance, not subscriber processing. REST is used to retain the shared DNS-pinned HTTPS boundary; AMQP SDK, sessions, scheduled messages, managed identity and Entra authentication are not implemented.

Verification and rotation

A send-only policy cannot safely inspect entity configuration, so basic verification validates configuration only. Explicit test-send proves the service accepted a synthetic event. Rotate through the alternate SAS key: replace Struct credentials, verify, then retire the old key. Existing queued jobs use replacement credentials. Azure recommends Entra identities when available; this initial adapter requires SAS and cannot connect to namespaces with SAS disabled.

Troubleshooting

HTTP 401/403 requires checking policy scope, key, namespace and clock synchronization. HTTP 404 indicates entity/namespace configuration. HTTP 429 and 5xx retry. No internal/private namespace connectivity is available. Message size is conservatively bounded by Struct’s 240000-byte transformed output limit; provider-tier limits still apply.