[BUG]: windows-latest in microsoft-hosted agent pool does not map correctly

[theBNT]

What happened?

Hi,

posting here after being redirect from this developer community post.

We have several microsoft-hosted agents in azure yaml pipelines and are using capabilities to ensure that the agents can be used by multiple teams and to ensure that no one uses up the complete capacity.

This works fine for Ubunu VM image:

pool:
  vmImage: 'ubuntu-latest'
  demands:
    - teamname

If I try to do the same with Windows-latest VM image I get the following error:

pool:
  vmImage: 'windows-latest'
  demands:
    - teamname

##[error]No agent found in pool Hosted Windows 2019 with VS2019 which satisfies the following demand: teamname. All demands: teamname, Agent.Version -gtVersion 3.218.0

Fun fact: we didnt have an agent pool called Hosted Windows 2019 with VS2019 so this seems to be some microsoft internal pool. Our pool with the microsoft-hosted agents is called Azure Pipelines (the default?).

Weird fun fact 2: In that Hosted Windows 2019 with VS2019 we had exactly the same amount of agents like in our pool Azure Pipelines so we assumed it was a mismapping and assigned the correct capabilities to the hosts (again) in there, and it worked! (Workaround)

We then tried to use the windows-2022 image and it correctly used the agents from the Azure Pipelines pool, so it seems for windows-latest the mapping is broken.

We know that the docs say that in microsoft-hosted agents one does not have to use capabilities, but we need them to separate the resources.

Versions

4.248 / windows-latest

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

No response

Version controll system

git

Relevant log output