in this video we'll connect and configure an Azure devops instance in applications using devops change velocity devops change velocity connects data from the devops tool chain which includes Azure devops once connected to the Azure devops tool additional settings can be configured to enable devops to import pipelines task execution records and step execution records to create a tool connection navigate to devops change workspace here you can create a tool connection through the connect tools widget as well as through the applications and Tool module we'll create a tool Connection by clicking the connect tools widget you can select Azure devops from either the plan code orchestration artifact or software quality categories in our example we'll select Azure devops from the plan category this will prompt you to choose whether to connect to an organization or project at the organization level you can configure multiple projects while at the project level you'll need to connect to each project separately in this case we'll select connect an organization from the drop down menu and then enter the URL of the devops organization and the tool name after this we can enter the Azure instance details because the tool name is already entered you just need to enter the password or access token we click connect and permission checks for the password or access token will appear and alert you whether they failed or were successful in our example all the access token permission checks are successful [Music] so let's specify the tool access we'll restrict access to the tool adding the groups that must have access in the maintained by field we'll also click the all devops app owners can view an associate tool objects to Applications checkbox so all owners can view an associate tool objects next we'll configure the Azure devops instance to send data to devops change velocity once we enter the integration user password we can select the projects we want to configure web hooks this will enable Azure devops to send real-time notifications for commits pipelines and work items making it easier to maintain up-to-date information now devops velocity is configured and connected to an organization next we'll create an application and Associate it with Azure plans repositories and pipelines that were previously discovered first let's associate plans for the application we also have the option to import historical data that selected plans created during a specified period this period lasts 90 days or three months a historical period of one month will show by default we'll stick with the default value of one month and import the plan's historical data now there is one import request created create additional import requests repeat the same steps when associating repositories and pipelines for the application once we refresh the page we see all the completed import requests for plans repositories and Pipelines all the applications can now be tracked through the Azure devops instance for more information see our product documentation or knowledge base or ask a question in the servicenow community [Music]