sigr SignalRAzure SignalR Service (<name>.service.signalr.net).
| CAF abbreviation | sigr |
| Resource type | Microsoft.SignalRService/signalR |
| Length | 3–63 characters |
| Case | Mixed case |
| Allowed characters | Alphanumerics and hyphens. Start with a letter; end with a letter or number. |
| Uniqueness | Global |
| Separator | Hyphen |
Source: Microsoft Learn, “Naming rules and restrictions for Azure resources”, checked October 2026. Abbreviation from the Cloud Adoption Framework.
A worked name for workload app, env prod, region weu, instance 001.
sigr-app-prod-weu-001
Valid
^(?=.{3,63}$)[A-Za-z][A-Za-z0-9-]*[A-Za-z0-9]$var name = take('sigr-${workload}-${env}-${region}-${instance}', 63)locals {
name = substr(join("-", compact(["sigr", var.workload, var.env, var.region, var.instance])), 0, 63)
}Azure Policy can't evaluate regular expressions, so a policy can check the sigr prefix but not the full format. Run the regex in your pipeline, or audit existing names on a schedule.
Globally unique across all of Azure — the name backs a public DNS label, so a clash with any other tenant's resource fails the deployment. Build in enough entropy (org/region/instance) to avoid collisions.
Open in the name generator