Logic app naming convention

The CAF abbreviation for Logic app is logic. Names can be 1 to 43 characters long and allow alphanumerics, hyphens and underscores. The name must be unique within the resource group.

Naming rules

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.

Naming Integration resources

Service Bus, Logic Apps, and API Management each have a dedicated guide covering their own two layer pattern, a globally unique namespace or service, with relaxed, scoped children inside. Integration accounts are the piece that does not get its own guide, they pair with Logic Apps for B2B and EDI scenarios and are usually shared across every logic app in an integration domain rather than created one per workflow.

The common mistake is provisioning a new integration account per logic app instead of sharing one per integration boundary, which fragments the partner agreements and schemas an integration account exists to reuse across workflows.

Example names

Generated by the same engine as the name generator, so length and character rules are already applied.

Naming in Terraform and Bicep

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

locals {
  logic_app_name = "logic-${var.workload}-${var.environment}-${var.region}-001"
}

var logicAppName = 'logic-${workload}-${environment}-${region}-001'

Related Integration resources

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