CLOUDY MUSINGS

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

People often toss around latency  and throughput  like they are one and the same. They are not. They live in the same world but serve very different roles. One cares about how fast something starts. The other cares about how much it moves. Understanding the difference is vital for cloud architects, platform engineers, FinOps professionals, and really anyone building digital systems. The best way to think about them is like two roommates with wildly different sleep schedules.

Picture this: you have built a castle in the cloud (filled with all your Azure workloads). Everything looks amazing, but is it safe,...

All code for this blog can be found here . I keep hearing more and more interest by customers I work with in exploring Cloud...

So there I was, ready to pull down a GitHub repo and get to work finishing a recent blog. I typed in the familiar command: git clone ...