Clarify behavior on VM resize operation failures

[Olosinsk-commits]

Added note about VM resize operation failures and behavior. https://msazure.visualstudio.com/One/_workitems/edit/35567915/?view=edit

[prmerger-automator]

@Olosinsk-commits : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit b2d2c90:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/sizes/resize-vm.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull Request Overview

Clarifies documentation about behavior when a VM resize operation fails.

• Adds a NOTE block explaining that after a failed resize, the VM keeps running on the previous size while the portal may show the requested size.
• Introduces new admonition syntax in the resize instructions section.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The Docs alert syntax should use uppercase NOTE (> [!NOTE]) for proper rendering. Recommend changing [!Note] to [!NOTE]; also consider reducing unnecessary bold emphasis to only the key term (e.g., 'fails') for readability.

Suggested change

	> [!Note]
	> If a resize operation **fails**, the VM model **may display the desired VM size**. However, the virtual machine will **continue running** on its **previous size until** a **new allocation attempt succeeds**. The Azure portal may temporarily show the resized SKU even though the VM is still operating with the earlier configuration.
	> [!NOTE]
	> If a resize operation **fails**, the VM model may display the desired VM size. However, the virtual machine will continue running on its previous size until a new allocation attempt succeeds. The Azure portal may temporarily show the resized SKU even though the VM is still operating with the earlier configuration.

[v-dirichards]

@ju-shim

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[clmendes-MSFT]

@Olosinsk-commits the VM model not may but will display the desired VM size.

And the portal will not temporarily show, it will always show the desired VM size as that comes from the VM model from CRP.
By resizing you are modifying the model of the VM, so the information that will be present is the one from that change. And it not just Portal, but on every GET operation , whichever the client that is used.

[Olosinsk-commits]

#sign-off

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @ju-shim

[learn-build-service-prod]

Learn Build status updates of commit b496840:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/sizes/resize-vm.md	✅Succeeded

For more details, please refer to the build report.

[Olosinsk-commits]

@clmendes-MSFT, thank you for reviewing this proposal. Updated note based on your feedback.

[v-dirichards]

@ju-shim Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

[github-actions]

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict