Quick Tips
- Use hyphens for readability
- Keep names concise but descriptive
- Follow length restrictions
đŠī¸ Choose Cloud Provider
Microsoft Azure Selected
Generate Azure resource names following Microsoft's Cloud Adoption Framework best practices.
Select Resource Type
Naming Guidelines
đ Microsoft Azure Best Practices
Microsoft 2024 Naming Pattern:
<resource-type>-<workload>-<environment>-<region>-<instance>
Required Components:
- Resource Type: Official Azure abbreviations (vm, app, func, st, etc.)
- Workload/Application: Project/application name (navigator, sharepoint, hadoop)
- Environment: Deployment stage (prod, dev, test, stage)
- Instance: Numbering for multiple resources (001, 01, etc.)
Optional Components:
- Business Unit: Department/division (fin, mktg, it, corp)
- Region: Azure region (eastus, westus, westeu)
Examples from Microsoft:
- vm-sharepoint-prod-001
- app-navigator-dev-001
- func-emissions-test-001
Naming Components
Top-level organization name (optional prefix)
Department or business division (as per Microsoft examples)
Project/application name (as per Microsoft examples)
Instance number (001, 01, etc.)
Infrastructure as Code
đĸ Bulk Generation
Ctrl+Enter to generate
Generated Name
Resource Name
đˇī¸ Suggested Resource Tags
Based on Microsoft Azure best practices for resource tagging:
đĄ Tip: Use these tags to organize, track costs, and manage your Azure resources effectively.
đ Microsoft Best Practices Compliance
This naming convention follows official Microsoft Azure Cloud Adoption Framework guidelines: