Skip to content

Use an SLA for SignalR Services#

Reliability · SignalR Service · 2022_03

Use SKUs that include an SLA when configuring SignalR Services.

Description#

When choosing a SKU for a SignalR Service you should consider the SLA that is included in the SKU. SignalR Services offer a range of SKU offerings:

  • Free - Are designed for early non-production use and do not include any SLA.
  • Standard - Are designed for production use and include an SLA.
  • Premium - Are designed for production use and include an SLA. Additional, Premium SKUs support increased resilience with Availablity Zones.

Recommendation#

Consider using a Standard or Premium SKU that includes an SLA.

Examples#

Configure with Azure template#

To deploy services that pass this rule:

  • Set sku.name to Standard_S1 or Premium_P1.

For example:

{
    "type": "Microsoft.SignalRService/signalR",
    "apiVersion": "2021-10-01",
    "name": "[parameters('name')]",
    "location": "[parameters('location')]",
    "kind": "SignalR",
    "sku": {
        "name": "Standard_S1"
    },
    "identity": {
        "type": "SystemAssigned"
    },
    "properties": {
        "disableLocalAuth": true,
        "features": [
            {
                "flag": "ServiceMode",
                "value": "Serverless"
            }
        ]
    }
}

Configure with Bicep#

To deploy services that pass this rule:

  • Set sku.name to Standard_S1 or Premium_P1.

For example:

resource service 'Microsoft.SignalRService/signalR@2021-10-01' = {
  name: name
  location: location
  kind: 'SignalR'
  sku: {
    name: 'Standard_S1'
  }
  identity: {
    type: 'SystemAssigned'
  }
  properties: {
    disableLocalAuth: true
    features: [
      {
        flag: 'ServiceMode'
        value: 'Serverless'
      }
    ]
  }
}

Last update: 2022-03-17