CLOUDY MUSINGS

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

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

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

Shannon's Disclaimer: All code for this blog can be found here . I'm going to start putting together code based blogs with their own repo and will clean up older blog posts as time allows. If you spend enough time working in the cloud, you get used to things breaking in ways that make no sense. Case in point: the other day my Azure CLI on Windows decided it was going to stop working. I started in WSL because that is usually where things behave the best. I ran az login and ins