FinOps Transformation in a Commodity Trading House

When FinOps was proposed, the top team felt that a metadata strategy would slow projects. They asked for reports without changing the way people created resources. We had to explain that without consistent tags there is no showback, no alerts, no budget baselines. Only after that discussion they approved one key rule. Every resource must have core tags.

Mandatory Metadata as Company Policy

We wrote the tag set into the company cloud policy so it applied to portal creation and to Terraform. The core set was the same for all teams.

Core Tags

• workloadname
• businessentity
• costcenter
• createddate
• createdby
• control with value Terraform or manual

Optional Tags

• dataclassification
• disasterrecovery
• environment
• ownername
• serviceticket
• documentation
• backupretention

By doing this we made sure that every resource had a business owner, a cost owner and a technical origin. This matched the FinOps Framework thinking, identify the owner, measure, then optimize. We ran workshops for top leadership, for management and for FinOps.

Each group saw the same message. Tags are not for auditors. Tags are the link between the bill and the business entities.

Cleaning Up Creativity in Names and Tags

After enforcement we saw a second problem. People used creative values. Some teams wrote only environment. Some used a code name for the app. Some put team names into businessentity. This made reporting messy. We prepared a naming convention for common resources with ready examples. Storage accounts, VNets, databases, app services, all had one good example in the guide. We asked every team to copy the example and only change the parts that were allowed to change. This lowered the entropy and helped later automation.

Alerts for Every Subscription

Once tags and names were stable we added daily alerts for every subscription. Each alert had two thresholds. The lower one sent to the delivery team, the higher one sent to management. Because tags were present, the alert message could say which businessentity and which costcenter was affected. This made alerts actionable, which is one of the lessons other FinOps practitioners report as well.

Building the Data Foundation with FOCUS

After a few months the environment had enough tagged resources and daily costs. We set up ingestion from the cloud billing source into Azure Data Factory. We shaped the data according to the FOCUS Specification. Because the tags were clean, mapping to FOCUS dimensions was simple. From this data we built reports for every team, for every project, for every subscription and for every entity. This created the first benchmark for the next year budget. Leaders could see how much production costs, how much development costs and which businessentity grows fastest.

Sample record for one resource in the warehouse

subscription = prod-trading-eu
workloadname = tdo-easyfeed
businessentity = ezpada-trading
costcenter = H-TDO
service = Azure SQL
meter = SQL Database General Purpose
cost = 143.40
environment = prod
control = terraform
date = 2025-05-11

With data in this form Finance could create showback and managers could compare projects.

Cookbook for New Development Costs

Engineers asked how to price new services. We did not want them to guess. We created a small cookbook with common resources and with three ranges, low, mid and high. Values were based on our own tagged history, not on vendor marketing. An engineer could take one App Service, one database, one storage account and see a working estimate. This supported the FinOps practice of informing and operating, not just reporting.

Example from the cookbook:

• App Service production, mid range
• Azure SQL for reporting, low range
• Storage for logs, low range

Combined this gives an expected monthly cost for the new feature.

Guidance for Other Practitioners

FinOps-Centric Guidance

• Start with one rule. Every resource must have core tags
• Enforce in the platform. Docs without policy will be ignored
• Train leadership and management, not only engineers
• Align tags with FOCUS early to avoid remapping later
• Make alerts use tag values so people see business impact

Challenges

• Leadership often thinks metadata is administration, you must tie it to showback
• Teams will try to invent their own keys, keep one master list
• If naming is not standard, anomaly detection is harder
• If you skip workshops, people will fill tags randomly

Cautionary Tales

• Do not allow projects to create resources from the portal without policy
• Do not mix costcenter and businessentity in one field
• Do not wait for CMDB to be perfect, use tags as the source of truth

Measures of Success and KPIs

• Percentage of resources with all mandatory tags, target 95 percent and higher
• Number of tag violations per week, target is a falling trend
• Time needed to produce monthly showback per entity
• Share of subscriptions with daily alerts
• Forecast accuracy for the next quarter based on FOCUS data

Risks and Considerations

• If Terraform modules do not contain tags, people will deploy untagged resources
• If businessentity changes often, tags must be updated in bulk
• If optional tags are too many, engineers will stop filling them
• If Finance does not consume the FOCUS like structure, you must provide a mapping

Decisions Made and Options

• Leadership approved mandatory tags for all resources
• We chose one set of keys for the whole group, option to let each project define keys was rejected because reporting would fail
• We ingested billing through Azure Data Factory since the data team already used it
• We created a cookbook instead of asking engineers to read the full rate card

Process Steps to Implement

• 1. Define mandatory and optional tags with Finance and Security
• 2. Create cloud policies that block creation of untagged resources
• 3. Publish naming examples for common services
• 4. Run workshops for leaders, managers and FinOps
• 5. Configure daily alerts per subscription with two thresholds
• 6. Ingest billing into ADF and align to FOCUS
• 7. Build the cost cookbook and update it quarterly
• 8. Report tag compliance monthly to management

Steps to Verify Outcomes

• Run a tag compliance report, confirm that new resources are tagged
• Trigger an alert and check that the message contains businessentity and costcenter
• Check that Finance can produce a showback per entity
• Review that the next year budget is based on real usage from the FOCUS data
• Ask engineers if the cookbook was enough to price a new feature

CSPs, Tooling, and References

• Azure Policy for tag enforcement
• Terraform modules with tag blocks
• Azure Cost Management exports
• Azure Data Factory for ingestion
• FinOps Foundation FOCUS specification
• Internal wiki or SharePoint for the cookbook

Organization Information for Readers

The company runs trading and energy related activities, it uses multiple country entities and mixes data, apps and trading workloads in cloud. Any organization with several business entities, with shared subscriptions and with fast delivery teams will face the same issue. Without mandatory metadata FinOps stays only in PowerPoint. With platform enforcement FinOps becomes daily work.

Lessons Learned / Takeaways

This journey confirmed that FinOps only works when metadata is enforced in the platform, not just described in a document. Making tags mandatory was the single decision that unlocked alerts, reporting and budget planning. An unexpected outcome was that management started to trust the reports once they saw their own business entities in the data. A negative outcome we spotted early was creative tag values, which is why naming examples and workshops were needed. Readers should secure executive approval for mandatory tags, publish clear tag and naming examples and set up automated checks so non compliant resources are visible the same day.