Azure Pipelines Images do not support newer generation Skus

[brittandeyoung]

Description

We are currently using the Standard D4ads v5 skue family for Manages Azure DevOps Pools with the Azure Pipelines Imanges. When attempting to update a Managed Azure DevOps Pool using the Azure Pipelines Images with a newer vm SKU, we run into the following error.

  {
│         "code": "SkuNotCompatibleWithImageDiskControllerType",
│         "message": "Incompatible DiskControllerType between Image(s) MMSWindows2022-g2 and Pool SKU Standard_D4ds_v6. Select a different image or sku for pool cloud-ops-non-prod-pool.",
│         "details": [],
│         "additionalInfo": []
│       },

We would like to leverage newer VM SKUs to take advantage of higher cpu clock speeds and efficiencies.

Platforms affected

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

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• Ubuntu Slim
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• macOS 26
• macOS 26 Arm64
• Windows Server 2022
• Windows Server 2025
• Windows Server 2025 with Visual Studio 2026

Image version and build link

We use the latest version of the available Gen2 images.

Is it regression?

n/a

Expected behavior

We should be able to use the latest version for the vm compute family with the Azure Pipelines Images.

Actual behavior

We receive the following error when attempting to update to a newer version:

  {
│         "code": "SkuNotCompatibleWithImageDiskControllerType",
│         "message": "Incompatible DiskControllerType between Image(s) MMSWindows2022-g2 and Pool SKU Standard_D4ds_v6. Select a different image or sku for pool cloud-ops-non-prod-pool.",
│         "details": [],
│         "additionalInfo": []
│       },

Repro steps

Attempt to use a V2 only VM SKU within azure for an Azure Managed DevOps Pool.