Skip to content

Conversation

@ManishaSinha0410
Copy link

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.

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.
@prmerger-automator
Copy link
Contributor

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 6fd0482:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/windows-in-place-upgrade.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Aug 21, 2025
@v-dirichards
Copy link
Contributor

@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
Copy link

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

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Sep 18, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a critical warning to the Windows in-place upgrade documentation, advising against in-place OS upgrades for VMs hosting critical infrastructure roles like SQL Server, Domain Controllers, and Active Directory.

  • Adds a new note section warning against in-place upgrades for critical infrastructure workloads
  • Recommends deploying new VMs and copying data as the safer alternative approach

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit b91cee1:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/windows-in-place-upgrade.md ✅Succeeded

For more details, please refer to the build report.

@ManishaSinha0410
Copy link
Author

Any update please?

@github-actions github-actions bot removed the inactive This PR is inactive for more than 14 days label Oct 10, 2025
@v-ccolin
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@ManishaSinha0410
Copy link
Author

@v-dirichards @v-ccolin @ju-shim
Any update on this pull request please? This is pending from long time now.
If any change or amendment is required, please let me know.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants