CLOUDY MUSINGS

a.k.a. Here's Your Full Guide to Understanding Azure Cloud Governance Without Losing Your Mind or Sanity Cloud governance is one of those topics that sounds straightforward until you start hearing people use the same five words to describe completely different things. You walk into a meeting and someone says, “We should solve this with Azure Policy,” and someone else responds, “We need a Blueprint,” and a third person chimes in with, “This belongs in our Service Group model.”

Cloud engineering looks complicated from the outside. But when you peel back some layers, it doesn't seem so daunting. I believe in breaking down tricky concepts so that even a six-year-old could understand. We don’t need to make everything so complicated that no one gets it. To me, that's the quickest way to lose the hearts and minds of your esteemed colleagues, customers, and peers. The Complexity of Cloud Engineering What I've found is that folks often imagine giant Terraf

I was reminded of Conway’s Law the day I watched an episode of The Bear where Carmy tried to redesign the entire kitchen workflow in the middle of lunch service. Onions were flying. Pans were screaming. Richie yelled “cousin” every twelve seconds. Sydney was five seconds away from either fixing everything or throwing a stainless steel pan into the alley. Half the staff looked like one more missed step would send them into a new career that involved silence and scented candles

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