Azure Cost Management - Simply Explained

So let me ask you something, when was the last time you actually looked at your Azure build line by line, not just the total? If you're like most people you probably never did, or only when a surprise bill made you panic, here's the thing about cloud computing. Most people think it's cheap. You spin up a virtual machine, pay for what you use and the costs are supposed to be tiny compared to buying your own servers. And that's true until it isn't. The problem is that the cloud follows a pay as you go model, which sounds great in theory. But in practice, you're not just paying for what you use, you're also paying for what you're not using, but still running. According to Flexera's 2024 state of the cloud report, organizations waste an average of 32% of their cloud spend, meaning nearly a third of every dollar you put into Azure is money down the drain. By the end of this episode, you'll understand exactly what Azure cost management is, why it matters, and how to use it so you never get a surprise bill again. Grab your coffee and let's dive in. The horror stories, real people, real bills, consider Troy Hunt. You might know him as the security researcher who runs, have I been powned, the website where you check if your email has been leaked in a data breach. He's a cloud expert, someone who's been doing this for years. One morning, he woke up to an Azure bill for AU $11,000, about $8,000 US dollars in a single month. The cause was a cloud flare caching issue. His downloadable password hash files had grown past the 15 gigabyte cash limit, so every single request hit Azure storage account directly. Each spike was 17.3 gigabyte of egress bandwidth, and he didn't know about it until the bill arrived. Now, Troy's story is bad, but it's not the worst. There's a story from Hacker News about a startup that hired an AWS expert to manage their infrastructure. He made a provisioning mistake, spinning up too many expensive instances for testing and leaving them running overnight. The company's daily usage jumped from $300 to $27,000 overnight, and the startup didn't survive. The founder said he went back to shared PHP hosting after that, because the risk was just too high. Then there's the SaaS company that got a $500,000 bill, doubled their usual spend. The cause was a perfect storm of zombie resources. All machines no longer needed, but still running over provision databases and forgotten storage volumes accruing charges for months. Nobody was watching. And here's one that should terrify anyone who's ever committed code to a repository. A new employee accidentally committed AWS credentials to a public GitHub repo. Within hours, automated bots scraped those credentials and launched thousands of instances worldwide to mine cryptocurrency. The bill came to $100,000 in a matter of hours. The company was lucky. AWS dropped the charges, but that's not guaranteed. Here's the common thread in every single one of these stories. No budgets, no alerts, no visibility. These aren't technical failures, they're visibility failures. The cloud was working exactly as designed, but nobody was watching. Why cost management is non-negotiable? Cloud follows a pay as you go model, which sounds great until you realize you're paying for stuff you're not even using. It's like using a credit card without ever checking your monthly statement. You don't realize how much you're spending until the bill arrives and by then it's too late. What does that matter? Because every dollar you waste on idle resources is a dollar you could be using to grow your business. Here's a number that might shock you. Idle and oversized virtual machines account for about 90% of cloud waste. That's not a typo, 90%. And that translates to 10 to 18% of your total compute costs that you could recover just by right sizing or shutting down what you don't need. Think about that for a second. If you're spending $10,000 a month on compute, you could be throwing away $10,800 on machines that are either too big for the job or sitting completely idle. But even test environments are a big part of the problem. A VM that runs 24/7 but only gets used during business hours is wasting about 60 hours per week, which adds up to over two full months of unnecessary compute per year per VM. If you've got five dev VMs running around the clock, you're paying for 10 months of compute you're not using. And that's just one VM. Multiply that across your entire environment and the numbers get scary. Then there are orphaned resources, disks that were attached to a VM you deleted months ago, public IP addresses that are allocated but not assigned to anything and snapshots of old databases you don't need anymore. These things add up. According to the FinOps 2026 waste playbook, orphaned resources can account for 2 to 5% of your total spend. And it doesn't sound like much until you realize that's money you're paying for absolutely nothing. The worst part, you might not even know they're there until you run a cost analysis. So here's the bottom line. Cost management isn't optional. It's not something you think about after you get a big bill. It's a must have practice from day one, whether you're a solo developer with a free trial or a company spending millions on Azure. What Azure cost management actually is. So now that we've seen what happens when you don't watch your cloud costs, let's talk about the tool that stops it from happening to you. Azure cost management is a built in Azure service that's already there, included with your subscription at no extra cost. And it does four things. It lets you monitor, analyze, control and optimize your cloud spending. Think of it like an office building. First analysis is the reception desk. It tells you who's coming in and out where people are going and what they're doing. Budgets are the security guard setting limits on who can go where and how much access they have. And alerts are the fire alarm going off when something's wrong. So you can deal with it before the whole building burns down. Let's break it down into the major components. So you can see how each piece fits. Now here's the thing as your cost management isn't just a billing tool. It's a governance tool. It gives you full visibility and control over every dollar you spend in Azure. Just it you can view your total spend, track costs by individual resource or resource group or subscription, analyze spending trends over time, set budgets with alerts and get cost-saving recommendations from Azure advisor. And all of this is available at different levels like your billing account, your subscription or even a single resource group. And here's the best part. All of this is built right into Azure, no extra setup required. One thing that surprises people is how often the cost data refreshes. Azure updates your cost data every four hours. So if you spin up a new VM at 10 AM, you'll see it reflected in cost analysis by 2 PM. And for build charges, the actual finalized numbers, those are available within 72 hours after the invoices issued. That's fast enough to catch problems early, but it's not instant. So you still need alerts as your safety net. So set up those alerts early and you'll sleep better at night. The billing hierarchy, understanding where your money lives. This is where your money actually lives in the cloud. Let's dive in. Here's the thing, Azure has two separate hierarchies that control where your money goes and they cross at the subscription level. That's where most people get confused. The first hierarchy is the billing hierarchy. It's how Microsoft tracks who pays for what? It goes like this, billing account, then billing profile, then invoice section, then subscription. Your billing account is your overall agreement with Microsoft. Within that, you have billing profiles, each representing a different invoice. Each billing profile can have invoice sections, which are like categories on your bill, and each invoice section links to one or more subscriptions. The second hierarchy is the resource hierarchy. This is how you actually deploy and manage your services. It goes management group, then subscription, then resource group, then resource. Management groups let you organize subscriptions. Subscriptions are the containers where billing happens. Resource groups are folders that hold related resources. And resources are the actual services you're paying for. VMs, databases, storage accounts. So why does this matter? Because knowing where your money is going means knowing which subscription, which resource group, and which individual resource is costing you. If you can't trace a charge back to a specific resource, you can't fix it. But here's the problem. Invoice sections don't relate to resource groups directly. Your finance team might see a charge in an invoice section called marketing department, but the actual resource could be in a resource group called web app prod that nobody in finance knows about. That creates allocation gaps. You know how much you're spending, but you don't know who's responsible. This is where tags come in. Tags are simple key value payers you attach to resources. Things like project ABC one on two three or department marketing or environment production. They're the bridge between the billing hierarchy and the resource hierarchy. With tags, you can slice your costs by project, department, environment, or anything else that makes sense for your organization. And a single resource can have up to 50 tags so you can be as granular as you want. The key takeaway is simple. If you're not tagging your resources, you're flying blind. You might know your total bill, but you won't know which team, which project, or which environment is driving those costs. And without that information, you can't optimize anything. Cost analysis, your financial dashboard, so you've got your tags in place, you understand the hierarchy. Now, where does all that money actually go? That's what cost analysis is for. It's the main dashboard inside as your cost management. And it lets you see every dollar you've spent broken down by service, location, resource group, or tag. When you open cost analysis and see your total spend for the month, that's useful, but not very helpful. What you really want to know is which services are eating up that budget. So you group by service name, and suddenly the picture becomes clear. Maybe 60% of your spend comes from a single application gateway, or a bastion service that's been running since you set up your VNet months ago, or a SQL database that's way bigger than it needs to be. That's the kind of inside cost analysis gives you. There's also a forecast line that shows you where your total spend is headed if nothing changes. So if you're on track to blow past your budget by the end of the month, you'll see it before it happens. Then you can take action. Right size of VM, shut down a dev environment, or delete an orphaned disk. You can switch between different views. Daily cost shows the day by day breakdown. Accumulated cost shows the running total for the month. View by resource to see individual charges or by service to see which Azure services are costing you the most. And once you start using tags, this becomes really powerful. You can filter by tag to see exactly how much a specific project, team, or environment is costing. The real power of cost analysis is drilling down. You started the subscription level, see your total spend, then drill into a resource group. From there, you drill into an individual resource. And suddenly you found the culprit, a single VM that's been running 24/7 for months, costing you hundreds of dollars when it should have been shut down after business hours. That's the kind of discovery that saves you real money. Budgets and alerts, your early warning system. Cost analysis shows you where you've been, but what about where you're going? That's where budgets and alerts come in as your early warning system, and they're the single most important thing you can set up to avoid the horror stories we talked about earlier. A budget is exactly what it sounds like. You set a spending limit at the subscription resource group or management group level, and then you configure alert thresholds that are percentages of that budget. You can set thresholds at 50%, 75%, 90%, and 100%. So if your monthly budget is 200 dollars, you'll get an email when you hit $100, then another at 150s, another at 180s, and another when you hit the limit. But here's the thing, budgets aren't just about getting emails. They can trigger automated responses. You can set up action groups that, when an alert fires, do things like shut down VMs, fail down resources, or even send a message to a team's channel or Slack. So if you hit 90% of your budget, you could have a logic app that automatically shuts down all non-production VMs until the next billing cycle starts. There are actually three types of alerts in Azure Cost Management. Budget alerts are the most common. They fire when you're spending crosses a threshold you set. Anomaly alerts are newer and more powerful because they use machine learning to detect unusual spending patterns. So if your daily spend suddenly spikes from 50 to $500, Azure will flag it as an anomaly and send you an alert even if you haven't set a specific budget for that scenario. Then there are scheduled alerts which are more like recurring reports. They send you a regular summary of your costs so you can stay on top of trends without having to log into the portal every day. Let me give you a real example. You set a monthly budget of $200 on your subscription and configure an alert at 75%, which is $150. A few weeks into the month, you get an email saying your spend has hit $150. You log into cost analysis, drill down and find that a development VM you spun up for testing is still running. You shut it down, problem solved. Without that alert, you would have kept paying for that VM until the bill arrived at the end of the month. Now there's a trap here. It's called "Set it and forget it." You set up a budget, configure alerts, and then never look at it again. That's a mistake because budgets need regular review and adjustment. Your spending patterns change, your workloads change, your team grows. At $200 budget, you set last quarter might be completely unrealistic now or it might be too generous and your missing opportunities to save. So here's a starting point. Create one budget at the subscription level with alerts at 50% 75%, 90% and 100%. Rute those alerts to an email distribution list that includes both your finance team and your engineering leads. Review the budget monthly and adjust it as needed. And if you're feeling ambitious, set up an action group that automatically shuts down non-production resources when you hit 90%, that's a safety net that can save you thousands of dollars. Saving money without sacrificing performance. So now you know how to track your spending and set up alerts. But the real question is probably on your mind, how do you actually spend less without breaking your infrastructure? The good news is, as your gives you several ways to save money that don't require you to sacrifice performance, the biggest savings come from committing to Azure for the long term. Reserved instances let you commit to using a specific VM size in a specific region for one or three years. And in exchange you get a discount of up to 72% compared to pay as you go pricing. So if you've got a production database that's been running 24/7 for the past six months and you know it's not going anywhere, buying a reserved instance for it is basically free money. You're going to run that VM anyway. Why not pay less for it? But reserved instances have a catch. They're tied to a specific VM family in region. If you switch to a different VM size or move your workload to a different Azure region, your reservation doesn't apply. That's where the Azure savings plan for compute comes in. It's more flexible because you commit to a certain hourly spend on compute services and you get up to 65% off. The difference is it applies to any compute service across any region. So if your workload shift over time, you're still covered. For most organizations, the savings plan is the better choice. Unless you have very stable, predictable workloads, then there's Azure Hybrid Benefit, which is for organizations that already have Windows Server or SQL Server licenses with software assurance. You can bring those licenses to Azure and save up to 40% on Windows VMs and up to 55% on SQL workloads. And here's the best part. You can combine Hybrid Benefit with reserved instances so you could get 72% off with a reservation and then stack another 40% on top of Hybrid Benefit giving you a total savings over 80% compared to standard pay as you go pricing. The catch is you have to enable it manually on each VM. It's not automatic. So if you've got Windows VMs running in Azure and you haven't checked whether Hybrid Benefit is enabled, you're probably leaving money on the table. For development and testing environments, the simplest way to save is auto shutdown. You can configure any VM to automatically shut down at 7pm and start back up at 7am which saves about 60 hours per week of unnecessary compute. For a single VM, that's the equivalent of running it for free for two and a half days every week. If you've got 10 dev VMs, auto shutdown alone could save you thousands of dollars a year, right sizing is another easy win. Azure Advisor analyzes your VM utilization over the past 30 days and recommends downsizing VMs that are over-provisioned. If your VM has been running at 10% CPU utilization for a month, you don't need that 16 core machine. Advisor will tell you exactly which VMs to resize and how much you'll save and the best part is it's free. You don't need any additional tools. Before you deploy anything, use the Azure pricing calculator. It's a free web tool that lets you add services, configure them and see exactly what they'll cost before you spin anything up. You can save your estimates and compare different configurations and it's the best way to avoid that I didn't know it would cost that much moment. And finally, there are spot instances. These are spare compute capacity that Azure sells at a discount of up to 90%. The catch is Azure can reclaim that capacity at any time with just 30 seconds notice. So you can only use spot instances for workloads that can handle interruptions, batch processing, rendering jobs or testing. But for those workloads, the savings are enormous. Building a cost-conscious culture. Here's the thing about all these tools and techniques. They don't work if nobody uses them. This management isn't just a finance problem, it's an engineering problem. If your developers don't understand what things cost, they'll keep spinning up expensive VMs and leaving them running because the tools are only as good as the culture around them. The first step is tagging. Tag every resource from day one with project environment, cost, center and owner. If it's not tagged, it's invisible. You can't track what you can't see, so don't rely on people remembering to tag things manually. Use Azure policy to enforce tagging rules automatically. You can set up a policy that depends tags to any resource that doesn't have them, or one that denies deployment entirely of required tags are missing. That makes tagging automatic and not optional. You'll also want to run regular cost reviews where every team has a monthly 30 minute meeting to look at their Azure costs, ask what changed, what's costing more than expected, and if there are any orphaned resources or idle VMs. This isn't a finance meeting, it's an engineering meeting, so the people who deploy the resources should be the ones reviewing the costs. And that brings us to responsibility. If you deploy it, you should understand what it costs. This should know that a D-Series VM costs more than a B-Series and that leaving a test environment running over the weekend costs real money. You don't need everyone to be a Finops expert, but they should have basic cost awareness. A simple dashboard showing each team's daily spend can change behavior overnight. The 80/20 rule applies here, which means 80% of your savings will come from 20% of your resources. Instead of trying to optimize everything at once, find your biggest spenders first, that application gateway, that oversized SQL database, or that dev environment that's been running for months. You'll see the biggest impact with the least effort. Now there is a limit to what Azure Cost Management can do on its own. If you're running multiple clouds, need complex chargeback models, or need to show back costs to individual business units, the native tools can start to feel limited. That's when you look at Finops tools or third party solutions like Cloud Health or Cloud Ability. But for most organizations, Azure Cost Management is more than enough to get started and save real money. So here's what you've learned today. Azure Cost Management turns cloud spending from a black box into a transparent dashboard. You can see where your money goes, set budgets to catch problems early, and use discounts and automation to save without sacrificing performance. Here's your homework. This week, set one budget and one alert on your subscription. Pick a threshold you're comfortable with and configure email notifications. It takes about five minutes and it's the single most effective thing you can do to avoid a surprise bill. Then, spend 15 minutes in cost analysis, drilling into your top three services by cost. Look at what's actually running. I guarantee you'll find something you can optimize like a VM that's too big, a dev environment that should be shut down at night or a disc that's been often for months. If you found this episode useful, subscribe on your favorite podcast platform and share it with someone who's just starting their cloud journey. We'll see you in the next episode.