VPN connection naming convention

The CAF abbreviation for VPN connection is vcn. 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

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 Security resources

Key Vault has its own guide covering its strict 24 character global uniqueness and soft delete name reservation. Managed identities are cheap to create and usually provisioned per app or per function rather than shared, so unlike most of this list, their naming should tie tightly to the specific workload they are attached to.

VPN Gateway and Bastion resources are typically one per hub or region rather than one per environment, name them for the network boundary they protect. The common mistake is naming managed identities generically, id-prod for example, when dozens end up in the same subscription and it becomes impossible to tell which resource an identity actually belongs to.

Example names

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

Naming in Terraform and Bicep

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

locals {
  vpn_connection_name = "vcn-${var.workload}-${var.environment}-${var.region}-001"
}

var vpnConnectionName = 'vcn-${workload}-${environment}-${region}-001'

Related Security resources

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