# General Concept ### Structure In order to be able to standardize environments, naming is incredibly important. To provide a similar experience for admin users and automation this structure can be followed. It should be as compliant with the Microsoft recommendations as possible. Abbreviations are based on Microsoft best practices: [Abbreviation recommendations for Azure resources - Cloud Adoption Framework | Microsoft Learn](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations) The following contents must be included in the name of an entity: - Object entity (Microsoft Entra ID Group, Intune Configuration Profile, Microsoft Entra ID Administrative Unit, AD Group, etc.) - Affected Technology (Azure Virtual Desktop, Cloud PC, Modern Workplace, etc.) - CompanyTag(ELB, PRD, DEV, ALL, etc.) - Object type (USER, DEVICE, PERMISSION, ALL, etc.) - Description of Environment in Pascal Case-Convention (I am doing something -> IAmDoingSomething) - Production status (PROD, NONPROD, TODELETE, etc.) - (Location) Hyphen can be used to separate the entities. #### Basic concept <Entity>-<Affected Technology>-<CompanyTag>-<Object>-<Description>-<Status>
**Tag Name** | **Description** | **Examplee** |
**Entity** | What is the object? | ST, RB, CAP, CAR |
**Affected Technology** | Which technology is affected? | MW, CVD, AVD, CPC, WIN, INT, MEID, MFT, RB, SPO, EXO, TVW, ALL |
**Company Tag** | Which scope or Company is affected? | LNC, XYZ, ALL |
**Object** | Which objects are affected? | USER, DEVICE, GROUP, ROLE, PERMISSION, INTUNE, ALL |
**Description** | What is the purpose? | Short description in Pascal Case |
**Status** | How is this object used? | PROD, NONPROD, DELETED |
**Location** | In which region or location is the entity stored / created? | WE, CH, F3 |