---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia IT Service Management
ft:clusterId :
- itsm
bundleId :
- itsm
workflow :
- Technology
---
# Model an Azure pipeline in DevOps
# Model an Azure pipeline in DevOps {#ariaid-title1}
* Release version: Australia
*
* Updated March 12, 2026
*
*  3 minutes to read
Model an Azure pipeline by mapping the pipeline to an app, and mapping DevOps Change Velocity pipeline steps to Azure pipeline jobs.
## Before you begin
Role required: sn_devops.admin
## Procedure
1. Map your pipeline to an app in DevOps.
1. Navigate to DevOpsApps \& PipelinesApps and open the application record to associate with the pipeline.
2. In the Pipelines related list, click Edit... to select a pipeline to associate with the app, or click New to create the pipeline.
Note:
While associating a pipeline with an app, the pipeline steps are also fetched during import.
For a new pipeline, fill in the Orchestration pipeline field using the project name and pipeline name as specified in Azure DevOps Pipelines in path format.
For example, My Project/My Classic Build Pipeline.
Note:
The project name must be specified with the pipeline because there could be multiple pipelines with the same name in different projects.
3. Click Submit.
2. Open the pipeline record again and select the Track check box so events from the pipeline are received.
The Track check box must be selected to integrate the pipeline with DevOps Change Velocity.
3. Create DevOps steps automatically or manually to map to each Azure pipeline job so an orchestration task can be created.
Note:
Manual creation of steps is not required when you [Use the ServiceNow DevOps extension for Azure DevOps and Azure DevOps custom actions](https://www.servicenow.com/docs/1xZN23j5GCbNyKMulIHDzA#config-dev-ops-extensions-azure "Install and configure DevOps extension for Azure DevOps to send build and release notifications from your Azure pipeline to DevOps Change Velocity.").
* Automatically create and map pipeline steps in DevOps by running your Azure pipeline when you [Use the ServiceNow DevOps extension for Azure DevOps and Azure DevOps custom actions](https://www.servicenow.com/docs/1xZN23j5GCbNyKMulIHDzA#config-dev-ops-extensions-azure "Install and configure DevOps extension for Azure DevOps to send build and release notifications from your Azure pipeline to DevOps Change Velocity.").
Pipeline steps are automatically created, mapped, and associated when DevOps receives step notifications from your Azure pipeline during the run.
* Manually create and map each pipeline step to an Azure pipeline job. In the Steps related list, click New to create a DevOps step for each Azure pipeline job (Orchestration stage field).
Note:
The Orchestration stage field value of each step is case-sensitive and must match the original name of the corresponding Azure pipeline job.
|-|-|
| Name | Name of the pipeline step. |
| Pipeline | Pipeline in which the step is configured. |
| Type | Pipeline step type. * Build and Test * Test * Deploy * Deploy and Test * Manual * Prod Deploy {#model-azure-pipeline-dev-ops__ul_ts3_nvm_wmb} |
| Order | Order in which the steps are run. Note: The step order determines the order of the cards in the [Pipeline UI](https://www.servicenow.com/docs/yaj2dQuVNc7UKuimbU8Fug "Use the Pipeline UI to visualize interactions and results across a pipeline execution. This graphical view shows pipeline step progression and other details for each pipeline."). The order of the cards in the Pipeline UI is by task execution. |
| Orchestration stage | Azure pipeline job name (case-sensitive). Note: For step association with Azure pipeline jobs, the Orchestration stage field must be configured. |
| Business service | Configuration service that applies to the step. |
[ ]
{#model-azure-pipeline-dev-ops__table_qs3_nvm_wmb}
Once orchestration tasks are created, [associate](https://www.servicenow.com/docs/2Bxce_S5tVNoeuA2WlGXEw "For manually created DevOps steps, associate each orchestration task in the Orchestration Tasks related list with a DevOps pipeline step to track the activity of each stage in your Azure pipeline.") each orchestration task in the Orchestration Tasks related list with a DevOps pipeline step.
{#model-azure-pipeline-dev-ops__choices_wmb_kkk_wmb}
4. Enable change control automatically or manually.
* If you are using the ServiceNow DevOps extension for Azure DevOps, run your Azure DevOps pipeline to automatically enable change control.
* If you are configuring change control manually, select the Change control check box in a step to enable [change acceleration](https://www.servicenow.com/docs/1IOGCXHTnX02RprvPaB2wg "Enable the change acceleration feature of DevOps Change Velocity for automatic change request creation in your pipeline, and use change approval flows and policies to automate approval under certain conditions.") and the corresponding configuration fields. For Azure release (CD) pipelines, enable change control in the first step of the required stage only. Change control for Azure release (CD) pipelines is supported only in pre-deployment gates.
Note:
ServiceNow [Change Management](https://www.servicenow.com/docs/uBHHMv4DsgI5VM1mPhonMg "The ServiceNow Change Management application provides a systematic approach to control the life cycle of all changes, facilitating beneficial changes to be made with minimum disruption to IT services.") must be installed for change acceleration.
|-|-|
| Change receipt | Select to enable change receipt for the step so the pipeline doesn't pause when a change request is created. All pipeline data is included in the change, but approval is not required for the pipeline to proceed. |
| Change approval group | Approval group for the change request. The change approval group becomes the Assignment group in the DevOps change request. Note: Ensure that the selected group has members and a group manager so the approver field is not empty. |
| Change type | Change request type to create. * Normal (default) * Standard * Emergency {#model-azure-pipeline-dev-ops__ul_zrc_xdf_llb} |
| Change model | Change model for the change request. For more information, see [DevOps change models](https://www.servicenow.com/docs/kYawifgINsRlYqcbPCDx_A "DevOps Change Velocity enables you to use fit-for-purpose change models that allow better flexibility in defining change models or processes to reflect modern development practices."). |
| Template Note: This field is shown only when Change type is Normal or Emergency. | List of templates to use to auto populate fields for Normal or Emergency change requests. Select a template or create a new one. |
| Standard change template Note: This field is shown only when Change type is Standard. | List of standard change templates to use for Standard change requests. Note: This field is required for Standard change type. |
| Change controlled branches | (Multibranch only) Comma-separated list of branches under change control. Wildcards are supported. |
[ ]
{#model-azure-pipeline-dev-ops__table_xm1_tdf_llb}
You can set up change control in your Azure DevOps YAML or Classic Azure pipeline using the [Azure Invoke REST API](https://www.servicenow.com/docs/JvdgAhTA1AeBK7OYJ7ZpHw "You can use the Azure Invoke REST API in your YAML or Classic Azure pipeline to configure change control for DevOps.") or the [ServiceNow DevOps extension for Azure DevOps](https://www.servicenow.com/docs/1xZN23j5GCbNyKMulIHDzA#config-dev-ops-extensions-azure "Install and configure DevOps extension for Azure DevOps to send build and release notifications from your Azure pipeline to DevOps Change Velocity.").
{#model-azure-pipeline-dev-ops__choices_gz4_1ns_1xb}
{#model-azure-pipeline-dev-ops__steps_jj2_q11_ykb}
## What to do next
[Configure the Azure
pipeline for DevOps](https://www.servicenow.com/docs/DXVXx8sIAwp4V7CfHkIcEg "Change control, artifacts, and packages can be configured in the Azure pipeline for integration with DevOps.")
*[\>]: and then