Integration sbts

Service Bus topic subscription naming convention

The CAF abbreviation for Service Bus topic subscription is sbts. Names can be 1 to 50 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the parent resource.

Naming rules

CAF abbreviation	sbts
Length	1 to 50 characters
Allowed characters	Alphanumerics (a-z, A-Z, 0-9), hyphens, underscores
Scope of uniqueness	Unique within the parent resource
CAF pattern	sbts-{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	`sbts-payments-prod-eus-001`	26/50
Web app, development	`sbts-webapp-dev-weu-002`	23/50
Analytics with company prefix	`sbts-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_topic_sub_name = "sbts-${var.workload}-${var.environment}-${var.region}-001"
}

Bicep

var serviceBusTopicSubName = 'sbts-${workload}-${environment}-${region}-001'

Generate Service Bus topic subscription 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 sbns Service Bus namespace sbq Service Bus queue sbt Service Bus topic

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