Azure tagging provides an important benefit of managing and organising azure resources effectively and to get a better visibility, identification and grouping. Here are some the usage, facts to remember and best practices.
Azure Tagging
- Azure Tags are a simple name and value pair of text data which can be applied to most of the Azure Resources and Resource Groups.
- Azure Tags are specific to a particular Azure Resource and upto 50 Tags can be assigned to a Resource.
- Azure Tag names can have maximum of 512 characters and a Tag value can have 256 characters.
- Azure Tags are not case-sensitive
- Azure Tags does not support the special characters (such as
< > % & / ? *etc) to be included. - Tags applied at a resource group level are not inherited or propagated to resources within the resource group. So Azure Tags are specific to the Resource or a Resource Group assigned.
- Not all the Azure Resources support tags, so check before planning or making a policy.
- Azure Classic Resources doesn’t support tags.
- Tags can be added and managed through Azure Portal, Azure Powershell, Azure CLI, REST API’s and Azure Resource Manager (ARM) templates.
Azure Tags Usage and Best Practices
- Use the tags to associate a cost center with resources for internal chargeback.
- Use the tags in conjunction with Azure Automation to schedule maintenance windows and automated shutdown and restarts.
- Use the tags to store environment and department association.
- Use the tags to define security identifier for Resources.
- Use the tag to monitor and track down the impacted resource. Azure monitor and other monitoring tools can include the tag info in logs and alerts.