Azure Resource
Name Parser

How the parser works

Microsoft's Cloud Adoption Framework defines a fixed component order for resource names: type-company-department-workload-environment-region-instance. Because the order is predictable, the parser anchors on the parts it can recognise with certainty, the leading resource-type abbreviation, and the trailing environment, region, and instance, then infers the free-text middle (workload, and optionally company and department).

Limitations

• Company / department / workload can't always be told apart, they're free text with no fixed values, so the parser labels them by position.
• Names without hyphens (like storage accounts) are harder to split, since there are no delimiters between components. The parser does its best and flags lower confidence.
• Region abbreviations follow the common community convention, Microsoft's CAF doesn't publish official ones.
• Custom component orders aren't auto-detected. The parser assumes the standard CAF order (type first), so names built with a reordered convention may be labeled by the wrong position.

Need to go the other way? Use the name generator to build CAF compliant names from scratch.