Management and governance pview

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

CAF abbreviation	pview
Length	3 to 63 characters
Allowed characters	Alphanumerics (a-z, A-Z, 0-9), hyphens
Scope of uniqueness	Global (must be unique across all of Azure)
CAF pattern	pview-{workload}-{environment}-{region}-{instance}

Worth knowing: Globally unique name.

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	`pview-payments-prod-eus-001`	27/63
Web app, development	`pview-webapp-dev-weu-002`	24/63
Analytics with company prefix	`pview-contoso-analytics-stage-uks-001`	37/63

Naming in Terraform and Bicep

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

Terraform

locals {
  purview_name = "pview-${var.workload}-${var.environment}-${var.region}-001"
}

Bicep

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

Generate Microsoft Purview instance names for your workload

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

Open in the generator →

Related Management and governance resources

aa Automation account policy Azure Policy definition appi Application Insights ag Azure Monitor action group dcr Azure Monitor data collection rule apr Azure Monitor alert processing rule dce Data collection endpoint script Deployment script

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