From cd4716f918ae7e581e0ac3c3a6d51fe328b5e601 Mon Sep 17 00:00:00 2001 From: Jan Jambor Date: Mon, 22 Jul 2024 19:17:01 +0200 Subject: [PATCH] =?UTF-8?q?new:=20Namingconvention=20gem=C3=A4ss=20AzureNa?= =?UTF-8?q?mingTool=20erg=C3=A4nzt.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 2eaa68e..d24c9c8 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,19 @@ This space is for the engineering team to share knowledge, resources, and best practices. +## Conventions + +### Naming conventions + +As we are heavily using Microsoft Azure and Azure DevOps, we are following the naming conventions provided by Microsoft: + +- [Abbreviation recommendations for Azure resources](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations) + +Furthermore, we are using the [AzureNamingTool](https://github.com/mspnp/AzureNamingTool): + +- [AzureNamingTool Deployment Instructions](https://xwr.visualstudio.com/jambor.pro/_git/app-azure-naming) +- [AzureNamingTool Development Instance](https://app-azurenamingtool-dev-bnhfgbdgafeqh2gf.switzerlandnorth-01.azurewebsites.net) + ## Sructure of the repository We are trying to keep the repositories small and structured. The following overview shows the general structure and the most important repositories.