Naming
Subscription Naming Policy
A subscription in Azure is a collection of Azure resources, including virtual machines, storage accounts, and networks, that you manage and pay for as a single unit. It provides a way to organize and control access to Azure resources.
Why a Good Naming Policy is Important?
A good naming policy is crucial for several reasons:
- Clarity and Organization: A consistent naming policy ensures that resources are easily identifiable and organized, making it simpler to find and manage them.
- Efficiency: Consistent naming conventions help in automating processes, reducing manual errors, and improving overall efficiency.
- Compliance: Adhering to naming policies can help in meeting organizational and industry-specific compliance requirements.
- Documentation: Well-named resources provide a valuable reference for documentation, making it easier for teams to understand the purpose and usage of resources.
- Scalability: As the environment grows, a good naming policy ensures that new resources are added in a predictable and manageable way.
By following a consistent naming policy, teams can maintain a clean and organized environment, which is essential for effective resource management and cost control.
All subscriptions must follow the same naming convention. This ensures clarity and uniformity in the environment.
The name is divided into 4 parts: - Customer Name - SUB - Department - Purpose - Region
Customer Name For the initial rollout of the environment, an abbreviation of the customer name is created. This abbreviation must be at least 2 and at most 4 characters long due to limitations on name length. This abbreviation is also used in most resource names within the environment.
SUB The second part is used to indicate that it is a subscription, abbreviated as SUB.
Department To clearly distinguish the responsibilities of the subscription, we also include the abbreviation of the department in the name. A couple possible abbreviations are:
| Department | Abbreviation |
|---|---|
| IT | IT |
| Data & RPA | DAT |
| Security | SEC |
| Power Platform | APP |
| Business Intelligence | BI |
Department Overstepping In some cases, there will also be a subscription for general purposes that are not linked to a specific department. An example of this is the HUB subscription for network components. There is currently no naming convention for this. The name will be decided on whenever it is needed, either a general 'Platform' naming scheme will be used or the department that has to manage it
The HUB subscription currently uses the word HUB instead of refering to a department.
Type This indicates whether it is a production, acceptance, test, or development environment.
| Type | Abbreviation |
|---|---|
| Production | PROD |
| Acceptance | ACC |
| Test | TST |
| Development | DEV |