Azure-docs: There is no clear statement related to downtime for changing the size of VM

[Anand-Moghe]

If my VM size is available in the hardware cluster, and if I update the size of the vm to new size without deallocating the VM, will that VM restart? And what is the impact to end users while the VM is being upgraded (changing the size) ? Would they experience any downtime?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7c823b1f-688f-e1b9-1590-92d12c28b138
• Version Independent ID: ac483660-9046-51b6-b678-4e6f5cd15e74
• Content: Use PowerShell to resize a Windows VM in Azure
• Content Source: articles/virtual-machines/windows/resize-vm.md
• Service: virtual-machines-windows
• GitHub Login: @cynthn
• Microsoft Alias: cynthn

[AdamS-MSFT]

@Anand-Moghe Thank you for the valuable feedback,we are investigating the issue.

[jakaruna-MSFT]

@Anand-Moghe The VM restarts even if the VM size is available in the hardware cluster.
I just checked that by connecting to the VM via RDP and then updating the VM Size. Then the VM shuts down and comes up again with the new size. But the time taken for that is less than 2 minutes.

@cynthn Please add your comments and check if we can add this to the document.

[Anand-Moghe]

@jakaruna-MSFT Thanks a lot.

[jakaruna-MSFT]

@cynthn Please check and update the doc as required.

[art-gregorio]

Hi, can this step be used on a classic VM?

[cynthn]

The doc has been updated a couple of times over this last year and I think we now have the VM restart covered. Sorry this has stayed open so long!

please-close