CLOUDY MUSINGS

Every legacy server eventually meets its Ragnarök. It doesn't matter if it's humming away on a rack in a closet, running as a VM on a vSphere or Hyper-V host, sitting in colo, or parked in an Azure subscription nobody's touched since the migration project wrapped. Support ends, the patches stop, and the only thing standing between that server and the wolves is whether you paid Microsoft's toll for a few more years of borrowed time. That toll is called Extended Security Update

You know how this usually goes...you wind up pulling the monthly AI spend report and the number is just that...a number. "Anthropic API: $14,200." No breakdown, no context, no indication of whether your team built something genuinely useful or spent three weeks regenerating the same 8,000-token system prompt on every single call. The invoice knows what you spent. Unfortunately, your invoice (by itself) has no idea why you spent what you did. The graphic above breaks it down:

Everybody loves AI until the invoice shows up! Not the cute "we spent a few hundred dollars experimenting" invoice that gets hand-waved away as innovation spend. I mean the kind of invoice that makes finance suddenly become deeply curious about architecture decisions they previously considered engineering trivia, while operations and/or product teams insist everything is still technically a pilot, and leadership starts asking whether we can "optimize this" as though that thou

Infrastructure changes have a way of producing unexpected side effects! (a.k.a. gather around for another lively lesson learned the hard way...) Sometimes it's a routing issue that doesn't surface until something tries to use the affected path. Sometimes it's a service dependency that nobody documented because it always just worked. And sometimes it's discovering that cloud management platforms don't automatically resume where they left off after you've changed the environmen

As with previous blog posts, all code can be found here! The Norns sat beside the Well of Urd weaving fate into the roots of Yggdrasil. The thread was already spun long before anyone knew how the story would end, and by the time the consequences arrived, they were simply discovering decisions that had already been made. I found myself thinking about that recently (HUGE Norse mythology fan) after yet another conversation about cloud billing, because the parallels are stronger

More and more, I'm finding that I'm getting asked a series of similar questions when a customer decides to pick up a Cloud Solution Provider or switches between a Cloud Solution Provider for Microsoft. It starts with a: "What happens to our tenant? Do we lose our identities? Does someone have to rebuild Entra ID?" The short answer is no. The longer answer is the rest of this post, because while nothing dramatic happens to your tenant, plenty of small things change at the bill