Skip to content

Clarify behavior on VM resize operation failures #346

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify behavior on VM resize operation failures #346

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b2d2c90
Clarify behavior on VM resize operation failures
Olosinsk-commits Oct 15, 2025
b496840
Clarify behavior of VM size resize failures
Olosinsk-commits Oct 23, 2025
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
4 changes: 4 additions & 0 deletions articles/virtual-machines/sizes/resize-vm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,10 @@ If your VM uses Premium Storage, make sure that you choose an **s** version of t

## Change the VM size

> [!Note]
> If a resize operation **fails**, the **VM model will still display the requested size**, but the **VM will continue running on its previous size** until the resize is successfully allocated. This behavior applies to both the Azure portal and all GET operations, as the displayed size always reflects the latest applied configuration, not the actual running size.
>

### [Portal](#tab/portal)
1. Open the [Azure portal](https://portal.azure.com). <br/><br/>
1. Type *virtual machines* in the search. Under **Services**, select **Virtual machines**.
Expand Down