SKU & pricing modernization
Clouds keep shipping cheaper ways to run the same workload: a newer instance generation, an ARM/Graviton processor, a newer disk type, a serverless or consumption pricing model, a managed-service tier that fits better. Modernizing the SKU or the pricing model keeps the workload identical while lowering the rate.
What we look for
Section titled “What we look for”- Newer generation / architecture — an older instance family or disk type (e.g. gp2→gp3) with a cheaper, equivalent successor; ARM/Graviton eligibility.
- Better pricing model — provisioned capacity that fits serverless or consumption better, an on-demand mode that should be switched, a batch or spot-eligible workload.
- Legacy tiers — classic/v1 services with a cheaper modern equivalent (e.g. Front Door classic → Standard, App Gateway v1 → v2).
Each candidate names the concrete target and confirms feature-compatibility in the pre-check, so a “cheaper” move never silently drops something you depend on.
How to act
Section titled “How to act”Modernization ranges from an online flag change to a planned migration; one-way moves (e.g. a Hyperscale promotion) lead with an export step and a longer lead time. leancosts drafts the migration steps, the validation, and the rollback. Follow Act on a cost finding.