Virtual desktop application group naming convention

The CAF abbreviation for Virtual desktop application group is vdag. Names can be 3 to 64 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the resource group.

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 Virtual desktop infrastructure resources

Azure Virtual Desktop resources, host pools, application groups, workspaces, and scaling plans, are usually organized around the population of users they serve rather than the prod or dev split used almost everywhere else in Azure, since AVD is structured around who uses the desktops, not a deployment pipeline.

A workspace groups several application groups the way a Front Door groups endpoints, name it for the audience or department it serves, finance-users or developers, rather than for an environment tier. The common mistake is applying a generic prod and dev scheme here when the dimension that actually distinguishes these resources is the user population, not the release stage.

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 {
  avd_application_group_name = "vdag-${var.workload}-${var.environment}-${var.region}-001"
}

var avdApplicationGroupName = 'vdag-${workload}-${environment}-${region}-001'

Related Virtual desktop infrastructure resources

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