Compute and web ntfns

Notification Hubs namespace naming convention

The CAF abbreviation for Notification Hubs namespace is ntfns. Names can be 6 to 50 characters long and allow alphanumerics and hyphens. The name must be globally unique across all of Azure.

Naming rules

CAF abbreviation	ntfns
Length	6 to 50 characters
Allowed characters	Alphanumerics (a-z, A-Z, 0-9), hyphens
Scope of uniqueness	Global (must be unique across all of Azure)
CAF pattern	ntfns-{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	`ntfns-payments-prod-eus-001`	27/50
Web app, development	`ntfns-webapp-dev-weu-002`	24/50
Analytics with company prefix	`ntfns-contoso-analytics-stage-uks-001`	37/50

Naming in Terraform and Bicep

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

Terraform

locals {
  notification_hub_namespace_name = "ntfns-${var.workload}-${var.environment}-${var.region}-001"
}

Bicep

var notificationHubNamespaceName = 'ntfns-${workload}-${environment}-${region}-001'

Generate Notification Hubs namespace names for your workload

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

Open in the generator →

Related Compute and web resources

ase App Service environment asp App Service plan lt Azure Load Testing instance avail Availability set arcs Azure Arc enabled server arck Azure Arc enabled Kubernetes cluster pls Azure Arc private link scope arcgw Azure Arc gateway

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