CLOUDY MUSINGS

Note, the companion code and corresponding full GitHub repository is located here . Azure costs are tricky enough without licensing contracts adding another layer of confusion on top. One of my long-running jokes from my time working at Microsoft was that you needed an advanced degree just to understand Azure billing, and then a second one to understand how that billing intersects with real-world consumption in Azure. What tends to catch teams off guard is that the agreement

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

Like all my previous blogs, code to accompany this post exists here . If you have ever tried to answer the question “what kind of Azure subscription is this?” using automation, you probably assumed there was a clean, authoritative answer somewhere. An API call. A property. A single source of truth. And if you have spent any real time with Azure billing or FinOps work, you already know how quickly that assumption falls apart. Most people eventually land on Offer ID. The Azure

There has been a lot of noise lately about Microsoft “changing support” for Azure Pay As You Go subscriptions. Depending upon who you ask, this has turned into everything from “PAYG is being deprecated” to “Microsoft is forcing everyone into CSP.” None of that is actually happening. Microsoft doesn't always make this straightforward in messaging, so my hope is to help you out a bit! This is what I want to land clearly with you all and will repeat it a few times: Microsoft is

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

All code for this blog can be found here . So you went all-in on Spot VMs to save money, but now you’ve hit that dreaded eviction wall....