Azure Pipeline discovery using config management on Cloud Admin Portal

Neeraj_27 · ‎02-20-2026

We are attempting to discover Azure DevOps pipelines using the Config Management module in the Cloud Admin Portal (CI/CD discovery setup as per ServiceNow documentation). However, no pipelines are getting discovered.

While reviewing the logs, we found the following error:

"ADO Discovery: Skipped pipeline with ID: 8 in discovery due to missing key 'deploymentID' in the pipeline variables."

We checked the response processor script: Azure_Devops_Persist_Pipelines_Response_Processor.

This script is expecting a field called deploymentID in the output variables returned by the Flow Designer action:

Action: AzureDevopsGetPipelines

The response from the action (which is passed as input to the response processor) looks like this:

[{
    "_links": {
      "self": {
        "href": "https://dev.azure.com/Mayank0464/e3d56396-5194-4fc4-9a8f-a30e5783ecd2/_apis/pipelines/5?revision=2"
      },
      "web": {
        "href": "https://dev.azure.com/Mayank0464/e3d56396-5194-4fc4-9a8f-a30e5783ecd2/_build/definition?definitionId=5"
      }
    },
    "configuration": {
      "path": "azure-pipelines.yml",
      "repository": {
        "fullName": "singhGS1110/AWS-auto-azure-pipeline",
        "connection": {
          "id": "5c6713a4-183f-4576-a49d-ea5b8ab0fc6f"
        },
        "type": "gitHub"
      },
      "type": "yaml"
    },
    "url": "https://dev.azure.com/Mayank0464/e3d56396-5194-4fc4-9a8f-a30e5783ecd2/_apis/pipelines/5?revision=2",
    "id": 5,
    "revision": 2,
    "name": "AWS-Infra-Creation",
    "folder": "\\"
  }]

As observed: There is no deploymentID field in the API response.

The official Azure DevOps REST API documentation for Pipelines – List also does not include deploymentID in the response schema. - Pipelines - List - REST API (Azure DevOps Pipelines) | Microsoft Learn

Therefore, the response processor script is validating against a field that does not exist in the API output.

Also, if we check the Azure official documentation for the API which is being used in the above-mentioned action does not have "deploymentID" as part of the response -

Current Setup

CSC Content Pack is installed.
CI/CD discovery configuration was done as per ServiceNow documentation. - Run Discovery on Azure DevOps config provider • Zurich IT Operations Management • Docs | ServiceNow
Discovery is executed from the Azure DevOps Config Provider.

So, Pipelines are skipped due to the missing "deploymentID" variable.

Anyone knows why is it happening? Are we missing on something

@Ram Devanathan1 your response would be helpful