Resource naming and tagging decision guide
Organizing cloud-based resources is a crucial task for IT, unless you only have simple deployments. Use naming and tagging standards to organize your resources for the following reasons:
Resource management: Your IT teams need to quickly locate resources associated with specific workloads, environments, ownership groups, or other important information. Organizing resources is critical to assigning organizational roles and access permissions for resource management.
Cost management and optimization: Making business groups aware of cloud resource consumption requires IT to understand the resources and workloads each team is using. The following topics are supported by cost-related tags:
Operations management: Visibility for the operations management team about business commitments and SLAs is an important aspect of ongoing operations. For operations to be managed well, tagging for mission criticality is required.
Security: Classification of data and security impact is a vital data point for the team, when breaches or other security issues arise. To operate securely, tagging for data classification is required.
Governance and regulatory compliance: Maintaining consistency across resources helps identify changes from agreed-upon policies. Prescriptive guidance for resource tagging demonstrates how one of the following patterns can help when deploying governance practices. Similar patterns are available to evaluate regulatory compliance using tags.
Automation: A proper organizational scheme allows you to take advantage of automation as part of resource creation, operational monitoring, and the creation of DevOps processes. It also makes resources easier for IT to manage.
Workload optimization: Tagging can help identify patterns and resolve broad issues. Tag can also help identify the assets required to support a single workload. Tagging all assets associated with each workload enables deeper analysis of your mission-critical workloads to make sound architectural decisions.
Tagging decision guide
Your tagging approach can be simple or complex. It can support IT teams managing cloud workloads or integrate information relating to all aspects of the business.
An IT-aligned tagging focus, such as tagging based on workload, application, or environment, reduces the complexity of monitoring assets. With less complexity, you can simplify the process of making management decisions that are based on operational requirements.
Tagging schemes that include a business-aligned focus, like accounting, business ownership, or business criticality might require a larger time investment. This time is spent creating tagging standards that reflect business interests and maintain those standards over time. This investment yields a tagging system that provides improved accounting for costs and value of IT assets to the overall business. Linking an asset's business value to its operational cost can change the cost center view of IT within your wider organization.
Baseline naming conventions
A standardized naming convention is the starting point for organizing your cloud-hosted resources. A properly structured naming system allows you to quickly identify resources for both management and accounting purposes. You might have existing IT naming conventions in other parts of your organization. If so, consider whether your cloud naming conventions should align with them or if you should establish separate cloud-based standards.
Naming rules and restrictions vary per Azure resource. Your naming conventions must comply with these rules.
Resource tagging patterns
For more sophisticated organization than a consistent naming convention only can provide, cloud platforms support the ability to tag resources.
Tags are metadata elements attached to resources. Tags consist of pairs of key/value strings. The values you include in these pairs is up to you. However, the application of a consistent set of global tags, as part of a comprehensive naming and tagging policy, is a critical part of an overall governance policy.
As part of your planning process, use the following questions to determine the kind of information your resource tags need to support:
- Do your naming and tagging policies need to integrate with existing policies within your company?
- Will you implement a chargeback or showback accounting system? Will you need to associate resources with accounting information for departments, business groups, and teams in more detail than a simple subscription-level breakdown allows?
- Does tagging need to represent details such regulatory compliance requirements for a resource? What about operational details such as uptime requirements, patching schedules, or security requirements?
- What tags will be required for all resources based on centralized IT policy? What tags will be optional? Are individual teams allowed to implement their own custom tagging schemes?
The following tagging patterns are examples of how tagging can be used to organize cloud assets. These patterns aren't meant to be exclusive and can be used in parallel. They provide multiple ways of organizing assets based on your company's needs.
||Categorize resources by their purpose within a workload, what environment they've been deployed to, or other functionality and operational details.|
||Classifies a resource by how it's used and what policies apply to it.|
||Allows a resource to be associated with specific groups within an organization for billing purposes.|
||Provides information about what people (outside of IT) are related or otherwise affected by the resource.|
||Aligns resources to business functions to better support investment decisions.|
For more information about naming and tagging in Azure, see:
- Naming conventions for Azure resources. Refer to this guidance for recommended naming conventions for Azure resources.
- Use tags to organize your Azure resources and management hierarchy. You can apply tags in Azure at both the resource group and individual resource level, giving you flexibility in the granularity of any accounting reports based on applied tags.
Resource tagging is just one of the core infrastructure components requiring architectural decisions during a cloud adoption process. Visit the architectural decision guides overview to learn about alternative patterns or models used when making design decisions for other types of infrastructure.
Submit and view feedback for