Read a sample: 1. The Governance Problem Tags Can Solve
A resource can be running normally and still be a governance problem. Its monitoring may be green, its deployment may be repeatable, and its application may be serving users. Yet when someone asks who pays for it, who approves a change, or whether it is still needed, the answer may require a week of messages.
That delay is not just an administrative inconvenience. It affects decisions. An unclaimed resource may remain in service because no one is confident enough to retire it. A shared platform cost may be charged to one team simply because that team created the subscription. An urgent security finding may reach a former employee rather than the people who can fix it.
Azure resource tags and naming conventions can make these questions easier to answer. They cannot answer them by themselves. Their value comes from a process that assigns meaning to metadata, keeps that meaning current, and connects it to decisions people are authorized to make.
This chapter introduces the governance problems the rest of the book addresses. It also introduces a fictional organization whose environment will serve as a running case.
Northstar Outfitters is a fictional retailer with online sales, regional operations, and a small internal technology department. Its Azure environment grew over several years. The infrastructure team created early subscriptions, application teams added resources for new products, and an external partner deployed part of the data platform.
Nobody set out to create a confusing environment. Each team made reasonable local decisions under delivery pressure. The result is nevertheless difficult to manage as a whole.
One resource group is named rg-commerce-prod-eastus. Another is named DataStuff. A virtual machine has an Owner tag containing a person’s name, but that person has moved to a different department. Several resources have an Environment tag, using values such as Prod, Production, and Live. A storage account has no tags, although its resource group has several. A shared monitoring resource is tagged with the name of the team that deployed it, even though multiple teams depend on it.
Northstar’s finance lead wants a monthly view of cloud spending by business product. The operations lead wants an escalation contact for production resources. The governance lead wants teams to review old test environments. Each request sounds like a reporting task, but each exposes a decision that has not been fully made.
For example, should shared monitoring costs be assigned to the infrastructure team, divided among products, or shown separately as a platform expense? The resource itself cannot decide. Nor can a tag settle whether an apparently inactive test environment contains data that must be retained.
Northstar does not need a long list of labels. It needs an agreed way to connect resources and charges to accountable people, allocation choices, and review actions.
In this book, governance means the practical arrangements that help an organization make and carry out decisions about its cloud environment. Those arrangements can include standards, responsibilities, controls, reports, and exception processes. A useful standard should help someone act, not merely make a dashboard look complete.
Three decisions recur throughout this guide:
- Ownership: Who is accountable for the resource, and who can operate or troubleshoot it?
- Cost allocation: Where should its eligible costs be reported, and how should shared or unattributed charges be handled?
- Lifecycle review: Who should confirm that it is still needed, appropriately configured, and ready for renewal, change, or retirement?
These decisions are related, but they are not interchangeable. A business owner may be accountable for the purpose and funding of an application, while a platform team operates its infrastructure. The team paying a bill may not be the team that can respond to an outage. A person authorized to review a resource may not have authority to delete it.
That is why a single Owner tag often becomes ambiguous. If one team interprets it as “the person who deployed this” and another as “the budget holder,” the same tag name carries two different meanings. Reports may appear consistent while directing questions to the wrong people.
Before choosing a tag, ask what action its value will support. If the answer is “contact the team responsible for restoring service,” define the field around operational responsibility and establish where its value is maintained. If the answer is “allocate spending to a product,” agree on the product or financial mapping first. The field is the container for a decision, not a substitute for one.
An Azure resource tag is metadata expressed as a name-value pair. A resource might have a tag named Environment with the value Production, or a tag named BusinessOwner with the value Retail Operations. Tags make it possible to attach organizational context that is not necessarily apparent from a resource’s technical configuration.
Tags are useful because they can be read and processed consistently when an organization defines them consistently. A report can group resources by an Environment value. A review process can look for a ReviewDate. A governance team can compare cost-allocation values with an approved mapping.
The important qualification is when supported and populated. Azure services and resource types do not all expose the same tagging behavior. Some resources may have limitations, and the availability of tag information in cost reports depends on the charge and reporting context. Verify the behavior of the relevant resource types and current billing views before designing a control or report around an assumption.
Tags on a resource…