Skip to content

Clarify Windows Server editions comparison in next steps#8123

Open
Karl-WE wants to merge 1 commit intoMicrosoftDocs:mainfrom
Karl-WE:patch-12
Open

Clarify Windows Server editions comparison in next steps#8123
Karl-WE wants to merge 1 commit intoMicrosoftDocs:mainfrom
Karl-WE:patch-12

Conversation

@Karl-WE
Copy link
Contributor

@Karl-WE Karl-WE commented Mar 3, 2026

Updated the next steps section to clarify the comparison of Windows Server editions.

@robinharwood in addition it might be useful to rename md filename, removing the version 2022 from the and update all references accordingly. It is likely that vNext will be 2028 and so the documenation can be version agonistic.

see: editions-comparison-windows-server-2022.md

Updated the next steps section to clarify the comparison of Windows Server editions.
@Karl-WE Karl-WE requested a review from a team as a code owner March 3, 2026 11:37
@Karl-WE Karl-WE requested review from robinharwood and removed request for a team March 3, 2026 11:37
@prmerger-automator
Copy link
Contributor

@Karl-WE : 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 84f716d:

✅ Validation status: passed

File Status Preview URL Details
WindowsServerDocs/get-started/azure-edition.md ✅Succeeded

For more details, please refer to the build report.

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 "Next steps" link label in azure-edition.md to clarify that the referenced editions comparison document applies to Windows Server 2022 or newer (rather than just 2022). The PR description also notes that the target filename (editions-comparison-windows-server-2022.md) should ideally be renamed to be version-agnostic.

Changes:

  • Updated the display text of the "Next steps" link from "...Windows Server 2022" to "...Windows Server 2022 or newer" to indicate the comparison covers newer versions as well.

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

## Next steps

- [Comparison of Standard, Datacenter, and Datacenter: Azure Edition editions of Windows Server 2022](editions-comparison-windows-server-2022.md)
- [Comparison of Standard, Datacenter, and Datacenter: Azure Edition editions of Windows Server 2022 or newer](editions-comparison-windows-server-2022.md)
Copy link

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

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

The link target editions-comparison-windows-server-2022.md no longer exists in the get-started directory. The current file is editions-comparison.md (as confirmed by its existence in the directory listing and its use across several other files such as overview.md, toc.yml, install-windows-server.md, and index.yml). This will result in a broken link. The link target should be updated to editions-comparison.md.

Additionally, the link label "Comparison of Standard, Datacenter, and Datacenter: Azure Edition editions of Windows Server 2022 or newer" does not match the actual title of the target document, which is "Comparison of Windows Server editions". The label should be updated to match the document's title to avoid confusion.

Suggested change
- [Comparison of Standard, Datacenter, and Datacenter: Azure Edition editions of Windows Server 2022 or newer](editions-comparison-windows-server-2022.md)
- [Comparison of Windows Server editions](editions-comparison.md)

Copilot uses AI. Check for mistakes.
@ttorble
Copy link
Contributor

ttorble commented Mar 3, 2026

#assign: @robinharwood, @dknappettmsft

@robinharwood @dknappettmsft

Can you review the proposed changes?

#label:"aq-pr-triaged"

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

@prmerger-automator
Copy link
Contributor

Users robinharwood are already assigned.

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Mar 3, 2026
@robinharwood
Copy link
Collaborator

Thanks @Karl-WE I'll take a look at the rename and let you know.

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.

5 participants