Azure naming · Microsoft.Network/privateEndpoints

pep Private endpoint

A private IP in your VNet for a PaaS service.

Naming constraints

CAF abbreviationpep
Resource typeMicrosoft.Network/privateEndpoints
Length2–64 characters
CaseMixed case
Allowed charactersAlphanumerics, underscores, periods, and hyphens. Start with alphanumeric; end with alphanumeric or underscore.
Uniqueness Resource group
SeparatorHyphen
Watch out: Each private endpoint also creates a NIC (<endpoint>.nic.<guid>) unless you set a custom NIC name.

Source: Microsoft Learn, “Naming rules and restrictions for Azure resources”, checked October 2026. Abbreviation from the Cloud Adoption Framework.

Example & copy-ready

A worked name for workload app, env prod, region weu, instance 001.

Example name
pep-app-prod-weu-001 Valid
Validation regex for CI checks or pre-commit hooks (.NET and JavaScript)
^(?=.{2,64}$)[A-Za-z0-9][A-Za-z0-9_.-]*[A-Za-z0-9_]$
Bicep naming expression
var name = take('pep-${workload}-${env}-${region}-${instance}', 64)
Terraform local
locals {
  name = substr(join("-", compact(["pep", var.workload, var.env, var.region, var.instance])), 0, 64)
}

Azure Policy can't evaluate regular expressions, so a policy can check the pep prefix but not the full format. Run the regex in your pipeline, or audit existing names on a schedule.

Uniqueness scope

Unique within the parent resource group. The same name can be reused in a different resource group.

Open in the name generator