Microsoft Purview instance naming convention

The CAF abbreviation for Microsoft Purview instance is pview. Names can be 3 to 63 characters long and allow alphanumerics and hyphens. The name must be globally unique across all of Azure.

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 Management and governance resources

Subscriptions and management groups sit at the top of this category and have their own guide covering immutable IDs versus display names. Resource groups are the single most created resource in Azure and the one place teams disagree most, workload first or type first, prefix or suffix, consistency matters far more than which specific order you settle on, which is also why this site lets you reorder the pattern rather than force one.

Log Analytics workspaces and Application Insights are usually centralized per environment rather than created per app, so name them for the environment or platform boundary they observe. The common mistake is spinning up a separate Log Analytics workspace per app, which prevents the cross service log correlation that a shared workspace exists to provide in the first place.

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

var purviewName = 'pview-${workload}-${environment}-${region}-001'

Related Management and governance resources

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