Essential Tags for Multi-Cloud Cost Allocation

If you were designing a tagging standard for a company running on AWS, GCP, and Azure, which tags would you require on every resource and why?

Mid-Level questions

FinOpsintermediate

// interview question

If you were designing a tagging standard for a company running on AWS, GCP, and Azure, which tags would you require on every resource and why?

Sample answer

Keep the required set small. Five tags is my baseline: environment (prod, staging, dev, sandbox), team or owner (who pays and who to call at 3am), cost-center (the accounting code finance actually uses), application or service (which product this resource belongs to), and managed-by (terraform, pulumi, manual, console). Those five answer the questions finance asks every month and give engineering enough to drive ownership. Optional but common additions: project or ticket for short-lived resources, customer for multi-tenant SaaS workloads, and data-classification for compliance. Two rules I insist on. First, pick one casing and stick to it. team=payments, Team=Payments, and TEAM=PAYMENTS are three different values to the billing system and will fragment your reports. Lowercase with hyphens is the safest across AWS, GCP, and Azure since GCP labels reject uppercase anyway. Second, fewer mandatory tags means higher compliance. If you require 15 tags, engineers will copy-paste junk values to get past the policy. Start with 3 to 5 that finance and engineering agreed on together, then add more only when you have a concrete reporting need.

Why this matters

This question tests whether the candidate has actually shipped a tagging policy or just read about one. Strong candidates will explain the tradeoff between completeness and compliance, mention case sensitivity and the GCP label restrictions, and talk about getting finance involved early. Watch for candidates who list 12 required tags - they usually have not had to enforce them across a real org.

Code examples

Terraform default tags for AWS and shared locals for Azure and GCP

hcl

# AWS: default_tags apply to every resource in this provider block
provider "aws" {
  region = "us-east-1"

  default_tags {
    tags = {
      team        = "payments"
      environment = "prod"
      cost-center = "eng-4200"
      application = "checkout-api"
      managed-by  = "terraform"
    }
  }
}

# Shared tag map for Azure and GCP resources
locals {
  common_tags = {
    team        = "payments"
    environment = "prod"
    cost-center = "eng-4200"
    application = "checkout-api"
    managed-by  = "terraform"
  }
}

resource "azurerm_linux_virtual_machine" "api" {
  name                = "prod-api-01"
  resource_group_name = azurerm_resource_group.rg.name
  location            = "eastus"
  tags                = local.common_tags
  # ... size, image, nic omitted
}

resource "google_compute_instance" "api" {
  name         = "prod-api-01"
  machine_type = "e2-standard-2"
  zone         = "us-central1-a"
  labels       = local.common_tags
  # ... boot_disk, network_interface omitted
}

Tagging standard documented for humans

yaml

# tagging-standard.yaml - single source of truth for the org
required_tags:
  - key: team
    description: Engineering team that owns the resource
    allowed_values: [payments, identity, growth, platform, data]

  - key: environment
    description: Deployment environment
    allowed_values: [prod, staging, dev, sandbox]

  - key: cost-center
    description: Finance cost center code
    pattern: "^eng-[0-9]{4}$"

  - key: application
    description: Logical application name this resource supports
    pattern: "^[a-z0-9-]+$"

  - key: managed-by
    description: How this resource was provisioned
    allowed_values: [terraform, pulumi, helm, manual]

casing: lowercase-hyphen
enforcement:
  aws: organizations-tag-policy + aws-config
  azure: azure-policy-deny
  gcp: terraform-default + opa-in-ci

Common mistakes to avoid

Requiring 10+ mandatory tags and wondering why compliance is at 40 percent
Mixing casing conventions across clouds so team=Payments and team=payments show up as two teams in reports
Not agreeing the tag values with finance first, so cost-center codes in the cloud do not match the ones in the ERP

Likely follow-ups

Why lowercase and hyphens instead of camelCase?
How do you handle tag sprawl when every team wants to add their own?
What do you do when finance wants a tag that engineering cannot answer at resource creation time?

Answer out loud first, then check yourself against the model answer.

Practice all Mid-Level questions More FinOps questions

#finops#cloud-costs#tagging#multi-cloud#governance

Also worth your time on this topic

Interview

Enforcing Tagging Policies Across Clouds

How do you actually enforce that every resource in AWS, GCP, and Azure gets the required tags? Walk me through what you would put in place.

mid

Checklist

How to Set Up Cloud Cost Allocation Tags Across AWS, GCP, and Azure

A practical guide to implementing consistent cost allocation tagging strategies across multi-cloud environments for accurate chargeback and showback.

60-120 minutes

Article

How to Set Up Cloud Cost Allocation Tags Across AWS, GCP, and Azure

A working playbook for tagging resources across AWS, GCP, and Azure so finance can finally answer which team spent what, and engineers can prove their workload is not the expensive one.

Essential Tags for Multi-Cloud Cost Allocation

More FinOps interview questions

Also worth your time on this topic

Enforcing Tagging Policies Across Clouds

How to Set Up Cloud Cost Allocation Tags Across AWS, GCP, and Azure

How to Set Up Cloud Cost Allocation Tags Across AWS, GCP, and Azure