CLOUDY MUSINGS

When I wrote Azure Savings Plans, Finally Explained with Math That Actually Makes Sense , I was very focused on solving one specific problem. People were looking at Savings Plans and feeling like they were missing something obvious. They saw the hourly commitment. Then they saw their bill. They did not see a discount. And that disconnect was driving a lot of unnecessary anxiety. Once that post went live, I started finalizing this post as I knew there would be immediate follow

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

There is a common and risky assumption in Microsoft Security Support belief I hear more often than I probably should, especially in large enterprise environments where a customer may have an Enterprise Agreement (EA): We have an EA and Enterprise Support. Microsoft will take care of us if something bad happens. I understand where that belief comes from. Enterprise Agreement sounds comprehensive...thorough, even. Enterprise Support sounds like you are covered no matter what. O

Somewhere along the way, FinOps picked up a bad reputation. I had a customer tell me they viewed FinOps as akin to security. I felt it was a bad comparison, as most FinOps teams I work with, plus customers who have aspirations to build a FinOps team, are just trying to optimize + make cloud cost management more transparent to the organization. For a lot of teams though, it shows up as a dashboard no one asked for, a budget alert that fires too late, a preventative guardrail t

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

For a long time, HTTP felt like background noise to me. Websites loaded, APIs responded, dashboards refreshed, and everything mostly worked. Whenever HTTP came up, I subconsciously filed it under “developer skills” and moved on. But the more I worked in cloud architecture, security, performance troubleshooting, and cost conversations, the more I realized I was making decisions that depended heavily on HTTP behavior without really understanding it. So I finally slowed down and