CLOUDY MUSINGS

You know how this usually goes...you wind up pulling the monthly AI spend report and the number is just that...a number. "Anthropic API: $14,200." No breakdown, no context, no indication of whether your team built something genuinely useful or spent three weeks regenerating the same 8,000-token system prompt on every single call. The invoice knows what you spent. Unfortunately, your invoice (by itself) has no idea why you spent what you did. The graphic above breaks it down:

Everybody loves AI until the invoice shows up! Not the cute "we spent a few hundred dollars experimenting" invoice that gets hand-waved away as innovation spend. I mean the kind of invoice that makes finance suddenly become deeply curious about architecture decisions they previously considered engineering trivia, while operations and/or product teams insist everything is still technically a pilot, and leadership starts asking whether we can "optimize this" as though that thou

As with previous blog posts, all code can be found here! The Norns sat beside the Well of Urd weaving fate into the roots of Yggdrasil. The thread was already spun long before anyone knew how the story would end, and by the time the consequences arrived, they were simply discovering decisions that had already been made. I found myself thinking about that recently (HUGE Norse mythology fan) after yet another conversation about cloud billing, because the parallels are stronger

After spending years working across Azure, AWS, and GCP, I can tell you the most frustrating part of FinOps is rarely the optimization itself. The hard part is getting everyone in the room to agree on what the data actually means before anyone can act. Every provider exports billing differently, every tool invents its own abstraction layer on top of that, and every dashboard ends up starting with translation instead of analysis. You spend the first hour of every cost conversa

Cloud conversations still tend to start in the same place. We talk about scalability, resilience, performance, and maybe security if we are feeling disciplined. Cost usually shows up later (way later), almost like a postscript to the architecture. It is something we validate after the system is live, after usage patterns are real, and after the bill gives us a reason to care. The problem with that sequence is that by the time cost shows up, most of the meaningful decisions ha

Math IS hard and mathing isn't my strong suit. I am writing this blog because I STILL get tripped up at times with Savings Plans. You guessed it...this becomes a cheat sheet for ME in the future, too! Azure Savings Plans are one of those topics that routinely make smart people feel like they missed a prerequisite class. I see it in customer meetings, I see it in internal chats, and I definitely see it in the way people react to Azure Advisor recommendations. The issue is not

In my last post , I talked about what’s changing with Azure’s Pay-As-You-Go (PAYG) APIs and why the old Usage Details endpoint is being retired. Now it’s time to roll up our sleeves! If your FinOps automations rely on Microsoft.Commerce/UsageAggregates, you’ll need to migrate those scripts to use the Exports API or Cost Details API. This post covers the exact code changes you need to make in PowerShell and Python (typically what I see most often with my customers and what I t

If you pull cost data from Azure’s Pay-As-You-Go (PAYG) subscriptions, you might have noticed something new in Microsoft’s documentation lately: the legacy “Get Usage Details” API is being deprecated. That’s right. The familiar Consumption API that so many FinOps teams built automations around is heading for retirement. Before you start rewriting every script you own, take a breath. This change is not a disaster. It is an upgrade. Let’s talk about what is happening, why Micro

Picture this: you have built a castle in the cloud, filled with all your Azure workloads. Everything looks amazing, but is it safe, strong, and efficient? Will it handle a sudden rush of traffic or unexpected outages? The Azure Well-Architected Review is Microsoft’s framework to provide "best in class" cloud adoption as you undergo digital transformation. Microsoft also has a corresponding assessment tool that helps you examine and strengthen your castle. They suggest runnin

Often times I think the idea is not to confuse, but when you sort of pile on all the different services in Azure, some of the details get...

When people hear the word FinOps, their minds almost always jump to one thing: savings. “How much money can we cut from the cloud bill?”...

It's 2025! If you've been living under a rock the last 10-15 years, you may not know that the global cloud computing industry is...

If you're managing multiple Log Analytics workspaces in Azure Monitor (like one of my customers recently), keeping track of log ingestion...

The journey to FinOps maturity is a transformative process for many (if not all) organizations adopting cloud financial management...