Skip to content

Update resize-vm.md #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update resize-vm.md #348

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/virtual-machines/sizes/resize-vm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ If your VM uses Premium Storage, make sure that you choose an **s** version of t
> [!Note]
> If the virtual machine is currently running, changing its size will cause it to restart.

If your VM is still running and you don't see the size you want in the list, stopping the virtual machine may reveal more sizes.
When you attempt to resize an Azure VM's size while it is running, the portal or CLI sometimes shows only a limited set of compatible VM sizes. This is because the VM is bound to a particular hardware cluster, and only certain sizes are supported in that cluster. By deallocating (stopping and releasing the compute host) the VM first, you allow Azure to reassign it to a cluster that supports more size options. After deallocation, you often see additional VM sizes available for resizing.

> [!WARNING]
> Deallocating the VM also releases any dynamic IP addresses assigned to the VM. The OS and data disks are not affected.
Expand Down