The Azure Resource manager model allows you to logically organize resources within a subscription. Read on to understand how tagging Azure Resources works.
To help you manage your instances, images, and other Azure resources, you can assign your own metadata to each resource in the form of tags. A tag doesn’t stand by itself. It has to be applied to a resource once it’s created.
Tags enable you to categorize your resources in different ways, for example, by purpose, owner, or environment. Each tag consists of a key and an optional value, both of which you define. For example, you could define a set of tags for your virtual machine instances that helps you track each instance’s owner and stack level. You can search and filter the resources based on the tags you add. There is even a browse by tag feature in Azure
The following diagram illustrates how tagging works. In this example, you’ve assigned two tags to each of your instances, one called Dept and another called Stack. Each of the tags also has an associated value
Tags don’t have any semantic meaning and are interpreted strictly as a string of characters. Also, tags are not automatically assigned to resources. Each resource or resource group can have a maximum of 15 tags. The tag name is limited to 512 characters, and the tag value is limited to 256 characters.
Pin the most important tags to your Dashboard for quick access and you’re ready to go.
Tagging and billing
You can use tags to organize your Azure bill to reflect your own cost structure. For example, line of business teams can apply “ITDept, COSTCENTER” as a tag to imply that common shared services cost is borne by IT department. This could be for services like AD, DNS etc.
A quick run through of how tagging Azure Resources work and how we can logically group resources in Azure has been described. Also, we have seen how we can organize billing in a subscription can be tagged. Note that, tags are not themselves resources but just a string of characters.