synw Synapse workspaceAzure Synapse Analytics workspace.
| CAF abbreviation | synw |
| Resource type | Microsoft.Synapse/workspaces |
| Length | 1–50 characters |
| Case | Lowercase only |
| Allowed characters | Lowercase letters, numbers, and hyphens. Start and end with a letter or number; can't contain '-ondemand'. |
| 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.
synw-app-prod-weu-001
Valid
^(?!.*-ondemand)(?=.{1,50}$)[a-z0-9](?:[a-z0-9-]*[a-z0-9])?$
var name = take(toLower('synw-${workload}-${env}-${region}-${instance}'), 50)
locals {
name = substr(lower(join("-", compact(["synw", var.workload, var.env, var.region, var.instance]))), 0, 50)
}
Azure Policy can't evaluate regular expressions, so a policy can check the synw 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