This video shows how to integrate the ServiceNow Alignment Planner Workspace with Microsoft Azure DevOps using ServiceNow Guided Setup. Before we start, let's make sure we’ve installed all the plugins we need. To do that, we’ll go to Plugins… …search for Alignment Planner… …and see if the plugin has been installed. If not, go the ServiceNow Store… …and request it. Now let’s start the guided setup. First we’ll make sure we have a planning hierarchy and planning organization set up. To do that, we’ll go to Planning Hierarchies with Integrations. For this demo, we’ll use Hybrid Planning. This hierarchy includes epics at the portfolio level. the portfolio level. That’s the planning item type we’ll exchange with Azure DevOps. Next we’ll make sure we have a planning organization assigned to the Azure DevOps instance. For this demo, we’ll use the Digital/Business Transformation planning organization… …which is assigned to the Hybrid Planning hierarchy we just selected. That completes this step. So we’ll go back to Guided Setup… …and mark this step as complete. Next we’re going to create an Azure DevOps instance on the 
ServiceNow side and connect to it. But first let’s set up the credentials and connections we’ll need.
  To do that, we’ll open our Azure DevOps instance. We could create a new project for this, but we’re 
going to use this one, Mobile School App. This project uses Agile process work items like epics. Later on we'll setup our integration to exchange agile items. To create the access token for the connection, we’ll go to user settings… …Personal access tokens… …New Token. We’ll call the token Alignment Planner. We’ll choose an expiration date… …specify Full Access for the scope… …and Create. Be sure to copy and save the token somewhere else 
because you won’t have access to it again. Now let’s go back to our ServiceNow instance… …go to Credentials… …create a new credential… …and choose Basic Auth Credentials. We’ll call our credential apw_ado. And we’ll set the user name to apwado,... ... the same value we used to create the access token in Azure DevOps. For the password, we’ll use the token itself, the one we copied and saved. And Submit. Next we’ll create a connection to Azure DevOps. To do that, we’ll go to Connection and Credential Aliases… …and open the Azure_DevOps connection alias. In the Connections tab… …we’ll create a new connection. We’ll give it a name…. …and the credential is the one we just created. The connection alias is the one we opened to create this new connection. The connection URL is Azure dot com… … plus the name of our Azure DevOps instance, apwao. And we’ll submit to create the connection. Now we’re ready to integrate our Azure DevOps instance with our ServiceNow instance. Back in Guided Setup, we’ll configure our new connection… …and add a new integration. We’ll call the new integration ADO… …and we’ll choose the alias for the connection we just created. The version is Azure DevOps five point oh. We'll submit… ... and that creates our integration. Now we’ll connect to the Azure DevOps instance. We’ll open the form for the ADO instance… …and connect… …and we’re connected. Next we’ll discover projects for this integration. When the page refreshes… …we can see the two Azure DevOps projects. That completes this setup task, so we’ll go back to Guided Setup and mark it complete. Next we’ll add our Azure DevOps instance to a planning hierarchy. We chose the Hybrid Planning hierarchy earlier 
in this setup, so we’ll open it now… …and Create Azure DevOps Integration. This creates an alignment integration for the Azure DevOps instance. Back in the Hybrid Planning hierarchy,... ... now we can see the new integration in the Alignment Integrations tab. Now we’ll add the new instance to the planning hierarchy. We’ll open the record… …and add an instance mapping. We’ll call it ADO Mappings… …and the instance is the one we just created. We’ll submit… …and here’s the new mapping. When we open the mapping… …here are the Azure DevOps processes that are mapped.
  If we open the Agile process… …we see the Epic execution table. And in that table are the fields that’ll be exchanged between the Azure DevOps instance and ServiceNow Alignment Planner. That completes this task, so we’ll go back to Guided Setup and mark it complete. Finally let’s add projects from our Azure DevOps instance to a planning organization,... ... so that we can import and export planning items between Azure DevOps and Alignment Planner. In the Planning Hierarchies page, we’ll open the Hybrid Planning hierarchy… …and go to the Planning Organizations tab. We’ll assign the Hybrid Planning hierarchy to the Digital/Business Transformation organization. Here in the Portfolio page, we’ll edit the project list. Here’s a list of projects in our Azure DevOps instance. We’ll add Mobile School App to our planning organization so that we can import planning items from it. We'll save… ... and now the project has been added to our planning organization. That completes this task,... ... so we’ll go back to Guided Setup and mark it complete. And that completes the setup. Our Azure DevOps instance is integrated with 
Alignment Planner Workspace... ... and we have an Azure DevOps project in the workspace. For more information, see our product documentation, knowledge base, or podcast. Or ask a question in the ServiceNow Community.