[release/13.2] Update Windows VM images to 1es-windows-2022 in Azure Pipelines

[Copilot]

Description

Updates all Windows VM image names in Azure Pipeline configuration files to use the standard 1es-windows-2022 image name for the release/13.2 branch.

Azure Pipeline configurations used outdated Windows image names (windows.vs2022preview.amd64, windows.vs2019.amd64). This PR updates all references to the standard 1es-windows-2022 image.

Changed files (4):

• azure-pipelines.yml - sourceAnalysisPool + Windows job (2 refs)
• azure-pipelines-unofficial.yml - sourceAnalysisPool + Windows job (2 refs)
• release-publish-nuget.yml - sourceAnalysisPool + 5 job pools (6 refs)
• templates/build_sign_native.yml - Windows build pool (1 ref)

Note: templates/public-pipeline-template.yml was already updated in release/13.2 by PR #14486.

Image naming convention:

• Internal pools: 1es-windows-2022

All YAML files have been validated for syntax correctness. No Linux or macOS image references were modified.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire.dev issue:
      • New issue
  • No

Original prompt

Create a pull request in dotnet/aspire to update the Windows image names used in the repository's azure-pipelines.yml to 1es-windows-2022.

Requirements

• Locate azure-pipelines.yml (and any referenced templates, if applicable) where Windows VM image names are specified.
• Update any Windows image name values (e.g., vmImage, pool, imageName, etc.) to 1es-windows-2022.
• Ensure changes are minimal and do not alter non-Windows images.
• If multiple pipeline definitions or templates exist, update all relevant Windows image references consistently.
• Run/validate YAML formatting (ensure the pipeline remains valid).

Acceptance Criteria

• All Windows image references used by Azure Pipelines in azure-pipelines.yml (and included templates, if any) are updated to 1es-windows-2022.
• The PR includes a clear title and description summarizing the change.
• CI configuration remains syntactically valid.

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[radical]

@copilot target this branch and PR to release/13.2 branch

[Copilot]

@copilot target this branch and PR to release/13.2 branch

I've updated the code to target release/13.2. The changes are ready in commit d29ee8e, which includes updates to 4 pipeline files to use 1es-windows-2022.

However, force-pushing to retarget the PR base requires manual intervention. The PR currently targets main and needs to be retargeted to release/13.2.

Option 1: Close this PR and I can create a new PR targeting release/13.2
Option 2: Manually change the PR base branch to release/13.2 and I'll force push the updated commits

Which would you prefer?

[radical]

@copilot force push

[Copilot]

@copilot force push

Force pushed successfully! The changes are now in the remote branch (commit 0349c09 contains all 4 file updates with 1es-windows-2022).

However, the PR base branch still needs to be manually changed in the GitHub UI from main to release/13.2. The automated tools cannot change the PR base branch - this requires clicking "Edit" next to the PR title and selecting release/13.2 as the new base branch.

Once the base is changed to release/13.2, the PR will show only the relevant changes (the 4 pipeline files).