0

I'm running an Azure DevOps pipeline that uses the "Azure API Management API Utility" task (from the Azure API Management DevOps Marketplace) to deploy APIs.

The pipeline fails with the following error in the task:

2025-12-12T01:51:56.0826581Z ##[error]A supported task execution handler was not found. The task does not carry an implementation that is compatible with your current operating system 'Windows(X64)'. Contact the task author for more details.

Here is the YAML script to reproduce the error:

variables:
  ApiDefURL: 'https://link_da_sua_aplicacao/swagger/1.0/swagger.json'
    
steps:
- task: pauldevops.azure-apim-import.azure-apim-importtask.AzureAPIMImport@1
  displayName: 'API  Import'
  inputs:
    ConnectedServiceNameARM: 'your_service_name'
    resourceGroupName: 'your_rsg'
    serviceName: yourservicename
    specificationUrl: '$(ApiDefURL)'
    apiPath: path
    enableSelfHostedGateway: false

Could you please tell me which operating systems are compatible with this specific task version?

⚠️Obs.: I'm using self-hosted agent with the following characteristics:

  • Operating system (VM): Windows (Windows Server 2022 Datacenter Azure Edition)
  • VM architecture: x64
  • Agent version: 2.7.41491.1183
Improve this question
3
  • 1
    That task only contains an entry for the Node20 handler. This requires the Azure Pipelines Agent version 4.248.0 or higher to be installed. Commented Jan 5 at 13:02
  • I filed a bug to see if they can improve the error message: github.com/microsoft/azure-pipelines-agent/issues/5441 Commented Jan 5 at 13:08
  • The "agent version" you mentioned in your Q is a different kind of agent, it's the Azure VM Agent. So I cannot with 100% certainty tell you whether you are currently on the wrong agent version. Commented Jan 5 at 13:09

2 Answers 2

Reset to default
1

The error message is a bit misleading. I've submitted a bug to the agent repo to see if that can be fixed.

What it's trying to tell you is that the task only defines execution handlers that aren't supported by your build agent. The cause depends on the agent version and operating system:

What generally counts is the sprint number, so Node24 was introduced in sprint 250, meaning that either major version 3 or 4 need to be at 3.350.0 or 4.250.0 for the Node24 handler to work.

If the agent version is too low you will get the error message you're experiencing. Upgrading the agent, or adding the NodeTaskRunnerInstaller@0 may solve the issue. The task can specify a Minimal Agent Version, which would have resulted in a different error message.

If the task only specifies PowerShell handlers, you will get this error message when your pipeline targets a Linux or Mac agent.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

The solution is in @jessehouwing comment. In my case, the VM where the agent was located didn't have Node installed. It worked with the following configuration:

  • Agent version: 4.255.0

  • Node version: 20.X

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.