# General Concept ### Structure In order to be able to standardise environments, naming is incredibly important. 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
**For example:** MEID-WIN-ALL-USER-IamDoingSomething-PROD