Tendrl

Docs / Contact / connectors/azure-queue

Azure Storage Queue

Provider: azure | Service: queue | Direction: Write

Azure Storage Queue connector for sending messages to a storage queue.

Required Permissions

If using a connection string (api_key auth), the Shared Access Signature must allow queue add/process operations. For role auth, the Contact service principal needs the Storage Queue Data Message Sender role.

Operation

When a message reaches this connector, it targets the queue named in the payload:

Payload field Required Description
queueName Yes Target storage queue name
message Yes Message body to enqueue

Connector Configuration

The connector is created with type: "cloud", provider: "azure", service_type: "queue", plus:

Field (config) Required Description
auth_type No api_key (default) or role. See below.
queue_conn_str Conditional Storage queue connection string (use ${secrets.azure_queue_conn}). Required when auth_type is api_key.
account_name Conditional Storage account name. Required when auth_type is role.
Role-based (cross-tenant) authentication

Set auth_type: "role" to authenticate as the Contact Azure AD application registered in your tenant. Provide tenant_id (required) and account_name; no connection string is needed.

Output

json

{
  "status": "completed",
  "data": {
    "status": "queued",
    "queueName": "device-events",
    "messageId": "5ca5e334-7e4e-4c4d-9c1f-8d6f0a1b2c3d"
  }
}

Example

Connector config (connection string):

json

{
  "type": "cloud",
  "provider": "azure",
  "service_type": "queue",
  "queue_conn_str": "${secrets.azure_queue_conn}"
}

Connector config (cross-tenant role):

json

{
  "type": "cloud",
  "provider": "azure",
  "service_type": "queue",
  "auth_type": "role",
  "tenant_id": "00000000-0000-0000-0000-000000000000",
  "account_name": "mystorageaccount"
}

← Back to Contact docs