What a tool has to do beyond what Azure already gives you for free, which levers actually move the invoice, and what differs for a Swiss estate.
Azure cost optimization tooling covers four jobs: showing where the money goes, finding waste, planning commitments, and applying licence entitlements. Azure's own Cost Management and Advisor do the first two for free and are the right place to start. A paid tool earns its place at the third and fourth — where commitments, entitlements and the Microsoft 365 side of the estate have to be weighed together rather than one resource at a time.
Updated
An honest comparison starts here, because two of the four jobs are already covered.
| Job | Native Azure | Where it stops |
|---|---|---|
| Cost visibility and allocation | Cost Management, free | Stops at the subscription boundary. Multi-tenant and cross-agreement roll-up is not covered. |
| Rightsizing recommendations | Azure Advisor, free | Advises per resource without commercial context: it does not know what you committed to, or what a change costs you in a reservation you already own. |
| Commitment planning | Partial | Reservations and savings plans are recommended separately, though they interact: reservations apply first, the savings plan covers what is left. |
| Licence-side levers | Not covered | Azure Hybrid Benefit, dev/test rates and the Microsoft 365 side of the estate sit outside Azure cost tooling entirely, and they are frequently the larger number. |
Unattached managed disks, reserved public IPs on nothing, load balancers with no backend, stopped-but-not-deallocated VMs. None of these show up as a failure; they show up as a line on the invoice.
A VM sized for a launch that never came stays that size for years. The judgement needs percentile utilisation over weeks, not a spot reading, and it needs to know whether a reservation already covers the current size.
Reservations reach a deeper discount but bind you to a family and region; savings plans are flexible but shallower. Azure applies the reservation first and the savings plan to the remainder, so the sensible pattern is to reserve the stable baseline and flex the rest.
Existing Windows Server and SQL Server licences with Software Assurance can be applied to Azure compute. It is a licensing entitlement, not a portal setting, which is why cost tooling rarely surfaces it and why it is so often left unclaimed.
The order is deliberate. Removing waste costs nothing and needs no commitment. Rightsizing changes what you should commit to. Only once the shape of the estate is settled does a multi-year commitment make sense — commit first and you have locked in the size you were about to reduce.
Swiss-hosted, and it reads your Microsoft 365 estate in the same view.