Skip to content

Update windows-in-place-upgrade.md #308

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 1 commit into
base: main
Choose a base branch
from
Open

Update windows-in-place-upgrade.md #308

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: 2 additions & 0 deletions articles/virtual-machines/windows-in-place-upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@ Before you begin an in-place upgrade:

> [!NOTE]
> When performing an in-place upgrade on Azure Windows VMs, the VM properties on the Azure portal aren't updated; the changes are only reflected within the OS. This means that the source image information in the VM properties, including the publisher, offer, and plan, remains unchanged. The image used to deploy the VM remains the same, and only the OS is upgraded.
>
> For workloads hosting critical infrastructure roles or applications such as SQL Server, Domain Controller (DC), Active Directory (AD), or similar, we do not recommend performing an in-place OS upgrade. Deploying a new VM with latest desired version and copying the data will always be a best option. This approach will not only address certain roadblocks but will also ensure a safer, more controlled, and supportable upgrade path across your critical environment.

## Upgrade VM to volume license (KMS server activation)

Expand Down