CLOUDY MUSINGS

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

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

Ok - I'm here to loudly proclaim that my entire "APIs Aren't Just for Devs" series is drawing to a close. I'm hopeful you've found these...