Azure naming · Microsoft.Search/searchServices

srch AI Search

Azure AI Search service (<name>.search.windows.net).

Naming constraints

CAF abbreviationsrch
Resource typeMicrosoft.Search/searchServices
Length2–60 characters
CaseLowercase only
Allowed charactersLowercase letters, numbers, and hyphens. Can't start or end with a hyphen; no consecutive hyphens.
Uniqueness Global
SeparatorHyphen

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

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

« Resource group Azure OpenAI »

Uniqueness scope

Globally unique across all of Azure — the name backs a public DNS label, so a clash with any other tenant's resource fails the deployment. Build in enough entropy (org/region/instance) to avoid collisions.

Open in the name generator

More in AI & data

All resource types