The documentation you are viewing is for Dapr v1.7 which is an older version of Dapr. For up-to-date documentation, see the latest version.

Azure SignalR binding spec

Detailed documentation on the Azure SignalR binding component

Component format

To setup Azure SignalR binding create a component of type See this guide on how to create and apply a binding configuration.

kind: Component
  name: <NAME>
  namespace: <NAMESPACE>
  version: v1
  - name: connectionString
    value: Endpoint=https://<your-azure-signalr>;AccessKey=<your-access-key>;Version=1.0;
  - name: hub  # Optional
    value: <hub name>

Spec metadata fields

Field Required Binding support Details Example
connectionString Y Output The Azure SignalR connection string "Endpoint=https://<your-azure-signalr>;AccessKey=<your-access-key>;Version=1.0;"
hub N Output Defines the hub in which the message will be send. The hub can be dynamically defined as a metadata value when publishing to an output binding (key is “hub”) "myhub"

Binding support

This component supports output binding with the following operations:

  • create

Additional information

By default the Azure SignalR output binding will broadcast messages to all connected users. To narrow the audience there are two options, both configurable in the Metadata property of the message:

  • group: Sends the message to a specific Azure SignalR group
  • user: Sends the message to a specific Azure SignalR user

Applications publishing to an Azure SignalR output binding should send a message with the following contract:

    "data": {
        "Target": "<enter message name>",
        "Arguments": [
                "sender": "dapr",
                "text": "Message from dapr output binding"
    "metadata": {
        "group": "chat123"
    "operation": "create"

For more information on integration Azure SignalR into a solution check the documentation