Skip to content
Networking snet

Virtual network subnet naming convention

The CAF abbreviation for Virtual network subnet is snet. Names can be 1 to 80 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the parent resource.

Naming rules

CAF abbreviation snet
Length 1 to 80 characters
Allowed characters Alphanumerics (a-z, A-Z, 0-9), hyphens, underscores
Scope of uniqueness Unique within the parent resource
CAF pattern snet-{workload}-{environment}-{region}-{instance}

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.

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 snet-payments-prod-eus-001 26/80
Web app, development snet-webapp-dev-weu-002 23/80
Analytics with company prefix snet-contoso-analytics-stage-uks-001 36/80

Naming in Terraform and Bicep

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

Terraform
locals {
  subnet_name = "snet-${var.workload}-${var.environment}-${var.region}-001"
}
Bicep
var subnetName = 'snet-${workload}-${environment}-${region}-001'

Generate Virtual network subnet names for your workload

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

Open in the generator →

Related Networking resources

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