Technology Portfolio Management (TPM) Best Practices

Overview

Cost visibility is the foundational discipline of FinOps. Cloud spending that cannot be attributed to specific services, applications, teams, or business capabilities cannot be governed, optimized, or allocated in any meaningful way. The mechanism for creating that attribution in cloud environments is resource tagging — applying consistent, governed metadata tags to every cloud resource at provisioning time that identify the application, team, environment, and business capability the resource supports. Without consistent tagging, cloud cost data is accurate in aggregate and meaningless in detail. With consistent tagging, every dollar of cloud spending is attributable to a specific organizational purpose.

Best Practice

Define and enforce a cloud resource tagging standard that applies to every resource provisioned in every cloud account across all cloud providers the organization uses. The tagging standard should define the mandatory tags — those required on every resource without exception — and the recommended tags that should be applied where applicable. Mandatory tags should at minimum identify: the application or service the resource supports, using the semantic identifier from the Applications Inventory; the technology type, using the semantic identifier from the Cloud and Infrastructure Services Inventory; the environment (production, staging, development, or equivalent); the team or organizational unit responsible for the resource; and the cost center or business capability to which the resource cost should be allocated. Enforce the tagging standard through policy controls in cloud provider policy frameworks (AWS Service Control Policies, Azure Policy, Google Cloud Organization Policy) that prevent or flag resource provisioning without required tags, and through automated tag compliance scanning that identifies and escalates untagged or incorrectly tagged resources.

Benefit(s)

Consistent cloud resource tagging is the governance investment that makes all other FinOps disciplines possible. Without tagging, FinOps analysis can identify aggregate cloud waste but cannot attribute it to specific applications, teams, or capabilities, making remediation ownership ambiguous. With tagging, every cost optimization opportunity is attributed to a specific owner who can be engaged directly in the optimization process. The tagging investment pays returns across every FinOps discipline: cost visibility, right-sizing prioritization, reserved capacity allocation, utilization management, and business-aligned cost reporting all depend on the tag data that consistent tagging governance maintains.