Analytics and IoT evh

Event hub naming convention

The CAF abbreviation for Event hub is evh. Names can be 1 to 256 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the parent resource.

Naming rules

CAF abbreviation	evh
Length	1 to 256 characters
Allowed characters	Alphanumerics (a-z, A-Z, 0-9), hyphens, underscores
Scope of uniqueness	Unique within the parent resource
CAF pattern	evh-{workload}-{environment}-{region}-{instance}

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	`evh-payments-prod-eus-001`	25/256
Web app, development	`evh-webapp-dev-weu-002`	22/256
Analytics with company prefix	`evh-contoso-analytics-stage-uks-001`	35/256

Naming in Terraform and Bicep

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

Terraform

locals {
  eventhub_name = "evh-${var.workload}-${var.environment}-${var.region}-001"
}

Bicep

var eventhubName = 'evh-${workload}-${environment}-${region}-001'

Generate Event hub names for your workload

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

Open in the generator →

Related Analytics and IoT resources

as Azure Analysis Services server dbac Azure Databricks Access Connector dbw Azure Databricks workspace dec Azure Data Explorer cluster dedb Azure Data Explorer cluster database adf Azure Data Factory dt Azure Digital Twin instance asa Azure Stream Analytics

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