feat: Add Azure resource naming conventions based on Microsoft CAF#1635
Conversation
There was a problem hiding this comment.
main, but PRs should target staged.
The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.
You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 1635 --base staged
There was a problem hiding this comment.
Pull request overview
Adds a new GitHub Copilot custom instruction file that documents Azure resource naming conventions aligned to Microsoft CAF, intended to guide naming suggestions/reviews for IaC files (Bicep/Terraform) and infrastructure directories.
Changes:
- Introduces
azure-naming.instructions.mdwith a recommended naming pattern, constraints, and a resource abbreviation/rules table. - Adds examples and “do not do” guidance for common Azure naming pitfalls.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…atterns and constraints Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
I couldn't determine any contributions to add, did you specify any contributions? |
|
@all-contributors add @username for instructions |
|
I couldn't determine any contributions to add, did you specify any contributions? |
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.stagedbranch for this pull request.Description
Adds an instruction file with Azure resource naming conventions based on the Microsoft Cloud Adoption Framework (CAF). It covers the general naming pattern, per-resource abbreviations, character constraints, naming scope, and examples across all major Azure service categories (networking, compute, containers, databases, storage, security, AI, etc.). Apply to Bicep, Terraform, and infrastructure files.
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.