Mike Austin explains that licensing need not be confusing and argues Azure itself is not primarily about licensing; instead, cost control (unit costs, avoiding overbuying/oversizing, using reservations) matters. He says the necessary data to manage costs exists but is often hidden. He gives a client example claiming a cost reduction equivalent to 60k (framed as about 10% of a ~700k annual expenditure) achieved in three days.
Chapters
The thing is, like, what I want you to know is licensing doesn't need to be confusing. In fact, we're going to talk about how Azure really isn't even about licensing. There are elements of licensing things that are in Azure, but Azure itself really isn't about it. You can pay a fair price for Azure. That could be unit cost and what you're paying for an hourly service. It could be ensuring that you're not over buying. It could be ensuring that you're not oversizing. It could be giving you the confidence to purchase reservations when maybe you don't have that. And you can control the conversation and the data that you need in order to do this exists. It's just hidden. And sometimes it's not hidden in plain sight. It is really hidden. And so we've got lots of proof of this. I'm just going to give you a couple of examples of some things that we've done recently. We had a client that was spending 60k per month. We reduced the spend by 60k per month out of their 70 or so. We reduced 60k out of a 700k annual annual expenditure, I shouldn't say per month. It was just over, you know, just shy of 10%. And we did that in three days.