Azure tagging strategy, part 2: from alert to ticket with Terraform and ITSM tags
· 6 min read
When something breaks on a data platform, the first question is which service is affected and who owns it. This is part 2 of 3. It shows how we answer that with tags: three itsm-* tags that mirror the ITSM (IT service management) service tree, plus env, managed-by and data-product, all generated by one Terraform module. It builds on the decisions from part 1.
TL;DR
- Keep the set small, mandatory and enforced. Every tag needs a reader. Ours are six, each with a named reader: three
itsm-*tags route incidents,data-productattributes cost,envsplits prod from non-prod cost, andmanaged-byexposes click-ops. All are generated and audited. - Generate tags in a central Terraform module, including
managed-byfor everything IaC creates. Azure Policy audits; it isn't the source. - Mirror your ITSM service tree in tags, so they route incidents. Don't reuse ITSM tags for cost: a shared Databricks workspace has one ITSM service but many products.
- One product, one spelling, everywhere. The module emits the
data-productslug once; Azure resources and Databricks jobs reuse the same key and value.

