Microsoft's Cloud Adoption Framework (CAF) and FinOps are both concerned with getting value from Azure, but they operate at very different levels. CAF is an organisation-wide framework that guides the entire journey of adopting cloud — from building the business case through to running workloads at scale. FinOps is a practice focused specifically on financial accountability for cloud spend and ensuring value and return on investment.
The relationship between them is less about one informing the other at design time (as with WAF) and more about CAF creating the structural conditions that make FinOps possible. The decisions you make following CAF guidance — how subscriptions are organised, how landing zones are structured, how governance policies are applied — either enable or hinder effective FinOps from that point forward.
What the Cloud Adoption Framework Covers
CAF is structured around six methodologies that represent the full cloud adoption lifecycle:
Methodology | What it addresses |
|---|---|
Strategy | Define the business justification for cloud adoption, expected outcomes, and motivations. Establishes why you're adopting cloud and what success looks like financially and operationally. |
Plan | Build actionable adoption plans aligned to business outcomes. Includes digital estate assessment, skills readiness, and a cloud adoption roadmap. |
Ready | Prepare the Azure environment — landing zones, subscription design, management group hierarchy, networking, and identity. The structural decisions made here have long-term consequences for cost management. |
Adopt — Migrate | Move existing workloads to Azure. Covers assessment, migration tooling, and optimisation of migrated workloads. |
Adopt — Innovate | Build new cloud-native capabilities. Customer feedback loops, modern application development, AI and data platforms. |
Govern | Establish governance policies across five disciplines: Cost Management, Security Baseline, Resource Consistency, Identity Baseline, and Deployment Acceleration. |
Manage | Operate the cloud environment — monitoring, business continuity, workload operations, and continuous optimisation. |
CAF is Microsoft-specific guidance but covers organisational, cultural, and process concerns well beyond Azure configuration. It is the broadest of the three major Microsoft frameworks (alongside WAF and the Security Development Lifecycle) in scope and ambition.
Where CAF and FinOps Overlap and Diverge
Dimension | Cloud Adoption Framework | FinOps |
|---|---|---|
Scope | Organisation-wide cloud adoption journey | Financial management of cloud spend specifically |
When it applies | Throughout the adoption journey — particularly influential at the start | Continuously — from first spend onwards |
Who leads it | Cloud strategy team, cloud centre of excellence, architects | Cross-functional — engineering, finance, business leadership |
Cost coverage | Cost Management governance discipline — policies, guardrails, accountability structures | Full operational practice — visibility, allocation, commitment discounts, anomaly detection, unit economics |
Structural decisions | Subscription design, management group hierarchy, landing zones — directly affects how cost is attributed | Operates within the structure CAF creates — but depends on it being set up well |
Governance | Broad — security, identity, resource consistency, cost, deployment | Cost governance specifically, including cultural accountability |
Migration guidance | Detailed — assessment, tooling, waves, optimisation | Not covered |
Commitment discounts | Mentioned as an optimisation pattern | Full lifecycle — purchase strategy, utilisation monitoring, renewal management |
Cloud agnostic? | No — Azure-specific | Yes — applies across cloud providers |
The most important relationship: CAF creates the structural foundation that FinOps depends on. If your landing zone design, subscription hierarchy, and tagging policies are well-constructed following CAF guidance, FinOps has a solid base to work from. If those structural decisions were made poorly or ignored, FinOps teams spend significant effort working around structural limitations rather than delivering cost optimisation.
CAF's Cost Management Governance Discipline
Within CAF's Govern methodology, the Cost Management discipline is where the framework comes closest to FinOps. It covers:
Cost accountability policies — defining which teams are responsible for which costs, and establishing the expectation that cost visibility comes with ownership responsibility
Budget policies — setting spending limits at subscription and resource group level, and defining what happens when those limits are approached
Cost reporting cadence — establishing regular cost reviews as part of operational governance, not just a finance activity
Optimisation triggers — defining what cost signals should trigger architectural reviews or rightsizing exercises
Tagging enforcement — using Azure Policy to enforce resource tagging as a prerequisite for cost attribution
CAF's Cost Management discipline describes what good governance looks like at a policy level. FinOps provides the operational practice to actually execute against those policies day to day. Both are needed — governance without operational practice is just documentation, and operational practice without governance is inconsistent and hard to sustain.
Landing Zones — The Most Critical Intersection
CAF's landing zone guidance is the most practically important area for FinOps practitioners to understand. A landing zone is the configured Azure environment into which workloads are deployed — it includes the subscription structure, management group hierarchy, networking topology, identity model, and governance policies. Getting landing zones right is a prerequisite for effective cost management at scale.
Subscription design and cost allocation
How subscriptions are structured determines how easily costs can be attributed to teams, products, or business units. A flat structure with a handful of shared subscriptions makes cost allocation difficult — shared costs need to be split, and the tagging burden is high. A well-designed subscription hierarchy that reflects your organisational or product structure makes cost attribution much more natural. CAF provides patterns for this; the FinOps requirement for clear cost attribution should be a primary input into which pattern you choose.
Management group hierarchy and commitment discounts
The management group hierarchy directly affects the scope at which Reservations and Savings Plans can be applied. A shared-scope commitment discount pools across all subscriptions under a billing account — the more subscriptions you have under one billing account, the more efficiently a shared-scope discount can be utilised. If your landing zone design results in multiple isolated billing accounts, you lose the ability to pool commitment discounts across your estate. This is a structural cost management decision that needs to be made at landing zone design time, not retrofitted later.
Tagging policy from day one
CAF landing zone guidance includes Azure Policy for enforcing tagging at resource and resource group level. From a FinOps perspective, getting tagging policy right in the landing zone means every resource that ever gets deployed is tagged correctly from the start. Trying to implement a tagging strategy after hundreds of resources exist — and after teams have developed habits that don't include tagging — is an order of magnitude harder. The landing zone is the right place to make tagging non-negotiable.
Retrofitting landing zone design is expensive. Reorganising subscriptions, moving resources between management groups, and restructuring naming conventions after workloads are in production disrupts operations and can invalidate months of cost history in your reporting tools. The FinOps team should have a seat at the table during landing zone design, not be brought in after it's done.
CAF and FinOps Through the Adoption Journey
FinOps isn't only relevant in the Govern and Manage phases — it has touchpoints throughout the CAF lifecycle:
CAF Phase | FinOps relevance |
|---|---|
Strategy | Establish the expected financial outcomes of cloud adoption. Define how success will be measured in cost terms — not just total spend, but unit economics, cost per transaction, cost per customer. Agree what "optimised" means for your organisation before spending starts. |
Plan | Develop cost forecasts for the adoption roadmap. Estimate the cost of running migrated workloads in Azure vs on-premises. Identify where commitment discounts will apply and when to start purchasing them. Build FinOps team capabilities alongside technical skills. |
Ready | Design subscription hierarchy, management group structure, and tagging policies with FinOps cost attribution in mind. This is the highest-leverage FinOps activity in the entire adoption journey — structural decisions made here persist for years. |
Migrate | Track cost of migrated workloads against on-premises baselines. Identify rightsizing opportunities before committing to reservations. Validate that migrated workloads are landing in the right subscription and with correct tags. |
Innovate | Embed cost modelling in the build process for new workloads. Use consumption-based services where appropriate but monitor that usage-based billing doesn't create surprise costs at scale. Establish cost guardrails for experimental and development environments. |
Govern | Implement and enforce the Cost Management discipline — budget policies, tag enforcement, cost review cadence, accountability. This is where FinOps governance is formalised. |
Manage | Operate the full FinOps lifecycle — Inform, Optimise, Operate. Commitment discount management, anomaly detection, team cost reviews, reservation utilisation monitoring, ongoing rightsizing. This is where FinOps is a continuous operational practice. |
Architect's Perspective
CAF is a starting point, not a blueprint
CAF provides patterns and principles, not prescriptive configurations. The subscription design pattern that works for a 500-person enterprise software company will not be right for a 50-person SaaS startup or a 5,000-person regulated bank. Use CAF to understand the considerations and trade-offs, apply the patterns that fit your context, and document the reasons you deviated from defaults where you did. The most costly mistake is following a CAF pattern that doesn't fit your organisation because it looked like the official approach.
Don't separate the landing zone team from the FinOps team
In larger organisations, the team designing landing zones and the team responsible for FinOps are often different — cloud platform engineers vs finance or FinOps practitioners. This separation means FinOps requirements don't get considered during landing zone design. Wherever possible, involve whoever will own cost management in subscription design and tagging policy decisions. The cost of getting them wrong is paid over years.
The Cloud Centre of Excellence is the natural home for FinOps governance
CAF recommends establishing a Cloud Centre of Excellence (CCoE) — a cross-functional team that owns cloud strategy, standards, and governance across the organisation. The CCoE is the natural owner of FinOps governance: it has the cross-functional authority to set cost accountability policies, enforce tagging standards, and drive adoption of cost management practices across engineering teams. If your organisation has a CCoE, FinOps should be a core part of its remit, not a separate initiative running in parallel.
Use the Manage phase to mature your FinOps practice
CAF's maturity model for the Manage phase maps well to FinOps maturity — from basic visibility through to advanced optimisation and unit economics. Don't try to implement everything at once. Start with the Inform phase of FinOps (visibility, tagging, basic allocation), establish that as normal practice, then progress to Optimise (commitment discounts, rightsizing) and Operate (full governance, chargeback, unit economics). The CAF maturity model gives you a roadmap for this progression that engineering and finance leadership can both understand.
How Can Turbo360 Cost Analyzer Help?
Turbo360 Cost Analyzer provides the operational FinOps capability that CAF's governance framework calls for but doesn't prescribe tooling for. It bridges the gap between CAF's structural guidance and the day-to-day practice of cost management.
Multi-subscription visibility across landing zones
CAF landing zones typically span many subscriptions across multiple management groups. Cost Analyzer gives you a unified view across all of them — so the cost picture isn't fragmented by subscription boundary. You can see total spend, trends, and anomalies across your entire estate from a single view, regardless of how the subscriptions are organised.
Validating tagging policy compliance
Azure Policy can enforce that tags are present, but it can't tell you whether the tag values are meaningful or whether costs are actually being attributed correctly. Cost Analyzer shows you the proportion of spend that is covered by your cost allocation tags, surfaces resources or resource groups that are untagged or incorrectly tagged, and identifies where tag policy gaps are creating blind spots in your cost attribution.
Supporting the CAF Cost Management governance discipline
CAF's Cost Management discipline requires regular cost reviews, budget monitoring, and cost accountability at team level. Cost Analyzer provides the reports and dashboards that make those reviews substantive — not a high-level total from the Azure portal, but a breakdown by team, workload, resource type, and trend that gives governance conversations real data to work with.
MSP and multi-tenant environments
For managed service providers operating CAF landing zones on behalf of customers, Cost Analyzer's multi-tenant capability means you can maintain cost visibility across customer environments without requiring direct access to each customer's billing account. This supports the kind of governance and managed cost optimisation service that CAF's MSP guidance describes.
FAQ
Do I need CAF if I'm already doing FinOps?
CAF and FinOps address different problems, so doing one well doesn't replace the other. If you're doing FinOps without CAF structure behind it — without well-designed landing zones, consistent subscription hierarchy, or enforced tagging — you'll find FinOps significantly harder than it needs to be. You'll spend energy working around structural limitations rather than optimising costs. If your Azure environment is already established, CAF is still useful for guiding improvements to your governance model and for informing decisions about restructuring or expansion.
What's the difference between CAF and WAF — and how do both relate to FinOps?
CAF operates at the organisation and adoption journey level — it guides how you set up and govern your entire Azure estate. WAF operates at the workload level — it guides how individual systems are designed and evaluated. FinOps operates at the cost management level — it's the practice that runs continuously across everything you've built. Think of it this way: CAF determines the environment workloads run in, WAF determines how those workloads are built, and FinOps manages the cost of both. All three are relevant for a mature Azure organisation; they're not alternatives to each other.
We didn't follow CAF when we set up Azure. Is it too late?
It's never too late to apply CAF principles, but the cost of retrofitting structural decisions (subscription reorganisation, management group changes, tagging policy rollout) is higher than getting them right initially. Start by assessing where your current structure diverges from CAF guidance and what the practical impact is on cost management — specifically, whether you can attribute costs clearly to teams and workloads. Fix the highest-impact gaps first: a consistent tagging policy enforced through Azure Policy is often the most impactful change you can make without reorganising subscriptions. Subscription restructuring is a longer-term improvement that needs careful planning and stakeholder alignment before execution.
How does the Cloud Centre of Excellence relate to a FinOps team?
A CCoE is a cross-functional team that owns cloud strategy, standards, and governance. A FinOps team (or FinOps practitioner) owns cloud cost management. In smaller organisations, these may be the same people. In larger ones, the FinOps function typically sits within or alongside the CCoE — the CCoE provides the governance authority and the cross-functional mandate, and FinOps provides the cost management expertise and practice. If you have a CCoE, FinOps should be a core part of its cost governance responsibility rather than a separate initiative that has to negotiate with the CCoE to get things done.
Does CAF cover multi-cloud, or is it Azure-only?
CAF is Azure-specific — Microsoft's guidance is naturally oriented toward Azure services and tooling. FinOps, by contrast, is cloud-agnostic and applies across Azure, AWS, GCP, and multi-cloud environments. If your organisation runs workloads across multiple cloud providers, CAF applies to your Azure estate specifically, while FinOps practices and tooling can span your full multi-cloud spend. The structural decisions CAF guides (subscription design, management groups, tagging) are Azure-specific, but the cost management principles FinOps builds on top of them apply regardless of which cloud the workload runs in.
Useful Resources
Related playbook pages
Microsoft resources
FinOps Foundation