Buy a SUSE Linux software reserved plan

This is one of the cleanest savings cases on the Advisor dashboard. The SUSE software charge is already in the run rate, the workload is steady, and Microsoft documents a discount of up to 64% over the on-demand SUSE rate for committing one or three years. There is no new resource to operate and no architecture change. The saving is the gap between the on-demand software rate you pay today and the discounted reserved rate, multiplied by every hour those VMs run across the term.

The commitment is real and worth sizing carefully. A SUSE software plan is billed up front for the term: monthly payment is not offered for SUSE reservations, so a three-year plan is a single up-front charge against the period. The payback is the point at which accumulated software savings exceed that up-front outlay, and for steady SUSE estates it is typically well inside the first year. The financial discipline is to commit only to the baseline of SUSE usage you are confident persists for the term, and to use the shared scope so the discount is not stranded on one subscription.

The risk is mild and bounded, which is what makes this a near-risk-free saving. A reservation discount is use-it-or-lose-it per hour: if in a given hour you have fewer matching SUSE VMs running than the plan covers, the unused portion is simply not discounting anything that hour. You cannot lose more than you committed, and Microsoft allows reservations to be exchanged or returned within its documented policy, so an over-buy is recoverable rather than sunk. Size to the floor of usage, not the peak, and the downside is close to nil.

Priya is the finance partner working with the platform team. The Advisor recommendation lands as a single High-impact line with an estimated saving, and the instinct is not to wave the commitment through on the strength of that one number. It is to ask which SUSE usage is genuinely steady enough to underwrite a one-year or three-year term, because that is what the plan is: an up-front commitment, not a toggle you can flick off next month.

Working with the team, Priya separates the estate into a confident baseline and a discretionary top. The two production SAP application VMs have run continuously for a year and are core to the business; they are the floor and they anchor the commitment. The test VM is real usage today but nobody will promise it survives three years, so it stays on demand. The finance pack reads: 'Commit to the two steady production VMs at the up-front three-year rate to capture the up-to-64% software discount on the part of the estate we are certain about; leave the variable usage on demand; revisit and top up the plan if the test workload becomes permanent.' That framing turns a tempting-but-vague saving into a sized, defensible commitment with a clear payback.

The arithmetic here is unusually one-sided in the right direction. The saving is concrete and documented: up to 64% off the SUSE software rate for the committed usage, captured automatically with no architecture change. The cost of capturing it is an up-front commitment for the term, and the only way to lose money on the deal is to commit to more steady-state usage than the business actually runs, which depresses your realised discount on the unused coverage but never costs more than the on-demand rate you would have paid anyway.

The discipline that makes it near-risk-free is sizing to the floor. Commit to the baseline of SUSE usage you are confident persists for the whole term and leave variable or uncertain usage on demand. Where you over-buy, Microsoft's documented exchange and refund policy lets you recover rather than eat the mistake. Use the shared scope so the discount is not stranded on a single subscription. Done this way, the expected value is strongly positive and the tail risk is small and recoverable, which is exactly the profile finance should want to act on quickly.

Some cost savings ask you to accept a trade: less performance, more operational risk, an architecture migration. This one asks for none of that. The business already runs SUSE Linux workloads and already pays Microsoft for the SUSE licence by the hour. A reserved plan keeps everything running exactly as it is and lowers what that licence costs by a documented figure of up to 64%, in exchange for committing to a one-year or three-year term.

The leadership question is narrow: are we confident this SUSE footprint persists for the next one to three years? If yes, paying the on-demand rate on top of it is leaving money on the table every hour. If the footprint is genuinely uncertain, a shorter term or a smaller committed baseline keeps the saving while bounding the commitment.

Frame it as a treasury decision rather than an engineering one. The technical work is minimal, the saving is High impact on the Advisor dashboard, and the only real exposure is committing to more steady-state usage than the business will actually run, which is recoverable under Microsoft's exchange and refund policy. This is the kind of saving that should be quick to approve once the baseline is confirmed.

After a finance review where someone noticed the SUSE line had quietly grown, the question to the platform team was simple: are we paying full on-demand rates on software we have run continuously for years? The honest answer was yes, because nobody owned the reservation decision and the software meter was easy to miss underneath the compute spend that had already been reserved.

The response was not to rush out and buy the largest plan Advisor would justify. It was to confirm the steady baseline, size a plan to the production VMs the business is certain to run for the term, choose the shared scope so the discount spreads across every subscription with matching SUSE VMs, and use the up-front three-year rate for the deepest documented discount. The next finance review showed the SUSE software line stepping down materially with no change to a single running workload. The signal leadership cares about is exactly that: a High-impact saving captured on usage the business already committed to, with a commitment sized to what is certain rather than to what is tempting.

Most cost decisions involve a trade the business has to weigh: spend now to save later, or accept some risk for some saving. This one barely qualifies as a trade. The workload is running and will keep running; the only choice is whether to keep renting its licence by the hour or commit to it for a term and pay a documented up-to-64% less.

The cost of getting it wrong is bounded and recoverable: over-commit and you have under-used coverage you can exchange or return, never a charge above the on-demand rate you were already paying. The cost of doing nothing is a steady leak on a line item the business has no intention of stopping. When the downside is a recoverable over-buy and the upside is a High-impact saving on certain usage, the right answer is to confirm the baseline and approve it.