---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Set up the Microsoft Azure DevOps console

# Set up the Microsoft Azure DevOps console {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Set up the Microsoft Azure DevOps console as the first step before you run Discovery and order a catalog item in the Cloud Services Catalog application.

## Before you begin

1. Add a deploymentID variable to the Microsoft Azure DevOps pipelines in your organization. The Microsoft Azure DevOps integration discovers pipelines with a deploymentID variable only.
2. Tag all the provisioned resources with a deploymentID key in the pipeline so that you can discover the resources after provisioning.
{#setting-up-azure-devops-console__ul_ztt_jjn_vzb}

The subscriptionID isn't required for Azure DevOps and Ansible templates.

Role required: none

## Procedure

1. Name a pipeline variable deploymentID that you can use for pointed Discovery to update the resources in CMDB.
2. Create a Personal Access Token (PAT) credential that you can use in Azure DevOps Discovery.
3. In the Update variable dialog box, override the pipeline variables by selecting the Let users override this value when running this pipeline check box.  
   Figure 1. Update variable dialog box   

   The pipeline works with the CSC DevOps Integration catalog item. The Microsoft Azure DevOps integration discovers pipelines with the deploymentID variable.