> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Right-size Azure VM Scale Set

> Move an underused Azure VM scale set to a smaller VM size that Azure Advisor recommends.

Azure Advisor watches the CPU, memory and network use of the instances in a virtual machine scale set and recommends a smaller or cheaper VM size when they are consistently underused. nOps imports these recommendations, checks them against your bill, and shows the estimated monthly saving.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Compute |
| **Service** | Virtual Machine Scale Sets |
| **Action** | Rightsize |
| **Effort** | Medium |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | Azure Advisor |

## Why it matters

Every instance in a scale set uses the same size, so an oversized size is paid for many times over. Resizing removes capacity you pay for but do not use.

## How nOps finds it

This recommendation comes from Azure Advisor, which looks at the scale set's use over its lookback period and recommends a target size. nOps imports Advisor's recommendations daily and checks each one against your own Azure bill for the last 7 complete days: the resource must still be billed in the last 3 days of that window, and Advisor's estimate is capped at what the resource actually cost (Advisor prices at pay-as-you-go rates, so you may pay less through discounts, reservations or savings plans). Recommendations worth less than \$1 a month are left out.

## Before you start

Permission to update the scale set, and a rollout plan that fits its upgrade policy.

## How to implement

1. Review the recommended size and confirm it supports what the workload needs (vCPU, memory, temp disk, accelerated networking, disk types).
2. In the Azure portal, open the scale set, go to **Size**, and choose the recommended size. Or use `az vmss update --resource-group RESOURCE_GROUP --name SCALE_SET --set sku.name=SIZE`.
3. If the upgrade policy is manual, update the instances (`az vmss update-instances --instance-ids "*" ...`), ideally a few at a time.
4. For AKS node pools, change the node pool VM size through AKS (a new node pool) instead of the scale set.
5. Update Terraform, Bicep or ARM templates so a later deployment does not change it back.

## Risks and considerations

* Instances restart to take the new size. Roll it out gradually to keep capacity.
* A smaller size has less headroom: check peaks outside Advisor's lookback window.
* Reservations or savings plans bought for the old size may cover the new one differently.
* To roll back, set the size back and update the instances again.

## FAQs

> [accordion] Why is the saving lower than Advisor shows?
>
> Advisor prices at pay-as-you-go rates. nOps caps the saving at what the scale set actually cost you, after discounts and commitments.

## Related

* [Shut Down Underutilized Azure VM Scale Set](https://help.nops.io/inform/supported-recommendations/shut-down-underutilized-azure-vm-scale-set)
* [Right-size Azure Virtual Machine](https://help.nops.io/inform/supported-recommendations/right-size-azure-virtual-machine)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.