azure-naming-convention

Generate CAF-compliant Azure resource names with abbreviations, workload, environment, and optional region or instance.

Updated Feb 10, 2026

Search Tags:#validation #azure #iac #abbreviations #naming #caf #resource-name

Ready to run

npx skills add https://github.com/eggboy/skills --skill azure-naming-convention

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azure-naming-convention
Source: https://github.com/eggboy/skills/tree/main/azure-naming-convention
Command: npx skills add https://github.com/eggboy/skills --skill azure-naming-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generate CAF-compliant Azure resource names to standardize naming across IaC templates and Azure deployments, reducing errors and rework from inconsistent identifiers.

Core Features & Use Cases

Enforces the standard naming format: <abbreviation>-<workload>-<environment>[-<region>][-<instance>].
Uses the CAF abbreviations reference to ensure correct resource type prefixes and predictable prefixes.
Validates lowercase, length constraints, and optional components, while supporting easy adaptation in Terraform, Bicep, and ARM workflows.
Use Case: Scaffolding new Azure projects, reviewing existing resource names for CAF compliance, or automating name generation for CI/CD pipelines.

Quick Start

Provide the resource abbreviation, workload, environment, and optional region or instance to generate a CAF-compliant Azure name.

Frequently Asked Questions about azure-naming-convention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate CAF-compliant Azure resource names for IaC templates?▼

CAF-compliant Azure resource names follow the format of abbreviation, workload, environment, and optional region or instance, ensuring consistent naming across Bicep, Terraform, and ARM templates while adhering to lowercase and length constraints.

What is the standard naming format for Azure resources in the Cloud Adoption Framework?▼

The standard CAF naming format for Azure resources is abbreviation-workload-environment with optional region and instance suffixes, using hyphen delimiters and lowercase to ensure predictable identifiers across deployments.

Can I use this naming convention to validate existing Azure resource names?▼

Yes, you can validate existing Azure resource names for CAF compliance by checking them against enforced lowercase rules, length constraints, and correct resource type abbreviations to identify and correct naming inconsistencies.

Does the Azure naming convention enforce resource name length constraints and lowercase rules?▼

Yes, the Azure naming convention enforces lowercase letters, hyphen delimiters, and specific length constraints while handling optional components to ensure generated names comply with CAF rules and Azure platform requirements.

What's the best way to ensure globally unique Azure resource names during scaffolding?▼

The best way to ensure globally unique Azure resource names is to follow CAF abbreviation references and include optional region and instance suffixes, generating distinct identifiers for project scaffolding and CI/CD pipelines.

How do I find the correct CAF abbreviation for a specific Azure resource type?▼

You can find the correct CAF abbreviation for a specific Azure resource type by referencing the built-in CAF abbreviations guide, ensuring your resource names use the proper predictable prefixes for your IaC workflows.