FinOps for Public Cloud - FinOps Framework Technology Category

FinOps for Public Cloud - FinOps Framework Technology Category
Loading...
Get Certified
Join the Community
Training
Back to menu
Training Catalog
Recommended Training
Mentorship Program
FinOps Certified Professionals
Professional Contributions
FAQs
Framework
Back to menu
Overview
Scopes
Principles
Personas
Phases
Maturity
Domains
Capabilities
Technology Categories
Asset Library
FOCUS
State of FinOps
FinOps X
Assets
Back to menu
Asset Library
FinOps X Session Library
FinOps Landscape
KPIs
Terminology
FinOps Assessment
FinOps Cloud Book
About
Back to menu
About
Who We Are
What is FinOps?
Mission & Structure
Governing Board
Technical Advisory Council
Member Organizations
Ambassadors
Foundation Staff
Latest Information
Adopting FinOps: Getting Started
Content Attribution
FinOps Foundation Insights
FinOps Landscape
Cloud FinOps Book
What’s New in FinOps
Get Involved
Join as an Individual
Join as an Enterprise
Get Certified
Join the Community
FinOps X 2026 · June 8-11 · San Diego
Register Now
Framework
Overview
Scopes
Principles
Personas
Phases
Maturity
Domains
Capabilities
Technology Categories
Asset Library
Make Suggestion
This work is licensed under
CC BY 4.0
- Read how use or adaptation requires attribution
FinOps for Public Cloud
Framework
FinOps Technology Categories
FinOps for Public Cloud
FinOps for Public Cloud focuses on managing and optimizing cloud-based consumption in support of business outcomes such as cost efficiency, agility, and delivery velocity.
FinOps Capabilities
are applied to provider billing and usage data, resource-level telemetry, and service activity across IaaS and PaaS to enable informed decisions, shared accountability, and continuous alignment between cloud investment and business value.
On this page:
FinOps Considerations for Public Cloud
FinOps Personas
Framework Domains & Capabilities
Measure of Success & KPIs
FOCUS Alignment
FinOps for Public Cloud Tools and Service Providers
FinOps Considerations for Public Cloud
Public cloud provides organizations with on-demand access to a broad and rapidly evolving portfolio of IaaS and PaaS services spanning compute, storage, database, networking, and managed services that are billed based on consumption, commitment, or a combination of both.
FinOps Practitioners
are supported by a mature ecosystem of FinOps tooling and services, a well-established operating model through the
FinOps Framework
, and a rich commitment discount landscape that rewards collaborative and planned purchasing decisions.
As public cloud spend grows in scale and strategic importance,
FinOps Practitioners
collaborate across
FinOps Personas
to enable timely, data-driven decisions and financial accountability, ensuring that consumption remains visible and continuously aligned with business priorities. The pace of change in public cloud from new services, pricing models, and provider capabilities means that maintaining an effective FinOps practice requires ongoing attention beyond a cost savings motion.
Key considerations when applying FinOps concepts to create a Public Cloud practice profile include:
Commitment Discount Management:
Public cloud providers offer a variety of commitment-based purchasing options such as reserved instances, savings plans, and committed use discounts that can significantly reduce effective rates. Selecting, sizing, and managing these commitments requires balancing coverage, flexibility, and utilization across a dynamic workload landscape.
Tagging and Allocation at Scale:
Public cloud environments support resource-level tagging and account hierarchy structures that enable cost allocation to teams, products, and business units. Maintaining consistent, complete, and enforceable tagging standards across large, distributed estates is an ongoing governance challenge.
Multi-Cloud Complexity:
Many organizations operate across multiple public cloud providers simultaneously. This introduces challenges in normalizing cost and usage data, applying consistent governance, and maintaining a unified view of spend and efficiency across providers. Adopting open billing schemas such as the
FinOps Open Cost and Usage Specification (FOCUS)
helps address these challenges by enabling consistent cost and usage data across providers, reducing normalization effort and supporting cross-provider analysis.
Pace of Service Evolution:
Public cloud providers continuously introduce new services, pricing constructs, and purchasing options. Practitioners must actively monitor these changes to identify workload and architecture opportunities, optimize existing usage, and ensure governance policies remain relevant.
Native Tooling and Third-Party Ecosystem:
Public cloud providers offer mature, built-in cost management capabilities including billing exports, cost explorer tools, and budgeting alerts, alongside a rich ecosystem of third-party platforms that extend visibility, automation, and optimization. Using outcome-based criteria aligned to the FinOps Framework to select and operationalize the right combination of tools is a key FinOps practice decision.
Anomaly Detection and Spend Governance:
The elastic, on-demand nature of public cloud means that spend can scale rapidly in response to workload changes, misconfigurations, or unintended usage. Effective anomaly detection and automated guardrails are essential to maintaining cost control without impeding engineering velocity.
Shared Responsibility for Cost:
Public cloud operates on a shared responsibility model where cost outcomes depend on decisions made across
FinOps Personas
including
FinOps Practitioners
Engineering
Product
Finance
, and
Procurement
. Defining
FinOps Scopes
in public cloud is fundamentally a cross-functional practice, requiring clear ownership, accountability, and collaborative decision-making.
Workload Placement and Architecture:
Decisions about which services to use, how workloads are architected, and where they are deployed have material cost implications in public cloud.
FinOps Practitioners
contribute cost and commercial insight to architecture and placement decisions to support better value outcomes.
Sustainability and Carbon Visibility:
Public cloud providers increasingly offer region-level and service-level carbon emissions data. Practitioners can incorporate sustainability signals into workload placement, architecture, and optimization decisions to support organizational environmental objectives.
Unit Economics at Cloud Scale:
The granularity and volume of public cloud billing data creates the opportunity to build detailed unit cost models linking cloud spend to products, features, customers, or transactions. Realizing this opportunity requires investment in data quality, allocation accuracy, and alignment on the right metrics across all
FinOps Personas
Must Reads
How to Calculate Effective Average Cost of Compute per vCPU
Playbook
Accurate Cloud Forecasts
Paper
How to Calculate Effective Savings Rate (ESR)
Playbook
How to Calculate Percentage of Costs Associated with Untagged CSP Cloud Resources
Playbook
How to Calculate Percentage of Commitment Discount Waste
Playbook
Building a FOCUS Data Export Pipeline for Alibaba Cloud
Paper
FinOps Personas
As a FinOps Practitioner Persona, I will…
Collaborate with
Finance
Engineering
, and
Product
Personas to develop and maintain cost allocation models, including showback and chargeback, that accurately reflect public cloud consumption across accounts, services, and teams.
Identify, analyze, and communicate optimization and waste opportunities related to idle or over-provisioned resources, uncommitted spend, and underutilized commitment discounts across compute, storage, database, and networking services.
Consult with
Finance
Product
, and
Procurement
Personas to align forecasting and budgeting with cloud workload patterns, growth trends, and commitment purchasing cycles.
Provide
Engineering
and
Procurement
Personas with insights into historical consumption and efficiency to support commitment discount decisions, including sizing, coverage, and renewal timing.
Partner with
Engineering
Personas to define, enforce, and continuously improve tagging and resource attribution standards that enable accurate cost tracking across a distributed public cloud estate.
Define and communicate unit economics and efficiency metrics that connect public cloud spend to business outcomes, enabling informed prioritization and investment decisions across
FinOps Personas
Support executive decision-making by translating public cloud cost and usage data into clear, business-aligned narratives that communicate investment value, risk, and strategic trade-offs to
Leadership
Personas.
As a FinOps Engineering Persona, I will…
Design, build, and operationalize public cloud workloads with an understanding of consumption-based and commitment-based pricing models, resource provisioning behavior, and the cost implications of architectural decisions across IaaS and PaaS services.
Collaborate with
FinOps Practitioner
and
Finance
Personas to provide workload-level context, including resource utilization patterns, deployment configurations, and scaling behavior, to support accurate allocation and forecasting.
Identify and implement optimization opportunities by rightsizing compute, storage, and database resources, eliminating idle or orphaned assets, and improving architectural efficiency to reduce unnecessary consumption.
Apply tagging, resource naming, and ownership standards consistently across accounts, services, and environments to enable accurate cost attribution and support showback and chargeback models.
Use cloud-native controls such as auto-scaling policies, budget alerts, and resource scheduling to balance performance, reliability, and cost across public cloud environments.
Partner with
Product
Personas to understand feature requirements and usage patterns, aligning technical design and service selection decisions with business value and cost efficiency objectives.
Evaluate and implement commitment discount opportunities, including reserved instances, savings plans, and committed use discounts, in collaboration with
FinOps Practitioner
and
Procurement
Personas to optimize rates across the public cloud estate.
As a FinOps Finance Persona, I will…
Partner with
FinOps Practitioner
Engineering
, and
Product
Personas to understand public cloud pricing models, including consumption-based and commitment-based across IaaS and PaaS services.
Collaborate with
FinOps Practitioner
Personas to translate public cloud consumption and commitment data into financial views that support budgeting, forecasting, and variance analysis across the organization.
Use showback and chargeback insights to improve financial transparency and accountability across teams, products, and business units consuming public cloud resources.
Align commitment discount purchases and other cloud related contracts with observed workload patterns and business demand to manage financial risk, maximize savings, and maintain purchasing flexibility.
Monitor public cloud spend trends, volatility, and anomalies to support timely financial decision-making, cost governance, and escalation where needed.
Connect public cloud investment to business outcomes through unit-based metrics that inform prioritization, portfolio decisions, and executive reporting.
As a FinOps Product Persona, I will…
Partner with
FinOps Practitioner
Engineering
, and
Finance
Personas to understand how public cloud consumption supports product features, and how architectural and service selection decisions influence cost outcomes.
Use unit-based cost insights, such as cost per feature, transaction, or customer, to inform product prioritization, roadmap decisions, and trade-off discussions with
Engineering
and
Finance
Personas.
Collaborate with
Engineering
Personas to balance performance, reliability, and cost based on user and business needs, ensuring that service level expectations are aligned with the cost implications of architectural choices.
Provide input into forecasting and planning by sharing expected changes in product usage, feature adoption, and demand growth to support accurate budgeting and commitment sizing decisions.
Use showback and chargeback insights to understand public cloud cost drivers and trade-offs across products, features, and teams, supporting accountability and informed investment decisions.
Align product success metrics with public cloud unit economics to support value analysis, realization, and executive investment decisions.
As a FinOps Procurement Persona, I will…
Partner with
FinOps Practitioner
Finance
, and
Engineering
Personas to understand public cloud commercial models, including consumption-based pricing, commitment discount constructs, and enterprise agreement terms across providers.
Support commitment discount and renewal decisions by aligning contract terms with observed workload patterns, usage volatility, and growth expectations to maximize savings while maintaining commercial flexibility.
Collaborate with
FinOps Practitioner
and
Engineering
Personas to interpret public cloud usage and commitment data, identifying opportunities to optimize discount coverage, negotiate better rates, and reduce commercial risk.
Account for multi-cloud dynamics when structuring contracts and evaluating utilization risk, ensuring commitment purchases reflect the organization’s workload distribution across providers.
Provide transparency into contract terms, commitment expiration dates, and enterprise agreement conditions to support informed operational and financial decision-making across
FinOps Personas
Explore and evaluate purchasing channels, including cloud marketplaces and private pricing agreements, to identify opportunities that align with the organization’s commercial strategy and existing commitments.
Leadership
As a FinOps Leadership Persona, I will…
Partner with
FinOps Practitioners
to leverage public cloud unit economics and investment performance data to make informed strategic decisions.
Establish clear governance and ownership for public cloud consumption, ensuring that stakeholder accountability, spending authorities, and controls are defined and consistently applied across teams.
Set strategic direction for public cloud investment, aligning commitment discount purchasing, capacity planning, and provider relationships with the organization’s business and technology strategy.
Champion a culture of financial accountability across
FinOps Personas
, ensuring that cost visibility, collaborative decision-making, and value realization are recognized as shared organizational responsibilities.
Framework Domains & Capabilities
This section outlines practical considerations for applying the FinOps Framework within the context of FinOps for Public Cloud. Refer to the FinOps Framework for foundational guidance.
Understand Cost & Usage
Expand all
Collapse all
Data Ingestion
Public cloud providers produce detailed billing and usage exports that serve as the foundation for
FinOps Framework Capabilities
across the practice. Unlike other technology categories, public cloud cost and usage data is typically available at high granularity enabling detailed
Allocation
Anomaly Management
, and
Unit Economics
analysis.
However, the volume, variety, and pace of change in public cloud billing data introduce their own ingestion challenges. New services, SKUs, and pricing constructs appear regularly, requiring ongoing maintenance of ingestion pipelines and data models. Organizations operating across multiple providers must normalize data from different schemas, formats, and granularities to support unified reporting and analysis.
Adopting the
FinOps Open Cost and Usage Specification (FOCUS)
as a common schema for public cloud billing data reduces normalization effort, improves cross-provider consistency, and enables more reliable downstream analysis across Capabilities.
Common public cloud data sources include:
Provider billing exports and cost and usage reports
Resource-level utilization and performance metrics
Commitment discount utilization and coverage data
Tagging and resource metadata
Cloud provider cost management APIs
Allocation
Public cloud providers offer a range of native allocation primitives like accounts, subscriptions, projects, resource groups, and tags that give organizations more direct control over cost attribution than most other technology categories.
When consistently applied, these constructs enable accurate showback and chargeback models that reflect actual consumption across teams, products, and business units.
Despite this maturity, allocation at scale remains one of the most persistent challenges in FinOps for public cloud. Shared services, centrally managed infrastructure, and inconsistent tagging practices can obscure ownership and require allocation approaches that go beyond simple account or tag-based attribution. Untagged or mistagged resources, accounts without clear ownership, and shared networking or security services are common sources of unallocated spend that require active governance to address.
FinOps Practitioners
typically combine provider-native allocation constructs with organizational metadata such as team hierarchies, cost center mappings, and organization-specific taxonomies to build allocation models that are both accurate and meaningful to stakeholders like Finance Personas.
Key considerations for public cloud include:
Establishing and enforcing a tagging taxonomy that covers all allocable dimensions including team, product, environment, and cost center
Defining clear ownership for shared services and centrally managed infrastructure
Managing commitment discount allocation, ensuring that savings from reserved instances and savings plans are distributed according to policy guidelines to the consuming teams
Maintaining allocation accuracy as the cloud estate grows, new services are adopted, and organizational structures change
Reporting & Analytics
Public cloud environments generate rich, granular cost and usage data that supports a wide range of reporting and analytics use cases, including high-level executive dashboards to resource-level efficiency analysis. The maturity of public cloud billing exports and provider-native reporting tools means that FinOps Practitioners can establish meaningful visibility relatively quickly compared to other technology categories.
Effective reporting in public cloud requires continuous access to both financial and operational metrics, combining billing data with resource utilization, commitment discount coverage, and tagging completeness signals to support informed decision-making across Personas.
Examples of public cloud reporting metrics include:
Total and unit costs by account, service, team, product, and environment
Commitment discount utilization, coverage, and savings rates
Tagging coverage and allocation accuracy rates
Resource utilization and rightsizing opportunity signals
Anomaly indicators and spend variance against forecast
Sustainability and carbon emissions data by region and service
Temporal reporting should align operational usage data with financial reporting periods, supporting clear variance explanation, forecast accuracy tracking, and commitment burn-down visibility across the public cloud estate.
Anomaly Management
Public cloud’s on-demand nature means that spend can scale rapidly in response to workload changes, misconfigurations, or unintended usage. Effective anomaly management is essential to maintaining cost control without impeding engineering velocity, and is supported by a mature ecosystem of native alerting tools, budget controls, and third-party platforms that can detect and surface unexpected spend patterns in near real-time.
Establishing reliable anomaly detection in public cloud requires well-maintained baselines that account for expected growth, seasonal patterns, and planned workload changes. Without these baselines, practitioners risk alert fatigue from false positives or missed anomalies that go undetected until they appear on a monthly bill.
Public considerations for public cloud include:
Unexpected spikes in compute, storage, or networking spend
Unintended resource provisioning or misconfigured auto-scaling policies
Commitment discount utilization drops indicating workload changes or coverage gaps
Data transfer and egress charges inconsistent with historical patterns
Orphaned or idle resources accumulating charges without active ownership
Tagging gaps or ownership changes that obscure spend attribution
A repeatable anomaly response process that includes investigation, owner engagement, and feedback into governance guardrails helps contain financial impact and reduces the likelihood of recurrence across the public cloud estate.
Quantify Business Value
Expand all
Collapse all
Planning & Estimating
Planning and estimating in public cloud is shaped by the available services and pricing models, requiring stakeholder
Personas
to translate expected business demand into workload and architecture decisions with material cost implications.
The availability of provider pricing calculators, historical billing data, and a mature ecosystem of estimation tools makes public cloud one of the more tractable technology categories for cost estimation but accuracy still depends on the quality of demand signals and architectural assumptions provided by Engineering and Product Personas.
Key considerations for public cloud include:
Translating expected workload growth, feature demand, and user adoption into resource and service consumption estimates
Evaluating the cost implications of architectural choices, including service selection, deployment regions, and scaling configurations
Incorporating commitment discount opportunities into estimates to reflect realistic effective rates rather than on-demand pricing
Coordinating across
Engineering
Finance
, and
Procurement
Personas to align demand forecasts with purchasing cycles and enterprise agreement terms.
Forecasting
Forecasting in public cloud benefits from the availability of detailed historical billing data, resource utilization trends, and commitment discount coverage metrics that provide a strong foundation for predicting future spend. The on-demand nature of public cloud services means that forecast accuracy depends on close collaboration between
FinOps Practitioner
Engineering
, and
Product
Personas to understand the workload and demand signals that drive consumption.
Key considerations for public cloud include:
Separating stable baseline consumption from variable and seasonal workload patterns to improve forecast accuracy and reduce variance
Incorporating commitment discount coverage and expiration timelines into spend forecasts to reflect realistic effective rates
Accounting for the pace of service adoption, new workload onboarding, and architectural changes that can materially shift consumption trajectories
Aligning forecast cadence with business planning cycles, budget reviews, and commitment purchasing windows to support timely financial decision-making
Maintaining forecast accuracy metrics and using variance analysis to continuously improve forecasting models and demand signal quality
Budgeting
Budgeting for public cloud requires coordinating consumption-based and commitment-based spend across a dynamic and often distributed estate, ensuring that financial guardrails reflect both expected workload demand and the organization’s commercial strategy. Public cloud budgets must account for the elastic nature of consumption, where spend can scale rapidly in response to business growth, new product launches, or unplanned workload changes.
Key considerations for public cloud include:
Establishing budgets at meaningful organizational levels like account, team, product, or business unit to support accountability and enable timely variance detection
Incorporating commitment discount purchases into budget planning to reflect effective rates rather than on-demand pricing, and accounting for commitment expiration and renewal cycles
Aligning budget cycles with enterprise planning processes, commitment purchasing windows, and provider enterprise agreement terms
Defining budget thresholds and alerting mechanisms that enable proactive governance without impeding engineering velocity
Coordinating with
Finance
and
Procurement
Personas to ensure that public cloud budgets reflect both operational demand and strategic commercial commitments.
KPI & Benchmarking
KPI & Benchmarking for public cloud focuses on measuring the efficiency, accountability, and business value of cloud investment across the estate. The maturity of public cloud billing data and tooling means that practitioners have access to a wide range of metrics, making it important to prioritize KPIs that are meaningful to the decisions being supported rather than tracking every available signal.
Key considerations for public cloud include:
Cost efficiency metrics such as commitment discount utilization, coverage rates, and savings against on-demand pricing
Allocation and governance signals including tagging coverage rates and percentage of spend attributed to a business owner
Unit cost metrics that connect public cloud spend to business outcomes such as cost per customer, transaction, or product feature
Forecast accuracy and budget variance rates that reflect the health of financial planning processes
Sustainability metrics including carbon emissions by region and service to support environmental reporting and workload placement decisions
Unit Economics
Unit Economics in public cloud focuses on connecting cloud investment to business outcomes by establishing the cost of delivering a product, feature, service, or transaction. The granularity of public cloud billing data makes it one of the most tractable technology categories for building meaningful unit cost models, provided that allocation accuracy and tagging standards are sufficiently mature to support reliable attribution.
Key considerations for public cloud include:
Defining the right unit of measure for each product or service, such as cost per customer, transaction, request, or active user, that is meaningful to business stakeholders
Combining resource-level billing data with product and operational telemetry to build unit cost models that reflect true consumption
Tracking unit cost trends over time to distinguish efficient scaling from cost growth that outpaces business value
Using unit economics insights to inform architectural decisions, commitment purchasing strategies, and product prioritization
Optimize Cost & Usage
Expand all
Collapse all
Architecting & Workload Placement
Architecting and workload placement decisions in public cloud have direct and material cost implications. The breadth of available IaaS and PaaS services across multiple providers and regions means that placement decisions involve trade-offs across cost, performance, reliability, and sustainability that benefit from collaboration across all
FinOps Personas
Key considerations for public cloud include:
Evaluating service selection trade-offs across managed services, containerized workloads, and serverless options, considering both unit cost and operational overhead
Incorporating regional cost and carbon emissions differences into workload placement decisions to optimize for both financial and sustainability objectives
Assessing multi-cloud placement strategies to balance commercial flexibility, resilience, and cost efficiency across providers
Ensuring that architectural decisions account for data transfer and egress costs, which can materially influence total cost of ownership in public cloud
Contributing cost and commercial insight from FinOps  into architecture review processes to ensure that cost efficiency is considered alongside performance and reliability objectives
Usage Optimization
Usage Optimization in public cloud focuses on reducing unnecessary consumption while maintaining performance and reliability. The breadth and on-demand nature of public cloud services creates both significant optimization opportunity and ongoing governance challenges, as resources can be provisioned quickly and accumulate waste if not actively managed.
Key considerations for public cloud include:
Rightsizing compute, storage, and database resources by matching provisioned capacity to actual utilization patterns across workloads and environments
Identifying and eliminating idle, orphaned, or underutilized resources including unattached storage volumes, unused load balancers, and inactive environments
Implementing scheduling and auto-scaling policies that align resource availability with actual demand, reducing waste during low-usage periods
Optimizing data transfer and egress patterns to reduce unnecessary cross-region or cross-provider data movement costs
Establishing continuous optimization workflows that surface and prioritize opportunities across
Engineering
and
Product
Personas, rather than treating optimization as a one-time exercise.
Rate Optimization
Rate Optimization in public cloud centers on reducing the effective rate paid for consumption through deliberate use of commitment discounts, and negotiated pricing. Public cloud offers one of the richest rate optimization landscapes of any technology category, with a variety of commitment constructs, enterprise agreement options, and marketplace purchasing channels that reward planned and collaborative purchasing decisions.
Key considerations for public cloud include:
Selecting and sizing commitment discount constructs such as reserved instances, savings plans, and committed use discounts to maximize savings
Monitoring commitment discount utilization and coverage rates continuously to identify opportunities to adjust, exchange, or consolidate commitments as workloads evolve
Coordinating commitment purchasing decisions across
Engineering
Finance
, and
Procurement
Personas to ensure that discount coverage reflects both current consumption and forward-looking demand signals
Leveraging enterprise agreements, private pricing arrangements, and cloud marketplace purchasing channels to negotiate favorable rates aligned with the organization’s commercial strategy
Licensing & SaaS
Public cloud environments frequently incorporate a mix of provider-native licensing, third-party software deployed on cloud infrastructure, and SaaS products procured through cloud marketplaces. Managing this combination requires coordination across FinOps Practitioner, Procurement, and ITAM
Personas
to maintain visibility, optimize entitlements, and ensure that licensing costs are accurately reflected in the overall public cloud cost picture.
Key considerations for public cloud include:
Managing bring-your-own-license (BYOL) arrangements and hybrid licensing models for software deployed on public cloud infrastructure, ensuring entitlements are accurately tracked and optimized
Evaluating cloud marketplace purchases for alignment with existing enterprise agreements, and organizational procurement policies
Identifying and eliminating redundant or underutilized software licenses deployed across public cloud environments, including development, test, and staging environments that may carry unnecessary licensing overhead
Coordinating with ITAM and Procurement
Personas
to maintain a unified view of software entitlements across on-premises and public cloud deployments, avoiding compliance risk and duplicate spend.
Sustainability
Public cloud providers offer increasingly detailed carbon emissions reporting at the region, service, and account level, giving FinOps Practitioners more direct visibility into the environmental impact than most other technology categories. This visibility creates an opportunity to incorporate sustainability signals into workload placement, architecture, and optimization decisions to support organizational environmental objectives.
Key considerations for public cloud include:
Using provider-reported carbon emissions data to understand the environmental impact of public cloud consumption across regions, services, and accounts
Incorporating region-level carbon intensity and renewable energy availability into workload placement and architecture decisions to reduce emissions alongside cost
Connecting public cloud sustainability metrics to organizational Scope 1, 2, and 3 emissions reporting frameworks to support environmental compliance and disclosure requirements
Manage the FinOps Practice
Expand all
Collapse all
FinOps Practice Operations
FinOps practice operations within public cloud benefits from a mature ecosystem of tooling, established community best practices, and a well-defined operating model through the
FinOps Framework
. As public cloud estates grow in scale and complexity spanning multiple providers, accounts, and teams, FinOps practices must evolve to maintain visibility, accountability, and governance across an increasingly distributed environment.
Key considerations for public cloud include:
Establishing clear operating processes, including regular reporting cadences, optimization reviews, and commitment purchasing cycles that keep FinOps activities aligned with business planning and engineering delivery cycles
Scaling governance processes to match the pace of public cloud adoption, ensuring that tagging standards, budget controls, and anomaly response processes remain effective as the estate grows
Coordinating FinOps activities across multiple cloud providers, accounts, and teams to maintain a unified practice that supports consistent decision-making and accountability
Investing in automation to reduce the operational overhead of routine FinOps activities such as tagging enforcement, anomaly detection, and commitment utilization monitoring, freeing FinOps Practitioners to focus on higher-value analysis.
FinOps Education & Enablement
Public cloud’s range of services, pricing models, and optimization levers means that effective education and enablement is a continuous and high-value practice investment. Education about best practices is essential to building a FinOps practice that scales as cloud adoption grows, ensuring that all stakeholder Personas understand how their decisions influence cost outcomes.
Key considerations for public cloud include:
Building shared understanding of public cloud pricing models, commitment discount constructs, and optimization levers across Engineering, Product, and Finance
Personas
to support informed, distributed decision-making
Developing role-specific enablement that connects FinOps concepts to the day-to-day responsibilities of each Persona, rather than delivering generic cloud cost awareness training
Establishing feedback loops between FinOps Practitioners and Engineering teams that reinforce cost-aware development practices, including tagging standards, rightsizing habits, and anomaly response behaviors
Leveraging the
FinOps Foundation
‘s community resources, training programs, and certification pathways to build organizational FinOps best practices
Governance, Policy & Risk
Governance in public cloud requires balancing the need for financial controls and accountability with the engineering velocity and innovation that public cloud enables. The scale and on-demand nature of public cloud means that manual governance approaches are unmanageable, making policy automation and proactive risk management essential components of a mature FinOps practice.
Key considerations for public cloud include:
Defining and enforcing policies for resource provisioning, tagging standards, and spending authorities that reflect the organization’s risk tolerance and financial accountability requirements
Automating governance controls such as budget alerts, tagging enforcement, and resource lifecycle policies to maintain consistent oversight across a large and rapidly evolving public cloud estate
Managing commitment discount risk by monitoring utilization, coverage gaps, and expiration timelines to avoid stranded commitments or unexpected on-demand exposure
Coordinating governance practices across multiple cloud providers and accounts to ensure consistent policy application and reduce the risk of shadow cloud spending
Invoicing & Chargeback
The granularity and volume of public cloud billing data, with line items spanning hundreds or thousands of services, SKUs, and resources across accounts and regions, creates both the opportunity to build highly accurate chargeback models and the operational challenge of maintaining them at scale. Adding to the challenge is reconciling billing data with public cloud provider invoicing which is typically summarized and delivered monthly.
Key considerations for public cloud include:
Translating provider invoices and billing exports into internal chargeback or showback models that accurately reflect consumption by team, product, cost center, or business unit
Incorporating commitment discount savings into chargeback models in a way that fairly distributes the financial benefit of centrally purchased discounts to the teams whose workloads generated the savings
Reconciling invoice data with internal tagging, account hierarchy, and organizational metadata to maintain allocation accuracy and support a reliable audit trail
Coordinating with Finance and Procurement
Personas
to ensure that marketplace purchases, enterprise agreement true-ups, and multi-provider invoices are consistently incorporated into the organization’s financial reporting.
FinOps Assessment
Regular assessment helps organizations understand the current state of their FinOps for Public Cloud practices, identify opportunities for improvement, and prioritize investments in Framework
Capabilities
that deliver the greatest business value, and a well-defined operating model through the
FinOps Framework
to guide evaluation.
Key considerations for public cloud include:
Evaluating the maturity of core Capabilities including Data Ingestion, Allocation, Forecasting, and Rate Optimization against the organization’s business priorities and desired outcomes across
FinOps Scopes
Assessing the effectiveness of governance processes, including tagging coverage, budget control adherence, and anomaly response times, as indicators of practice health across the public cloud estate
Including Engineering, Product, Finance, and Procurement
Personas
in assessment activities to ensure that
FinOps Maturity
is evaluated holistically across the practice
Using assessment outcomes to define a prioritized roadmap of
Capability
improvements that are aligned to business objectives and the pace of public cloud adoption
Intersecting Disciplines
FinOps for public cloud intersects with teams whose responsibilities and activities directly influence public cloud cost, governance, and value outcomes. Effective coordination across these disciplines is essential to maintaining a well-governed public cloud practice.
Key considerations for public cloud include:
Collaborating with ITAM and Procurement
Personas
to maintain visibility into software licensing, enterprise agreements, and marketplace purchases that influence public cloud commercial strategy and total cost of ownership
Coordinating with ITFM
Personas
to ensure that public cloud cost and usage data is consistently integrated into broader technology financial management processes, supporting accurate organizational reporting and investment decisions
Engaging with Security and Compliance teams to align governance policies, resource provisioning controls, and data access standards across the public cloud estate
Partnering with Sustainability teams to incorporate carbon emissions data and environmental objectives into workload placement, architecture, and optimization decisions, ensuring that sustainability goals are pursued collaboratively
How to Calculate Percentage of Costs Associated with Untagged Cloud Resources
Watch the session
Unit Economics Playbook: Calculate the Unit Cost
Measure of Success & KPIs
Data Integration and Timeliness
Provider billing exports, usage data, and resource utilization are ingested with sufficient frequency to support near real-time visibility and alerting across the public cloud estate.
Cost and usage data from multiple public cloud providers is normalized into a consistent reporting model, using open schemas such as
FOCUS
to support cross-provider interpretation and analysis.
Data quality controls exist, including handling of new service and SKU introductions, schema changes, and tagging completeness checks that maintain allocation accuracy over time.
Reporting and Financial Transparency
Tagging coverage and allocation policies are sufficiently mature to enable accurate cost attribution across teams, products, business units, and environments.
Untagged, mistagged, and unowned resources are detectable and actively remediated, with a measurable and improving cost attribution rate tracked over time.
Shared resources, services, and centrally managed infrastructure are handled with clear split rules and repeatable reallocation models, so costs do not remain permanently unattributed across the public cloud estate.
Demand and Forecast Accuracy
Forecast accuracy is tracked against agreed variance thresholds and updated as workload patterns, new service adoption, and architectural changes shift public cloud consumption trends.
Forecast drivers are explainable in public cloud terms, such as resource growth, scaling behavior, workload onboarding, and commitment discount coverage changes.
Consumption trends are visible across key public cloud service categories like compute, storage, database, and networking, supporting clearer planning, variance explanation, and commitment purchasing decisions.
Usage and Cost Efficiency
Unit cost measures are tracked over time, such as cost per transaction, customer, or product feature, to support benchmarking and inform prioritization and investment decisions.
Efficiency signals highlight optimization opportunities, including idle or orphaned resources, underutilized compute and storage, and unnecessary data transfer and egress costs across the public cloud estate.
Commitment discount utilization and coverage rates are visible and actively monitored, supporting configuration decisions, reducing on-demand exposure, and maximizing savings across the public cloud estate.
Anomaly Detection and Response
Cost spikes are identifiable at a granular level, including unexpected increases in spend, and can be traced to specific resources, accounts, or teams.
Anomalies can be correlated with workload changes, deployment events, and scaling activity to distinguish planned consumption from unexpected or unintended cost drivers.
A repeatable response process exists, including investigation, owner engagement, and feedback into governance guardrails to reduce the likelihood of recurrence across the public cloud estate.
Sustainability Discipline
Public cloud provider-reported carbon emissions data is ingested and integrated into cost and usage reporting, enabling visibility into the environmental impact of public cloud consumption across accounts, services, and regions.
Region-level carbon intensity and renewable energy availability are actively considered in workload placement and architecture decisions, with sustainability metrics tracked alongside cost efficiency outcomes.
Public cloud sustainability data is connected to organizational Scope 1, 2, and 3 emissions reporting processes, supporting environmental compliance, disclosure requirements, and progress toward organizational sustainability objectives.
Unit Economics
Unit cost models exist for key products, services, and business outcomes. They are regularly updated to reflect changes in public cloud consumption and organizational structure.
Unit cost trends are tracked over time to distinguish efficient scaling from cost growth that outpaces business value, supporting informed prioritization and investment decisions.
Public cloud unit economics insights are actively used to inform architectural decisions, commitment purchasing strategies, and product roadmap prioritization, connecting cloud investment to measurable business outcomes.
KPIs
Cost Optimization Index (COIN)
Method of objective scoring based on resource cost efficiency.
Cost Optimization Index (COIN)
The Cost Optimization Index score, or COIN, is a quantitative measure designed to assess cloud cost efficiency. COIN applies to any breakdown of infrastructure cost: Team, service, account, etc. COIN is calculated using the savings opportunity and overall total cost for the infrastructure in question to assess efficiency. Think of it as the inverse of waste.
Formula
COIN Score = [1 – (Total Savings Opportunity / Total Cost)] * 100
The resulting score from 0-100 serves as an objective benchmark for cost efficiency. Total Cost is based on the aggregate cost of any relevant scope of infrastructure and measured in any desired currency.
Total Savings Opportunity is based on the sum of individual Savings Opportunities. Savings Opportunities are usage patterns within that scope of infrastructure which indicate expected areas of inefficiency and waste. These are calculated as projected savings in the same currency as Total Cost. Each Savings Opportunity will need it’s own cost model to identify potential savings.
This scoring system can help:
Identify areas to save money within run rate
Compare teams, services, org or organizations cost efficiency
Identify priority savings opportunities to target across the broader organization
Example:
Acme Corp has identified 3 potential areas of savings which they wish to drive through their organization.
Savings Area #1 is defined as the use of older generation storage technologies.
AcmeCorp’s FinOps team has identified a 20% savings for each dollar spent on legacy storage by upgrading to the latest generation.
Savings opportunity #1 is calculated as 20% multiplied by the current spend on legacy storage.
Savings Opportunity = (Legacy Gadget Spend) * 20%
Savings Area #2 is defined as low CPU utilization.
AcmeCorp’s FinOps team has identified a 30% P95 utilization target for compute.
Savings Opportunity #2 is calculated as the portion of infrastructure spend wasted on resources below that 30% benchmark.
Savings Opportunity = Compute spend * (1- (P95 Utilization (%) / 30%)
Savings Area #3 is defined as turning on a vendor’s network cost-savings option.
AcmeCorp’s FinOps team has identified a 25% savings from turning on the vendor feature.
Savings Opportunity = (Network Spend) * 25%
For a given Team Rocket, the FinOps team has calculated the following:
Team Rocket’s Total Cost = $500
Legacy Storage Spend = $100
Compute Spend = $100
P95 Compute Utilization = 25%
Network Spend = $100
First, calculate the expected savings from each savings opportunity.
#1 – Storage = $100 * 20% = $20
#2 – CPU utilization = $100 * (1 – 25%/30%) = $100 * .1666 = $16.67
#3 – Network = $100 * .25 = $25
Next, calculate the total savings opportunity by summing the individual savings opportunities:
$20 + $16.67 + 25 = $61.67
The COIN Score for Team Rocket then is calculated:
1 – ($61.67 / $500) =
1 – .12334 =
87.66
Team Rocket’s COIN score reflects that ~12% of their spend is known waste and that overall, based on their aggregate spend and defined patterns of waste, their spend is ~88% efficient.
Data Sources:
CSP or Vendor Billing Report
Resource Utilization Metric Data Store
Related Capabilities
Usage Optimization
Rate Optimization
Time to Achieve Business Value
Measures the time it takes to achieve measurable business value from AI initiatives. This KPI uses a “breakeven point” of doing a function with AI versus the cost of performing it some other way (like with labor). It provides the awareness around the forecasted days to achieve the full business benefit vs the actual business
Time to Achieve Business Value
Measures the time it takes to achieve measurable business value from AI initiatives. This KPI uses a “breakeven point” of doing a function with AI versus the cost of performing it some other way (like with labor). It provides the awareness around the forecasted days to achieve the full business benefit vs the actual business results achieved and understanding the opportunity costs and value per month.
Formula
Time to Value (days) = Total Value associated with AI Service / daily Cost of Alternative solution
Candidate Data Sources:
API usage reports
Dashboards from AI platforms
Logs from AI platforms
Cloud billing data
Example:
If an AI initiative starts on January 1, 2024, and the model is successfully deployed on April 1, 2024, the Time to Value is: April 1, 2024−January 1, 2024=3 months.
Forecast to get $100k/mo of business within 1 month, but it actually took 5 months and only achieved $50k/mo business benefit, 5 months was the time to business value metric to track and seek to improve.
Related Capabilities
Forecasting
Unit Economics
Reporting & Analytics
Planning & Estimating
Related Assets
GenAI FinOps vs. Cloud FinOps: Similar Roots, Different Challenges
GenAI FinOps: How Token Pricing Really Works
How to Build a Generative AI Cost and Usage Tracker
Resource Utilization Efficiency
Measures the efficiency of hardware resources like GPUs and TPUs during AI training and inference. This KPI identifies underutilized or over-provisioned resources, ensuring cost savings, and tracks the performance of autoscaling mechanisms.
Resource Utilization Efficiency
Measures the efficiency of hardware resources like GPUs and TPUs during AI training and inference. This KPI identifies underutilized or over-provisioned resources, ensuring cost savings, and tracks the performance of autoscaling mechanisms.
Formula
Resource Utilization Efficiency = Actual Resource Utilization / Provisioned Capacity​
Candidate Data Sources:
API usage reports
Dashboards from AI platforms
Logs from AI platforms
Cloud billing data
Example:
If the actual resource utilization is 800 GPU hours and the provisioned capacity is 1,000 GPU hours, the resource utilization efficiency is: 800/1,000 = 0.8 or 80%
Related Capabilities
Reporting & Analytics
Data Ingestion
Usage Optimization
Unit Economics
Related Assets
GenAI FinOps vs. Cloud FinOps: Similar Roots, Different Challenges
GenAI FinOps: How Token Pricing Really Works
How to Build a Generative AI Cost and Usage Tracker
Anomaly Detection Rate
Measures the frequency and cost impact of anomalies in AI spending, such as sudden cost spikes or unexpected usage patterns. This KPI enables proactive identification and mitigation of runaway costs.
Anomaly Detection Rate
Measures the frequency and cost impact of anomalies in AI spending, such as sudden cost spikes or unexpected usage patterns. This KPI enables proactive identification and mitigation of runaway costs.
Formula
Total Cost of Anomaly Spikes / Total AI Spend = Anomaly Cost %
where (adjust for your needs):
Green (< 2%): Healthy. Normal fluctuations.
Yellow (2-7%): Warning. Minor anomaly trend
Red (> 7%): Critical. You have a “runaway” costs.
Candidate Data Sources:
API usage reports
Dashboards from AI platforms
Logs from AI platforms
Cloud billing data
Related Capabilities
Anomaly Management
Reporting & Analytics
Data Ingestion
Related Assets
GenAI FinOps vs. Cloud FinOps: Similar Roots, Different Challenges
GenAI FinOps: How Token Pricing Really Works
How to Build a Generative AI Cost and Usage Tracker
Percentage of CSP Cloud Carbon that is Tagging Policy Compliant
This KPI measures the amount of compliance for cloud sustainability tagging.
Percentage of CSP Cloud Carbon that is Tagging Policy Compliant
This KPI measures the amount of compliance for cloud sustainability tagging, and requires an established organizational tagging policy.
The sophistication of determining what acceptable tag criteria are, and the stringency of the KPI should evolve with the organization’s FinOps maturity.
Formula
(Total emissions Associated with Tagging Policy Compliant CSP Cloud Resources During a Period of Time / Total CSP Cloud Emissions During a Period of Time) x 100
Data Sources:
CSP billing data,
Cloud Console,
carbon emission data source
Related Capabilities
Sustainability
Intersecting Disciplines
Related Assets
Cloud Sustainability and Its Intersection with FinOps
Percentage of Costs Associated with Untagged CSP Cloud Resources
Calculate percentage of untagged cloud resources using an established organizational tagging policy.
Percentage of Costs Associated with Untagged CSP Cloud Resources
Calculate percentage of untagged cloud resources using an established organizational tagging policy.

The sophistication of determining what is acceptable tag criteria and the stringency of the KPI should evolve with the organization's FinOps maturity.
Formula
(Total Effective Costs Associated with Untagged CSP Cloud Resources During a Period of Time / Total CSP Effective Cost During a Period of Time) x 100
Note: Not all CSP Cloud Resources can be tagged.
Data Sources:
CSP Billing Data
Related Capabilities
Allocation
Related Assets
How to Calculate Percentage of Costs Associated with Untagged CSP Cloud Resources
Fixed Percentage Apportionment Validation
Method of apportioning shared costs based on Fixed Percentage.
Fixed Percentage Apportionment Validation
Method of apportioning shared costs based on Fixed Percentage.
Formula
Total apportionment of shared Effective Costs / Total shared  Effective costs
Example: ACME Global Limited shared effective cost for the month of July was $200,000 on cloud monitoring tools, security tools, cloud costs management tools, CSP (Cloud Service Provider) Premium Support Fees. ACME Global Limited has 4 Cost centers/Product/Department, so the fixed percentage is 25%.
Finance = 25% x $200,000 = $50,000
Logistics = 25% x $200,000 = $50,000
Commercial = 25% x $200,000 = $50,000
Marketing = 25% x $200,000 = $50,000 =
($50,000 +$50,000+$50,000 +$50,000) / $200,000 x 100 = 100%
Data Sources:
CSP Billing Data
Internal Finance Metrics
Related Capabilities
Allocation
Cloud Spend Percentage of Recurring Revenue
Track cloud spend relative to company revenue, as a percentage.
Cloud Spend Percentage of Recurring Revenue
Leadership and Finance can use this KPI to measure actual cloud expenses vs. company revenue, on a monthly and/or annual basis - formula options for both are provided below.
Formula
(Monthly total cloud invoice amount / Monthly Recurring Revenue)
and/or
(Annual total cloud invoice amount / Annual Recurring Revenue)
Data sources:
CSP Billing data,
CSP FOCUS files
Related Capabilities
Reporting & Analytics
Planning & Estimating
KPIs & Benchmarking
Unit Economics
Forecast Drift Rate
Evaluate how cloud infrastructure forecasts change over time due to various factors.
Forecast Drift Rate
Evaluates how cloud infrastructure forecasts change over time due to various factors such as priority shifts, workload variations, rightsizing, and CUD impacts.

Though percentage variance is prioritized, measuring in dollars is also valuable. Organizations set their own standards for acceptable variances.
Formula
((New Forecasted Cloud Infrastructure Spend – Previous Historic Forecasted Cloud Infrastructure Spend) / Previous Forecasted Cloud Infrastructure Spend)
Data Sources:
CSP Billing Data
Organizational forecast documents
Related Capabilities
Forecasting
Forecast Accuracy Rate (Spend)
This metric compares forecasted vs. actual cloud spend over a specific period (e.g., day, month, quarter).
Forecast Accuracy Rate (Spend)
This metric compares forecasted vs. actual cloud spend over a specific period (e.g., day, month, quarter).

While percentage variance is the primary metric, dollar differences can also be informative. Each organization defines its acceptable variance.
Formula
((Forecasted Public Cloud Spend – Actual Public Cloud Spend) / Forecasted Public Cloud Spend)
Data Sources:
CSP Billing Data
Organizational forecast documents
Related Capabilities
Forecasting
Forecast Accuracy Rate (Usage)
Compares forecasted vs. actual cloud usage (vCPUs, Memory, etc) over a specific period (e.g., day, month, quarter).
Forecast Accuracy Rate (Usage)
Compare forecast vs. actual cloud usage (serviceName, serviceCategory, serviceSubCategory, etc) over a specific period (e.g., day, month, quarter).

This should be specific to service types (ex, measure by a specific serviceName, SKU, serviceCategory, serviceSubCategory etc). Percent variance is recommended, although the scale of usage should also be considered. Each organization defines its acceptable variance
Formula
Formula : For specific ServiceName or ServiceCategory or SKU
((Forecasted Resource Utilization – Actual Resource Utilization) / Forecasted Resource Utilization)
Data Sources:
CSP Billing Data
Organizational forecast documents
Related Capabilities
Forecasting
Sustainability
Related Assets
Exploring Cloud Cost Forecasting
Accurate Cloud Forecasts
How to Forecast AI Services Costs in Cloud
Percent of Compute Spend Covered by Commitment Discounts
Measures the percentage of compute cost (excluding Spot) covered by commitment discount for the previous month.
Percent of Compute Spend Covered by Commitment Discounts
Measures the percentage of compute effective cost (excluding Spot) covered by commitment discount for the previous month.
Formula
Compute Cost after Commitment Discount / On-Demand Compute Cost
Data Sources:
CSP Billing Data
Related Capabilities
Rate Optimization
Effective Savings Rate Percentage
Return on investment metric of all commitment discounts.
Effective Savings Rate Percentage
Return on investment metric of all commitment discounts by commitmentDiscountId / commitmentDiscountName, commitmentDiscountStatus, commitmentDiscountType, etc..
Formula
Option 1: (CB Discount Savings – Cost to achieve CB Discount Savings) / Compute On-Demand Equivalent Spend
Option 2: 1 – (Actual Spend with Discounts / Equivalent Spend at On Demand Rate)
Data Sources:
CSP Billing Data
Related Capabilities
Rate Optimization
Related Assets
How to Calculate Effective Savings Rate (ESR)
See the
FinOps KPI Library
for a comprehensive list of KPIs that could be considered for this technology.
FOCUS Alignment
The
FinOps Open Cost and Usage Specification
(FOCUS) is an open specification that defines clear requirements for public cloud providers to produce consistent cost and usage datasets. FOCUS makes it easier to understand all technology spending so you can make data-driven decisions that drive better business value.
Among technology categories, public cloud has the most comprehensive FOCUS adoption, with
all major providers producing FOCUS-aligned cost and usage exports
For detailed information about the FOCUS Columns and use cases for public cloud see:
Introducing FOCUS 1.2 – What is new for Public Cloud
FOCUS Cost and Usage Columns
FOCUS Contract Commitment Columns
FOCUS Use Case Library
Virtual currencies therefore sit between raw technical usage (bytes processed, seconds elapsed) and the dollar amount you ultimately pay, enabling the vendor to adjust pricing simply by changing the unit-to-cash conversion rate.
Example: Snowflake
The below table shows what consuming 25 Snowflake credits looks like with the relevant 1.2 columns. This example shows the pricing currency in USD (how Snowflake prices) and the billing currency in EUR.
The exchange rate for the sake of this example is 1 USD = 1.008 EUR (FX rate used in the invoice)
Column
Example Value
Purpose / Mapping
ProviderName
Snowflake
Identifies the SaaS/PaaS source
ChargePeriodStart
2025-05-14T00:00:00Z
Beginning of the hour
ChargePeriodEnd
2025-05-14T01:00:00Z
End of the hour
ConsumedQuantity
25
Number of credits consumed
ConsumedUnit
Credit
Unit identification
New pricing-currency fields
PricingCurrency
USD
Currency in which Snowflake invoices the account
PricingCurrencyListUnitPrice
List price per credit
PricingCurrencyContractedUnitPrice
2.7
Discounted unit price from negotiated rate
PricingCurrencyEffectiveCost
67.5
25 credits * 2.70 USD
Existing billing-currency fields
BillingCurrency
EUR
Invoice delivered in EUR
ListCost
75.6
Converted from 75.00 USD at 1.008 EUR
EffectiveCost
67.95
Converted from 67.50 USD at 1.008 EUR
Browse all FOCUS columns using the
FOCUS Column Library
and explore use cases using the
FOCUS Use Case Library
FinOps for Public Cloud Tools and Service Providers
Explore FinOps tools, training, and service providers that help FinOps Practitioners successfully apply the FinOps Framework and best practices for this Scope.
Show FinOps for Public Cloud Tools and Service Providers in the FinOps Landscape.
Learn the fundamentals
Level up your knowledge with FinOps Certified Practitioner
Get started
Technology Categories
FinOps for AI
FinOps for SaaS (Software-as-a-Service)
FinOps for Data Cloud Platforms
FinOps for Data Center
Related Assets
Building a FOCUS Data Export Pipeline for Alibaba Cloud
How Google Cloud Invests in FOCUS and GenAI to Drive the Future of FinOps
AWS Doubles Down on Data Granularity and FOCUS for Faster Decision-Making
Oracle Cloud Supports FOCUS to Level the Cost and Usage Billing Data Playing Field
Microsoft on FOCUS Improving Understanding of Consumption-Based Cloud Spend, feat Srivatsan Kidambi
FinOps X Sessions
Multi-Cloud and On-prem Strategy Leveraging FOCUS™
Make Suggestions
Suggest a Resource