Azure naming · Microsoft.OperationalInsights/workspaces

log Log Analytics workspace

Log Analytics workspace for Azure Monitor logs.

Naming constraints

CAF abbreviationlog
Resource typeMicrosoft.OperationalInsights/workspaces
Length4–63 characters
CaseMixed case
Allowed charactersAlphanumerics and hyphens. Start and end with alphanumeric.
Uniqueness Resource group
SeparatorHyphen
Watch out: Defender for Cloud and other services can create DefaultWorkspace-<subscription>-<region> in DefaultResourceGroup-<region>.

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
log-app-prod-weu-001 Valid
Validation regex for CI checks or pre-commit hooks (.NET and JavaScript)
^(?=.{4,63}$)[A-Za-z0-9][A-Za-z0-9-]*[A-Za-z0-9]$
Bicep naming expression
var name = take('log-${workload}-${env}-${region}-${instance}', 63)
Terraform local
locals {
  name = substr(join("-", compact(["log", var.workload, var.env, var.region, var.instance])), 0, 63)
}

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

Uniqueness scope

Unique within the parent resource group. The same name can be reused in a different resource group.

Open in the name generator