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

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

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