Skip to content
Developer tools sigr

SignalR naming convention

The CAF abbreviation for SignalR is sigr. Names can be 3 to 63 characters long and allow alphanumerics and hyphens. The name must be globally unique across all of Azure.

Naming rules

CAF abbreviation sigr
Length 3 to 63 characters
Allowed characters Alphanumerics (a-z, A-Z, 0-9), hyphens
Scope of uniqueness Global (must be unique across all of Azure)
CAF pattern sigr-{workload}-{environment}-{region}-{instance}
Worth knowing: Globally unique name.

Rules follow Microsoft's resource naming rules and CAF abbreviations. Some resource types have extra start/end character restrictions, so verify against the official docs before locking in a convention.

Naming Developer tools resources

App Configuration stores, Maps accounts, SignalR, and Web PubSub each become their own DNS endpoint and are typically shared across several apps or services rather than owned by one, similar in spirit to a shared API Management instance. Name them for the platform or shared boundary they serve, not for whichever app happened to need them first.

The common mistake is naming a shared App Configuration store after its first consumer, then having to work around that name once a second, unrelated app depends on the same store. Naming for the boundary from day one avoids that rename.

Example names

Generated by the same engine as the name generator, so length and character rules are already applied.

Scenario Generated name Length
Payments API, production sigr-payments-prod-eus-001 26/63
Web app, development sigr-webapp-dev-weu-002 23/63
Analytics with company prefix sigr-contoso-analytics-stage-uks-001 36/63

Naming in Terraform and Bicep

Build the name from variables so one module produces the right name in every environment.

Terraform
locals {
  signalr_name = "sigr-${var.workload}-${var.environment}-${var.region}-001"
}
Bicep
var signalrName = 'sigr-${workload}-${environment}-${region}-001'

Generate SignalR names for your workload

Free, no login. Validation and Terraform, Bicep, or CSV export included.

Open in the generator →

Related Developer tools resources

See the full list of Azure resource naming rules or read the complete CAF naming guide.