MR
Mayur Rathi
@github
⭐ 34.1k GitHub stars

Azure-Naming

Azure-Naming是一款engineering方向的AI技能,核心价值是Azure resource naming conventions based on Microsoft CAF (Cloud Adoption Framework),可用于解决开发者在engineering领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

Azure resource naming conventions based on Microsoft CAF (Cloud Adoption Framework). Use when creating, reviewing, or suggesting names for Azure resources.

Last verified on: 2026-05-30
mkdir -p ./skills/azure-naming && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/azure-naming/SKILL.md -o ./skills/azure-naming/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# Azure Resource Naming Conventions (CAF)


Source: [Define your naming convention](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming) | [Abbreviations](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations) | [Name rules](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules)


Always follow these rules when creating, suggesting, or reviewing Azure resource names.


---


General Pattern


text
<resource-type-abbr>-<workload>-<environment>-<region>-<instance>

**Component rules:**

- **Resource type** — use the official abbreviation from the table below, placed first

- **Workload / app / project** — short descriptive name (e.g., `navigator`, `payments`)

- **Environment** — `prod`, `dev`, `qa`, `stage`, `test`

- **Region** — use Azure region short names: `westus`, `eastus2`, `westeurope`, `northeurope`, `uksouth`, `southeastasia`, `australiaeast`, etc.

- **Instance** — zero-padded number: `001`, `002`


> Some resource types deviate from this pattern (e.g., no hyphens allowed). See [Official Abbreviations and Naming Rules](#official-abbreviations-and-naming-rules) for per-resource patterns and constraints.


**General character rules:**

- Prefer lowercase letters and hyphens (`-`). No spaces, no underscores unless the resource type requires it.

- Some resources **do not allow hyphens** — use concatenated lowercase alphanumerics instead (see table).

- Do not use: `#`, `<`, `>`, `%`, `&`, `\`, `?`, `/` or control characters.

- Do not encode sensitive data (subscription ID, tenant ID) in names.

- Most names are **case-insensitive** in Azure — always compare case-insensitively.

- Resources with public endpoints cannot include reserved words or trademarks.


---


Naming Scope


| Scope | Meaning |

|-------|---------|

| **Global** | Unique across all of Azure (PaaS with public endpoints) |

| **Resource group** | Unique within the resource group |

| **Resource** | Unique within the parent resource |


---


Official Abbreviations and Naming Rules


Management and Governance


| Resource | Abbr | Scope | Length | Valid Characters | Example |

|----------|------|-------|--------|-----------------|---------|

| Management group | `mg` | tenant | 1-90 | Alphanumerics, hyphens, underscores, periods, parentheses | `mg-platform-prod` |

| Resource group | `rg` | subscription | 1-90 | Underscores, hyphens, periods, parentheses, letters, digits | `rg-navigator-prod` |

| Log Analytics workspace | `log` | resource group | 4-63 | Alphanumerics and hyphens | `log-navigator-prod-001` |

| Application Insights | `appi` | resource group | 1-260 | Can't use: `%&\?/` | `appi-navigator-prod-001` |

| Automation account | `aa` | resource group + region | 6-50 | Alphanumerics and hyphens, start with letter | `aa-navigator-prod-001` |


Networking


| Resource | Abbr | Scope | Length | Valid Characters | Example |

|----------|------|-------|--------|-----------------|---------|

| Virtual network | `vnet` | resource group | 2-64 | Alphanumerics, underscores, periods, hyphens | `vnet-shared-eastus2-001` |

| Subnet | `snet` | virtual network | 1-80 | Alphanumerics, underscores, periods, hyphens | `snet-shared-eastus2-001` |

| Network security group | `nsg` | resource group | 1-80 | Alphanumerics, underscores, periods, hyphens | `nsg-weballow-001` |

| Application security group | `asg` | resource group | 1-80 | Alphanumerics, underscores, periods, hyphens | `asg-navigator-prod-001` |

| Network interface | `nic` | resource group | 1-80 | Alphanumerics, underscores, periods, hyphens | `nic-01-vmnavigator-prod-001` |

| Public IP address | `pip` | resource group | 1-80 | Alphanumerics, underscores, periods, hyphens | `pip-navigator-prod-westus-001` |

| Load balancer (internal) | `lbi` | resource group | 1-80 | Alphanumerics, underscores, periods, hyphens | `lbi-navigator-prod-001` |

| Load balancer (external

🎯 Best For

  • Engineering teams doing code reviews
  • Open source maintainers
  • Claude users
  • GitHub Copilot users
  • AI users

💡 Use Cases

  • Reviewing pull requests for security vulnerabilities
  • Checking code style consistency
  • Using Azure-Naming in daily workflow
  • Automating repetitive engineering tasks

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Azure-Naming to Your Work

    Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.

  4. 4

    Review and Refine

    Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.

❓ Frequently Asked Questions

Does this skill check for OWASP Top 10?

Security-focused review skills often include OWASP checks. Check the skill content for specific vulnerability categories covered.

How do I install Azure-Naming?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/azure-naming/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Blindly accepting AI suggestions

Always verify AI-generated review comments. Some suggestions may not apply to your specific codebase conventions.

Not reading the full skill

Skills contain important context and edge cases beyond the quick start.

🔗 Related Skills