Skip to main content

Azure Storage Queues

The Azure Storage Queues Transport is used to communicate to Azure Storage Queues. It is suitable for development, testing, and production environments.

Configuration​

To use the Azure Storage Queues Transport, define it under transports and reference it as current-transport.

Example​

current-transport: local-azure-service-bus

transports:
  - name: local-azure-service-bus
    azure-storage-queues-transport-config:
      connection-string: Endpoint=amqp://127.0.0.1:32799/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true

azure-storage-queues-transport-config Fields​

FieldRequiredTypeDefaultDescription
connection-stringYesstring—Connection string to Azure Storage Queues.

Field Details​

connection-string (required)​

A standard conection string for Azure Storage Queues.

Examples:

connection-string: UseDevelopmentStorage=true

Limitations​

Timeout Send Not Supported​

The timeout send command is not supported with the Azure Storage Queues transport. Native delayed delivery is disabled in busly's transport configuration because it requires an in-process background poller (NativeDelayedDeliveryProcessor) to forward due messages from an Azure Table to the destination queue. Because busly exits immediately after dispatching a message, the poller is stopped before it can forward the deferred message. Enabling native delayed delivery for send-only endpoints also requires a dedicated poison queue and would still not resolve the fundamental timing incompatibility.