Integration sbns

Service Bus namespace naming convention

The CAF abbreviation for Service Bus namespace is sbns. 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	sbns
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	sbns-{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	`sbns-payments-prod-eus-001`	26/50
Web app, development	`sbns-webapp-dev-weu-002`	23/50
Analytics with company prefix	`sbns-contoso-analytics-stage-uks-001`	36/50

Naming in Terraform and Bicep

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

Terraform

locals {
  service_bus_namespace_name = "sbns-${var.workload}-${var.environment}-${var.region}-001"
}

Bicep

var serviceBusNamespaceName = 'sbns-${workload}-${environment}-${region}-001'

Generate Service Bus namespace names for your workload

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

Open in the generator →

Related Integration resources

apim API Management service ia Integration account logic Logic app sbq Service Bus queue sbt Service Bus topic sbts Service Bus topic subscription

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