Skip to content

Conversation

@v-Andre
Copy link
Contributor

@v-Andre v-Andre commented Oct 29, 2025

Clarified upgrade instructions for Azure Local 2510. Current verbatim induces customers in error that after installing 23h2 2510 it should automatically change to 24h2 -> this is not the case.

They will need to install a separate solution upgrade. The diagram of the release train should also be included to remove the "automatically" from

-> The OS version 25398.xxxxx automatically changes to 26100.xxxx

Clarified upgrade instructions for Azure Local 2510. Current verbatim induces customers in error that after installing 23h2 2510 it should automatically change to 24h2 -> this is not the case.

They will need to install a separate solution upgrade.
The diagram of the release train should also be included to remove the "automatically" from

-> The OS version 25398.xxxxx automatically changes to 26100.xxxx
@prmerger-automator
Copy link
Contributor

@v-Andre : 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 c3ec8d6:

✅ Validation status: passed

File Status Preview URL Details
azure-local/release-information-23h2.md ✅Succeeded

For more details, please refer to the build report.

@ShannonLeavitt
Copy link
Contributor

@alkohli

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 Tracking label for the PR review team label Oct 29, 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 updates the Azure Local release documentation to clarify the upgrade process for version 2510. The change adds information about when the solution upgrade will be available.

  • Clarifies that the solution upgrade from 23H2 to 24H2 will be released separately

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

3 participants