---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Configuring change control using the Azure Invoke REST API

# Configuring change control using the Azure Invoke REST API {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
You can use the Azure Invoke REST API in your YAML or Classic Azure pipeline to
configure change control for DevOps.

You must enable the This property decides whether to create a Generic Connection on configure operation for Azure DevOps property to use Invoke REST API.

For Azure Invoke REST API details, visit the [Microsoft documentation site](http://docs.microsoft.com) and search for [<kbd class="ph userinput">Invoke HTTP REST API task- Azure Pipelines</kbd>](https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/invoke-rest-api-v1?view=azure-pipelines&tabs=yaml).  
Important:  
If you have duplicate or reused job names in your pipeline execution steps, ensure that the
stageName attribute contains azurestageName/jobName in it's value, i.e. `stageName =
azureStageName/jobName`. The artifact registration tasks send both stage and job names
to associate the artifact version to the correct task execution.

## Generic service connection {#dev-ops-azure-change-control-api__section_e5x_5dd_qnb}

Using the Azure Invoke REST API requires the creation of a generic service connection in Azure DevOps.

## YAML Azure pipeline {#dev-ops-azure-change-control-api__section_ib2_lhc_rmb}

In Azure DevOps, a server task must be created with the service connection as the change
control endpoint.  
{#dev-ops-azure-change-control-api__table_yjj_5mp_wmb__entry__2}

| Azure pipeline type | Values |
|-|-|
| Build | * buildNumber * isMultiBranch * branchName {#dev-ops-azure-change-control-api__ul_gkc_xmp_wmb} |
| Release | * releaseNumber * projectName {#dev-ops-azure-change-control-api__ul_th2_fwr_wmb} |
[Table 1. Invoke REST API payload requirements]

{#dev-ops-azure-change-control-api__table_yjj_5mp_wmb}  
Note:  
For release pipelines, set the Pre-deployment conditionsAdvancedCompletion event field to Callback.  
Build pipeline:


    - task: InvokeRESTAPI@1
          inputs:
            connectionType: 'connectedServiceName'
            serviceConnection: 'change1'
            method: 'POST'
            body: |
             {
                "buildNumber": "$(build.buildId)",
                "isMultiBranch": "true",
                "branchName": "$(build.sourceBranchName)"
             }
            waitForCompletion: 'true'

Release pipeline:


    - task: InvokeRESTAPI@1
          inputs:
            connectionType: 'connectedServiceName'
            serviceConnection: 'change1'
            method: 'POST'
            body: |
             {
                "releaseNumber": "$(Release.ReleaseId)",
                "projectName": "$(System.TeamProject)"
             }
            waitForCompletion: 'true'

## Classic Azure pipeline {#dev-ops-azure-change-control-api__section_wyv_shc_rmb}

For a Classic Azure pipeline, an Invoke REST API server task must be added.  
Figure 1. Classic Azure build pipeline example  
Figure 2. Classic Azure release pipeline example

*[\>]: and then