Better cloud management through cloud resource tagging


Enterprises are now, more than ever, managing multi-cloud environments, trying to come to grips with highly complex pricing structures and an onslaught of new cloud services. The key to success is implementing enterprise-grade governance platforms that enable you to efficiently optimize costs across all cloud providers and ensure that you have access to any and all of the cloud services that your company requires.

Tagging of cloud resources is a critical foundation for your cloud governance initiatives. You will need a consistent set of tags specifically for governance and will apply globally across all of your resources. These global tags will add metadata specific to your organization that helps you better categorize each of your cloud resources for cost allocation, reporting, chargeback and showback, cost optimization, compliance, and security.

Defining your tagging policy

Your cloud governance team should lead a process of defining your global tagging policy. It will be important to work with key stakeholders to get feedback and buy-in. Global tags should be applied consistently by all applications and teams in your organization. Individual teams or applications may add additional tags for their specific needs as well.

Absent a tagging policy, it is common for teams or individuals within the same organization to use variations of the same tag, which makes it extremely difficult to achieve accurate reporting. To effectively use tags for reporting and governance purposes, it is critical to create a policy that defines consistent naming conventions including spelling, uppercase/lowercase conventions, and spacing.

” particular tags for cost allocation so that they show up in billing reports.

Maximum active tag keys for billing and cost management reports: 500.

Can tag on Azure Resource Manager (ARM) resources only (not classic Azure).

Tag at resource group or resource level. Suggest resource level for better cost allocation.

Combine tags or use JSON string if exceeding the 15 tag limit.

Labels are a Beta service.

Keys must start with a lowercase letter.

Tags are called “labels” in GCP.

Note that “network tags” in GCP are used to apply firewall rules. These are separate from labels.

Taggable resources

All ARM resources can be tagged.


Implementing your tagging policy

To effectively implement your tagging policy, you will need to create a staged rollout process.

. She has held executive marketing positions at a variety of enterprise software startups and public software companies. She received a B.S. in engineering from Duke University.