Define your tagging strategy

When you apply metadata tags to your cloud resources, you can include information about those assets that couldn't be included in the resource name. You can use that information to perform more sophisticated filtering and reporting on resources. You want these tags to include context about the resource's associated workload or application, operational requirements, and ownership information. This information can be used by IT or business teams to find resources or generate reports about resource usage and billing.

What tags you apply to resources and what tags are required or optional differs among organizations. The following list provides examples of common tags that capture important context and information about a resource. Use this list as a starting point to establish your own tagging conventions.

Minimum suggested tags

The following tags will guide implementation and processes in all subsequent Cloud Adoption Framework methodologies. Many of the best practices in those methodologies demonstrate automation of cloud operations and governance based on the following tags.

Tag Name Description Key and example values
Workload name Name of the workload the resource supports. WorkloadName

  • ControlCharts
  • Data classification Sensitivity of data hosted by this resource. DataClassification

  • Non-business
  • Public
  • General
  • Confidential
  • Highly confidential
  • Business criticality Business impact of the resource or supported workload. Criticality

  • Low
  • Medium
  • High
  • Business unit-critical
  • Mission-critical
  • Business unit Top-level division of your company that owns the subscription or workload that the resource belongs to. In smaller organizations, this tag might represent a single corporate or shared top-level organizational element. BusinessUnit

  • Finance
  • Marketing
  • Product XYZ
  • Corp
  • Shared
  • Operations commitment Level of operations support provided for this workload or resource. OpsCommitment

  • Baseline only
  • Enhanced baseline
  • Platform operations
  • Workload operations
  • Operations team Team accountable for day-to-day operations. OpsTeam

  • Central IT
  • Cloud operations
  • ControlCharts team
  • MSP-{Managed Service Provider name}
  • Additional common tagging examples

    The following are a number of tags commonly used across Azure to increase visibility into the usage of Azure resources.

    Tag Name Description Key and example values
    Application name Added granularity, if the workload is subdivided across multiple applications or services. ApplicationName

  • IssueTrackingSystem
  • Approver name Person responsible for approving costs related to this resource. Approver

  • chris@contoso.com
  • Budget required/approved Money allocated for this application, service, or workload. BudgetAmount

  • $200,000
  • Cost center Accounting cost center associated with this resource. CostCenter

  • 55332
  • Disaster recovery Business criticality of the application, workload, or service. DR

  • Mission-critical
  • Critical
  • Essential
  • End date of the project Date when the application, workload, or service is scheduled for retirement. EndDate

  • 2023-10-15
  • Environment Deployment environment of the application, workload, or service. Env

  • Prod
  • Dev
  • QA
  • Stage
  • Test
  • Owner name Owner of the application, workload, or service. Owner

  • jane@contoso.com
  • Requester name User who requested the creation of this application. Requester

  • john@contoso.com
  • Service class Service level agreement level of the application, workload, or service. ServiceClass

  • Dev
  • Bronze
  • Silver
  • Gold
  • Start date of the project Date when the application, workload, or service was first deployed. StartDate

  • 2020-10-15
  • Take action

    Review the resource naming and tagging decision guide.

    Next steps

    Learn how to move resource groups and assets between subscriptions in Azure.