"An image label with the label unsupported-vmimage does not exist" using `macos-13-arm64`

[albyrock87]

Description

Everything was working fine until one hour ago, then suddenly I'm getting the following error:

##[warning]An image label with the label unsupported-vmimage does not exist.
,##[error]The remote provider was unable to process the request.
Pool: [Azure Pipelines](https://dev.azure.com/centralreach01/472e2055-b6ee-4ef4-9bcd-bae6e680286c/_settings/agentqueues?poolId=&queueId=18)
Image: macos-13-arm64

I also tried to use macos-14-arm64, but in that case the error says that:

##[warning]An image label with the label macos-14-arm64 does not exist.

I also tried to use macos-14, but in that case the error says that:

##[warning]An image label with the label macos-14 does not exist.

Then I tried using macos-13 but that image is not up to date (no .NET8, and I don't like to install .NET 8 from scratch every time).

This looks very similar to #8926

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• macOS 11
• macOS 12
• macOS 13
• Windows Server 2019
• Windows Server 2022

Image version and build link

Is it regression?

Yes, last successful build was using 20231115.2

Expected behavior

The macOS-13-arm64 image is found and runs as expected

Actual behavior

The macOS-13-arm64 image appears to be not found.

Repro steps

1. Create an Azure pipeline using macOS-13-arm64
2. Run it a bunch of times

[mikhailkoliada]

Closing as duplicate of #8879 (comment) as stated in the comment Azure DevOps only supports what listed in the table, while macOS 14 is not supported yet at all.

[joshuapoq]

Definitely not a duplicate of 8879 which is to do with slow AzureDevOps pool providers. Would love to be able to use arm64 and macOS-14 as an ADO customer but they did state in the announcement for xlarge that it's GitHub only... but it makes little sense. What more does ADO have to do to support GH runners? Why are there two teams working on different same techs at Microsoft (GH Actions vs ADO) and why do they crossover in an unmaintained way?

[mmrazik]

Definitely not a duplicate of 8879 which is to do with slow AzureDevOps pool providers.

You are right about this but the previous comment was mostly referring to the specific comment which mentions supported vmImages in ADO.

macos-13-arm64 is an undocumented vmImage and I believe it is not working on GH either (macos-13-xl is). The pricing model is also different.
That said, I hear and acknowledge the feedback (as someone who works on ADO).

[qwertylolman]

we also started to receive this error today :(

[Nathan-Molby]

#8971