FinOps - Simply Explained

0:00 Welcome to the M365 FM podcast, where we explore the people, ideas and technologies shaping the future of work. Why cloud costs feel out of control. Most companies find out they're overspending on cloud when the invoice lands, and by then the money is already gone. Welcome to the M365 FM podcast, where we explore the people, ideas and technologies shaping the future of work. FinOps sounds like another piece of jargon, but it's really the missing conversation between the people who build with technology and the people who pay for it. Cloud bills grow quietly, one small decision at a time, and nobody notices until someone asks who actually owns the number. By the end of this episode, you'll understand what FinOps is, how it works, where it fits in Microsoft three hundred sixty five and Azure, and the mistakes that trip up almost everyone who tries it.

0:42 Cloud computing changed how companies pay for technology, and that shift sits underneath the whole problem. Years ago, you bought a server once and spread the cost across several years, so you knew the number in advance. Today you rent computing by the second. The bill rewrites itself every day and no single person feels responsible for it. Picture a developer who spins up a virtual machine on a Tuesday afternoon to test one idea. A meeting pulls them away. The test is forgotten, and that machine keeps running and charging. For months, nobody chose to waste that money, and that quiet accident is exactly what makes the league so easy to miss. The split shows up in the language people use. Finance asks for a forecast it can trust and engineering answers with a diagram of services that scale on demand. Neither side is wrong and neither side can see the whole picture alone.

1:23 Which is why the bill keeps growing while everyone feels busy. So the money drains away in dozens of tiny moments in almost every company that touches the cloud. That leak has a name, and more importantly, it has a practice built to stop it. What FinOps actually means. Start with the name because it gives away more than you would expect. FinOps is a mashup of finance and DevOps, and that pairing is the entire idea. It describes the dialogue between the builders and the payers, which sounds obvious until you notice how rarely those two groups actually talk. Here's the part that surprises most beginners. FinOps isn't a product you buy, and it isn't a single job title you can hire for. The FinOps Foundation, the nonprofit that writes the playbook, calls it an operational framework and a cultural practice. That's a formal way of saying it's a shared habit rather than a piece of software.

2:07 The goal isn't simply to shrink the bill. The foundation says it plainly if you think FinOps is about saving money, think again, because it's really about getting the most value out of technology. Sometimes the smart move is to spend more on something that earns more, and the practice gives you the numbers to make that call with confidence. You'll also hear the same idea called cloud cost management or cloud financial management. Those labels describe a task, while FinOps describes a culture that spreads across teams. And that difference matters more than it sounds. Picture the difference in practice. A team wants to run an analytics job every night. The cheap option takes six hours on a slow machine, and the pricier option finishes in twenty minutes. FinOps doesn't automatically pick the cheaper one. It asks what those saved hours are worth, then makes the trade off on purpose instead of by accident.

2:49 That habit of deciding on purpose is the heart of the whole thing. It's the reason the practice belongs to the company rather than to one department. Hold on to that idea because it explains something strange. You'll see later. The biggest savings come from a decision about people rather than a decision about technology. The practice grew out of a real shift in how technology gets funded. Companies used to treat it as one big yearly purchase, something accountants call capital expense. The cloud flipped that into a running cost that changes constantly, which left finance teams with no fixed number to plan around. FinOps grew up to bridge that gap, and it has since stretched far past the cloud into software, subscriptions, licenses, data centers, and now AI. Today, the numbers show how far it has spread in the FinOps Foundation's latest survey.

3:31 Ninety eight percent of teams said they manage AI spending in some form. Ninety percent manage or plan to manage software subscriptions. What began as a cloud cost club now touches almost every kind of technology a company buys. None of this requires an engineering degree. The practice is built for the person who is new to all of it. The first step is simply asking where the money goes and who is watching it. The six habits every FinOps team shares. The foundation lays out six principles, and they make the most sense when you read them as habits rather than rules. The first is that teams have to collaborate, which means finance, engineering and the business all look at the same numbers instead of arguing across a wall. The second habit is that business value drives the decisions.

4:12 You aren't chasing the lowest possible number, because a service that is cheap and breaks every week isn't cheap at all. The third is that everyone owns their own usage, so the person who built a resource is the person who watches what it costs. The fourth habit is about the data itself. Cost information has to be timely, accurate and available to the people who need it. A report that shows up three weeks late can't change a decision that's already been made. The fifth is that a small central team enables the whole practice, sharing best practices and holding the standards. The real work stays close to the teams doing it. The sixth habit is the one people forget, and it's about using the flexibility you're already paying for. The cloud lets you shrink when demand drops and grow when demand spikes. So the goal is to match what you pay to what you actually use. That blend of a central core and local ownership is the norm, not the exception.

4:55 In the Foundation's twenty twenty six survey, eighty one percent of teams ran either a centralized enablement model or a hub and spoke model. That's a formal way of describing a small core group that coaches everyone else. That doesn't mean the central team does the work itself. It means the central team draws the map and hands out the compasses, because one hundred people watching their own costs will always beat five people watching everyone else's. The ownership habit sounds abstract until you watch at work. A team that tags its resources and checks its own monthly number starts choosing smaller machines on its own. Nobody sends a memo because the cost finally belongs to a person instead of a spreadsheet. The collaboration habit works the same way when finance and engineering share one dashboard, the argument about the bill becomes a shared question about which services are earning their keep.

5:37 The six habits only work together, and skipping one usually shows up as a weakness somewhere else. If the data is slow, ownership fades. If ownership is missing, the central team turns into a referee instead of a coach. How FinOps runs in three repeating phases. The practice runs on a loop with three phases, and you cycle through them quickly rather than treating any of them as a one time project. The first phase is in form and its job is visibility. You gather the cost and usage data, then split it up so every team can see its own share of the bill. The second phase is optimize, where you look for ways to get more from what you already spend. There are two flavors of savings here. Usage optimization means using fewer resources to reach the same result, such as shutting down a machine that nobody needs. Rate optimization means paying a better price for the resources you really have to keep.

6:19 The third phase is operate, and this is where talk turns into action. You make the changes, measure what happened, and then loop right back to inform small, frequent steps. Beat one giant cleanup because the cloud changes faster than any annual project can keep up with. New teams usually start at the crawl stage where they react to problems after they show up. As the habit takes hold, they move into a walk stage and then a run stage. Their cost becomes part of how they design things from the beginning, rather than something they chase afterward. A whole cast of people makes this work. Executives set the priorities. Engineers own the usage they create. Finance keeps the numbers honest, procurement handles the contracts, and a FinOps practitioner ties the whole thing together. No single person runs FinOps alone, which is why the word culture keeps coming up.

7:01 The roles can feel like a lot at first. So here is the quick version. Executives decide what matters. Engineers decide how to build it, finance decides how to count it, and procurement decides what to sign. A FinOps practitioner is the person who keeps all four talking, which is a job that's mostly translation. One small warning here because the loop has a condition attached. The optimize phase only helps when people can see their own name on the bill, and that visibility depends on the tagging and allocation work from the inform phase. Skip the boring setup step and the clever savings never arrive. What FinOps looks like on a normal Tuesday. Here is what the loop looks like in real life, and it's far less dramatic than the theory suggests. Imagine a marketing team whose cloud spending jumps one week for no obvious reason.

7:42 An automatic alert fires and lands in the team's inbox, and someone finally asks the obvious question of what changed because the resources were tagged, the answer shows up in minutes. A test environment that was supposed to run for a single day has been quietly charging for two months, and a five minute cleanup makes the spike disappear. The money saved is small, but the habit that caught it is the real prize. Now the team sees its own number every month, and that changes how people behave. Some companies go one step further and actually bill each team for what it uses, a practice called chargeback. Others simply show teams their costs in a process called showback. Showback is the gentler starting point because it builds awareness before it starts moving budgets around. Notice how little of that story required a new product, a tag, an alert, and one curious person did the whole job.

8:26 And you could copy that same pattern on a Monday morning. The rhythm matters more than the tooling. A short monthly review, a couple of clear decisions, and one named owner for each action will beat a giant quarterly audit every time. The goal is a habit that survives busy weeks. The alert itself is doing quiet work underneath all of this. It turns a number nobody was watching into a question somebody has to answer. That small nudge is often the whole difference between a bill that stays flat and one that doubles by the end of the year. Getting there doesn't need a big meeting or a new system. It needs one alert, one owner, and one honest look at the number each month, which is exactly why a small team can start this week. The point of showback and chargeback is never to punish anyone. It's to make the cost of a decision visible to the person making it so the next choice comes out a little smarter.

9:08 Where FinOps lives in Microsoft three hundred sixty five and Azure. Microsoft makes this easy to start because the tools are already sitting inside the products you use. The home base is Microsoft Cost Management, which Microsoft describes as a suite of FinOps tools that help you analyze, monitor, and optimize your cloud costs. You can reach it in the Azure portal and in the Microsoft three hundred sixty five Admin Center. So your cloud bill and your software licenses finally live in the same place. Inside cost management cost analysis lets you explore where the money went and budgets, let you set a limit and get warned when you cross it. Anomaly alerts watch for unusual spikes and scheduled alerts. Email you a summary on a daily or weekly rhythm. Exports push the raw data into power BI or another system so you can build your own dashboards.

9:50 Azure advisor is the free helper that most beginners never open. Microsoft calls it a personalized cloud consultant, and it studies your setup and recommends changes every day, from resizing an oversized machine to shutting down something that sits idle. It's free. It's already switched on, and it's the closest thing Azure has to a to do list for saving money. Then come the rate levers where the discounts live, and Azure Savings Plan can cut compute costs by up to sixty five percent from pay as you go prices when your usage is steady. A reservation can save up to seventy two percent if you commit to specific usage for a set term. Azure Hybrid Benefit goes further and lets you reuse Windows Server or SQL server licenses you already own, which Microsoft says can save up to forty percent on virtual machines.

10:31 Treat every one of those numbers as a ceiling rather than a promise, because they only pay off when your usage is predictable. One more idea ties all of this together, and it carries a slightly awkward name focus. The FinOps Open Cost and usage specification is a shared format for billing data, and Microsoft is a founding member. It means a cost report from Azure, from another cloud, or from a software vendor can finally be read in the same language. That's a big deal. The first time you have to compare them side by side. And remember that software licensing belongs in the same discipline. A Microsoft three hundred sixty five copilot license runs about thirty dollars per user per month as an add on to a qualifying plan. Once you multiply that across a few hundred people, it deserves the same scrutiny you would give any server on the Microsoft three hundred sixty five side. The same thinking applies to licenses.

11:12 It's common to find people holding a premium license they never use, or two overlapping subscriptions doing almost the same job. Cleaning those up is often the fastest saving in the whole tenant. The Microsoft three hundred sixty five admin Center shows who is assigned what, so the question stops being a mystery and becomes a task. Those tools hand you the visibility and the discounts, and that part is available to you today. What no tool can hand you is the discipline to keep using them. Which brings us to the mistakes that sink almost every practice. The mistakes that sink a FinOps practice. The first mistake is treating FinOps as a pure, cost cutting exercise. When savings are the only scoreboard, teams learn to hide their spending instead of talking about it, and the numbers get worse rather than better. The second is running the practice without ownership or tags.

11:52 If nobody can say which project caused a charge. Every conversation about cost turns into a guessing game and the fix never sticks for long. The third mistake is buying a tool and calling the job done. Software can show you the numbers, but it can't repair a conversation that nobody wants to have. The fourth is keeping all the work inside one central team. If engineers never see their own costs, they never build the instinct to design with cost in mind, and the central team becomes a bottleneck instead of an enabler. The fifth mistake is chasing the last few percent of savings while ignoring the big calls. The foundation's twenty twenty six report captured this well, quoting a practitioner who said the big rocks of waste are gone. What remains, in their words, is a high volume of smaller opportunities that take far more effort to capture. The sixth is trying to measure value without agreeing on what value means.

12:36 Teams end up arguing about whether a tool is worth the money when they never define the outcome they were buying in the first place. Mistakes like these rarely announce themselves. They show up as a slow drift. The dashboards look fine, the meetings keep happening, and the bill still climbs because nobody changed the behavior behind it. The good news is that the same habits from earlier fix most of them, which means the cure is usually simpler than the disease. What FinOps can't fix FinOps is honest about its limits, and you should be, too. It can't yet tell you whether your AI investment is paying off, because the whole industry is still wrestling with that question. The twenty twenty six survey put it bluntly, and it shared a practitioner's line that nobody can answer whether AI is providing value yet. Measuring the money you saved by never making a mistake is just as hard as another practitioner.

13:18 In that same report, put it once you fix a problem, it's gone. So how do you give a developer credit for a cost that never appeared? It can't mend bad architecture or unclear ownership either, because those are design and culture problems that a report will only expose. It also can't promise that the easy wins are still waiting, since mature teams report that the obvious waste has largely been picked over, and it can't turn a commitment discount into free money, a reservation or a savings plan only helps when your usage is steady, so buying one for a workload you plan to shut down can lose more than it saves the cost. Data itself also arrives after the fact, which is worth sitting with for a second. You're always reading yesterday's numbers, so FinOps is a practice of steering, not a switch. You flip once and forget. The harder truth is that FinOps asks for patience.

13:59 The first pass usually finds a few obvious wins, and the second pass finds fewer, which is normal rather than a sign that the practice stopped working. None of that makes the practice weak. It just means FinOps is a way of asking better questions about technology spending, not a machine that prints savings on demand. Knowing what it can't do is what keeps you from expecting magic, and then giving up when the magic never shows. What to remember about FinOps. So here is the short version to carry with you. FinOps is a shared habit of watching what technology costs and deciding together what it is worth. It runs on a simple loop of inform, optimize, and operate. Microsoft hands you the starting tools inside the products you already use. Now for one question, and I really do want your answer. When was the last time someone on your team asked who owns the cloud bill if this made the topic feel less intimidating?

14:43 Subscribe to M365 FM to master the tools and the mindset shaping the future of work.