--- type: docs title: "Azure Service Bus Queues binding spec" linkTitle: "Azure Service Bus Queues" description: "Detailed documentation on the Azure Service Bus Queues binding component" --- ## Setup Dapr component ```yaml apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: namespace: spec: type: bindings.azure.servicebusqueues version: v1 metadata: - name: connectionString value: "Endpoint=sb://************" - name: queueName value: queue1 - name: ttlInSeconds value: 60 ``` - `connectionString` is the Service Bus connection string. - `queueName` is the Service Bus queue name. - `ttlInSeconds` is an optional parameter to set the default message [time to live](https://docs.microsoft.com/azure/service-bus-messaging/message-expiration). If this parameter is omitted, messages will expire after 14 days. {{% alert title="Warning" color="warning" %}} The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described [here]({{< ref component-secrets.md >}}). {{% /alert %}} ## Specifying a time to live on message level Time to live can be defined on queue level (as illustrated above) or at the message level. The value defined at message level overwrites any value set at queue level. To set time to live at message level use the `metadata` section in the request body during the binding invocation. The field name is `ttlInSeconds`. Example: ```shell curl -X POST http://localhost:3500/v1.0/bindings/myServiceBusQueue \ -H "Content-Type: application/json" \ -d '{ "data": { "message": "Hi" }, "metadata": { "ttlInSeconds": "60" }, "operation": "create" }' ``` ## Output Binding Supported Operations * create ## Related links - [Bindings building block]({{< ref bindings >}}) - [How-To: Trigger application with input binding]({{< ref howto-triggers.md >}}) - [How-To: Use bindings to interface with external resources]({{< ref howto-bindings.md >}}) - [Bindings API reference]({{< ref bindings_api.md >}})