Tags
What it is
Tags are key-value metadata you add to Azure resources, resource groups, and subscriptions. Examples include environment=production, costCenter=retail, and owner=orders-team. A tag makes a resource easier to find, group, report on, and automate; it does not change what the resource can do.
Why it exists
Tags let you organize, classify, and query resources for cost reporting, resource management/filtering, and automation — Azure Cost Management and many dashboards group by tag. They support policy-driven tagging standards (e.g. require a costcenter tag via Policy).
Key ideas
- A tag is plain-text metadata. Never place passwords, tokens, personal data, or other secrets in a tag: tags can surface in reports, deployment history, commands, and logs.
- Tags do not automatically inherit from a resource group or subscription to resources. Azure Policy can enforce or add an inheritance pattern where suitable; Cost Management tag inheritance is a separate reporting feature and does not necessarily write the tag onto the resource.
- Tags do not grant access. RBAC authorizes people and workloads; Policy governs allowed configuration; tags add business context.
- Tag support and limits vary by resource type. Confirm support for a specific resource before making a workflow depend on it.
Northwind example
Northwind applies environment=production, application=orders, and costCenter=retail to resources that run its ordering workload. Priya filters cost reports by application=orders; Maya uses Policy to require the business tags on new supported resources. Luis still needs RBAC to modify the production web app—the owner=orders-team tag is a helpful label, not a permission.
Common confusion
- A tag is not a resource name, resource group, management group, or security group.
- A tag cannot reliably model a complex hierarchy or replace separate subscriptions when billing, access, or quotas must be isolated.
- Inconsistent spelling and casing create fragmented reports. Agree a small tag vocabulary before applying tags at scale.
How it fits (diagram)
Practical tag set
Start with a small stable set such as environment, application, owner, and cost center. Document allowed values, enforce only the tags that genuinely matter, and review exceptions rather than creating dozens of inconsistent labels.
Related
resource-group · subscription · azure-policy · rbac · azure-cost-management · northwind-traders-case-study
📘 Source: Microsoft Learn — Use tags to organize Azure resources, checked 2026-09-16.