Azure naming · Microsoft.EventHub/namespaces

evhns Event Hubs namespace

Event Hubs namespace (<name>.servicebus.windows.net).

Naming constraints

CAF abbreviationevhns
Resource typeMicrosoft.EventHub/namespaces
Length6–50 characters
CaseMixed case
Allowed charactersAlphanumerics and hyphens. Start with a letter; end with a letter or number.
Uniqueness Global
SeparatorHyphen
Watch out: Shares the servicebus.windows.net DNS space with Service Bus, so the two can't use the same 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
evhns-app-prod-weu-001 Valid
Validation regex for CI checks or pre-commit hooks (.NET and JavaScript)
^(?=.{6,50}$)[A-Za-z][A-Za-z0-9-]*[A-Za-z0-9]$
Bicep naming expression
var name = take('evhns-${workload}-${env}-${region}-${instance}', 50)
Terraform local
locals {
  name = substr(join("-", compact(["evhns", var.workload, var.env, var.region, var.instance])), 0, 50)
}

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

Uniqueness scope

Globally unique across all of Azure — the name backs a public DNS label, so a clash with any other tenant's resource fails the deployment. Build in enough entropy (org/region/instance) to avoid collisions.

Open in the name generator