this video shows how to model and map a devops change velocity pipeline to Azure pipeline jobs devops change velocity automates the change process by letting developers pause the pipeline to automatically create change requests collecting devops data from the Azure devops Pipeline and other devops tools and applying policies for the change request from the visual studio Marketplace download the service now devops extension for Azure devops after installing the extension you can establish a service connection this lets Azure devops send data to your service now [Music] instance now let's map the pipeline to an app in [Music] devops tracking is enabled automatically and we can check the tracking details here everything looks good so now it's time to set up Change Control in Azure devops for the deploy pipeline to do this manually open Azure devops and click pipelines here you can choose the pipeline to edit which opens the pipeline's yaml file the yaml file contains various jobs within the pipeline as well as tasks that are connected to the service Now devops application to add the service now devops server change acceleration task first select the deploy stage of the pipeline next click search tasks and search for the task now we can add our instances service Connection in the service now endpoint field and then add change request details in the change request details field copy the sample Json code and edit it to the specifications needed for the pipeline these specification ations include optional attributes the change requester the requester name and start and end dates finally we'll click add now the task has been added to the Azure devops Pipeline and you can run the pipeline the service now devops extension also lets you enable automatic change control for Azure devops pipelines the pipeline will go through three stages build test and deploy once the deploy stage Begins the pipeline will pause until we approve it to approve the pipeline we'll navigate back to the devops change workspace and open the change record let's click the approvers tab and select the state of the change request next we'll change the state to approved and click save from here the pipeline moves to the next approval stage and we'll repeat the same steps as before after we save the change we can update the pipeline to the Implement State once saved the pipeline will resume the deploy stage we can also automate this process by creating an approval [Music] policy now the devops change velocity pipeline is mapped to Azure devops to automate the change process for more information see our product documentation or knowledge base or ask a question in the service now community