Azure's February 2027 reservation exchange change: what to exchange, trade in and buy
Azure reservations bought after February 1, 2027 for savings plan services can't be exchanged. What changes, what doesn't, and a worked portfolio to act on.
Dotwork Blog
Strategy, operating models, planning and AI, from the people building Dotwork.
Azure reservations bought after February 1, 2027 for savings plan services can't be exchanged. What changes, what doesn't, and a worked portfolio to act on.
Coverage and utilization can both look healthy while commitments save little. Why finance should ask for effective savings rate, and how to check the math.
Why cloud cost data rarely matches the invoice, what FOCUS 1.4's Invoice Detail and Billing Period datasets add, and a month-end routine for controllers.
A close reading of the FinOps Framework 2026: the new Executive Strategy Alignment capability, rewritten Scopes guidance, technology categories and renames.
State of FinOps 2026 shows FinOps spreading to AI, SaaS and data centers. What its 1,192 responses support, where the method is thin, and what to tell a CIO.
Most FinOps teams report to the CTO or CIO; 8% report to the CFO. When each line fits, what it costs, and how to make a dotted line to finance work.
Requests, usage or the higher of the two? A worked cluster example, where idle and overhead belong, and what FOCUS split cost allocation does and doesn't fix.
Tags are one input to cloud cost allocation, not the whole of it. Why 100% tag compliance stalls, what can't be tagged, and a layered approach that works.
SaaS is moving into FinOps, but ITAM and procurement already hold contracts and entitlements. Who should own what, where FOCUS stands, and a working split.
Where cost belongs in architecture review: design docs, ADRs, ranged estimates and IaC guardrails, what accuracy to expect, and a short checklist to use.
Split committed, usage-driven and AI cloud spend, tie usage to business drivers, forecast in ranges and measure variance by line, with a worked example.
AWS and Google say demand outruns supply, and all three report backlogs over $550B. What that does to your bargaining power and which terms still move.
Provisioned AI capacity is billed every hour, used or not, and often breaks even only at high use. How to compare PTUs, model units and GSUs, with the math.
Product teams should hold cloud budgets once allocation puts spend in their name and shared costs have an owner. Prerequisites, guardrails and failure modes.
Cloud cost alerts reach billing admins, not the teams that can fix the spend. Set thresholds, route alerts to owners, set triage times and close each one out.
Agents suit FinOps work that is read-only or easy to undo. Commitments, policy and chargeback disputes need a person. Where the line sits, with guardrails.
A TCO frame for cloud repatriation: what to count, what the exit-fee waivers cover, what 37signals' numbers show, and when moving back doesn't pay.