VSTS Rebrand: 10 files updated

Author: craigcaseyMSFT

articles/automation/TOC.yml

@@ -175,7 +175,7 @@
           href: automation-scenario-remove-resourcegroup.md
         - name: Source control integration with GitHub Enterprise
           href: automation-scenario-source-control-integration-with-github-ent.md
-        - name: Source control integration with VSTS
+        - name: Source control integration with Azure DevOps
           href: automation-scenario-source-control-integration-with-VSTS.md
         - name: Deploy an Azure Resource Manager template in an Azure Automation PowerShell runbook
           href: automation-deploy-template-runbook.md

articles/devops-project/index.yml

@@ -68,7 +68,7 @@ sections:
 - title: Step-by-Step Tutorials
   items:
   - type: paragraph
-    text: Learn how to use the Azure DevOps Project to create VSTS Release pipelines
+    text: Learn how to use the Azure DevOps Project to create Azure Release pipelines
   - type: list
     style: ordered
     items:

articles/devops-project/overview.md

@@ -31,8 +31,8 @@ The Azure DevOps project does all the work for the initial configuration of a De
 You can use the Azure DevOps Project to:
 
 * Quickly deploy your application to Azure
-* Automate the setup of a VSTS CI/CD pipeline
-* Use the DevOps project as a template to view and understand how to properly set up CI/CD to Azure with VSTS
+* Automate the setup of an Azure CI/CD pipeline
+* Use the DevOps project as a template to view and understand how to properly set up CI/CD to Azure with Azure DevOps
 * Get started with CI/CD pipeline to Azure, and then further customize the release pipeline based on your specific scenarios
 
 ## How do I use the Azure DevOps Project?
@@ -45,16 +45,16 @@ You choose several configuration options as part of the initial setup.  These op
 * Select an App language
 * Choose an App framework based on language
 * Select an Azure service (deployment target)
-* VSTS account (new or existing)
+* Azure DevOps organization (new or existing)
 * Choose your Azure subscription
 * Pick the location of Azure services
 * Choose from various pricing tiers for Azure services
 
 After you use the Azure DevOps Project, you can also delete all of the resources from a single place from the Azure DevOps Project dashboard on the Azure portal.
 
-## Azure DevOps Project and VSTS integration
+## Azure DevOps Project and Azure DevOps integration
 
-DevOps Projects are powered by VSTS.  The DevOps project automates all of the work needed in VSTS to set up CI/CD to Azure.  A Git repository is created in a new or existing VSTS account.  The DevOps project commits a sample application or your existing code to a new Git repository.  The automation also establishes a CI trigger for the build so that every new code commit will initiate a build.  The DevOps project also creates a CD trigger and will deploy every new successful build to the Azure service of your choice.  The build and release definitions can be customized for additional scenarios.  You can also clone the build and release definitions for use in other projects.
+DevOps Projects are powered by Azure DevOps.  The DevOps project automates all of the work needed in Azure DevOps to set up CI/CD to Azure.  A Git repository is created in a new or existing Azure DevOps organization.  The DevOps project commits a sample application or your existing code to a new Git repository.  The automation also establishes a CI trigger for the build so that every new code commit will initiate a build.  The DevOps project also creates a CD trigger and will deploy every new successful build to the Azure service of your choice.  The build and release definitions can be customized for additional scenarios.  You can also clone the build and release definitions for use in other projects.
 
 After creating your DevOps Project, you can:
 

articles/docker/toc.yml

@@ -9,7 +9,7 @@
   items:
   - name: Python Web App with Docker and PostgreSQL
     href: /azure/app-service-web/app-service-web-tutorial-docker-python-postgresql-app
-  - name: CI/CD with Docker Swarm and VSTS
+  - name: CI/CD with Docker Swarm and Azure DevOps
     href: /azure/container-service/container-service-docker-swarm-mode-setup-ci-cd-acs-engine
   - name: CI/CD with Docker, Jenkins, and Linux
     href: /azure/virtual-machines/linux/tutorial-jenkins-github-docker-cicd

articles/jenkins/toc.yml

@@ -38,7 +38,7 @@
     - name: Publish to Azure Storage
       href: /azure/storage/storage-java-jenkins-continuous-integration-solution
       maintainContext: true
-    - name: Use Jenkins with VSTS
+    - name: Use Jenkins with Azure DevOps
       href: https://www.visualstudio.com/docs/build/apps/jenkins/build-deploy-jenkins
     - name: Deploy Service Fabric apps
       href: /azure/service-fabric/service-fabric-cicd-your-linux-applications-with-jenkins

articles/machine-learning/team-data-science-process/platforms-and-tools.md

@@ -124,7 +124,7 @@ Run the following bash command to install Git on Linux (CentOS) machines:
 
 ### Generate public SSH key on Linux (CentOS) machines
 
-If you are using Linux (CentOS) machines to run the git commands, you need to add the public SSH key of your machine to your VSTS server, so that this machine is recognized by the VSTS server. First, you need to generate a public SSH key and add the key to SSH public keys in your VSTS security setting page. 
+If you are using Linux (CentOS) machines to run the git commands, you need to add the public SSH key of your machine to your Azure DevOps server, so that this machine is recognized by the Azure DevOps server. First, you need to generate a public SSH key and add the key to SSH public keys in your Azure DevOps security setting page. 
 
 - To generate the SSH key, run the following two commands: 
 
@@ -134,7 +134,7 @@ If you are using Linux (CentOS) machines to run the git commands, you need to ad
 ![](./media/platforms-and-tools/resources-1-generate_ssh.png)
 
 - Copy the entire ssh key including *ssh-rsa*. 
-- Log in to your VSTS server. 
+- Log in to your Azure DevOps server. 
 - Click **<Your Name\>** at the top right corner of the page and click **security**. 
 
 	![](./media/platforms-and-tools/resources-2-user-setting.png)

articles/machine-learning/team-data-science-process/project-ic-tasks.md

@@ -32,14 +32,14 @@ The tasks of project individual contributors (data scientists) to set up the TDS
 
 For instructions on how to execute a data science project under TDSP, see [Execution of Data Science Projects](project-execution.md). 
 
->[AZURE.NOTE] We outline the steps needed to set up a TDSP team environment using Visual Studio Team Services (VSTS) in the following instructions. We specify how to accomplish these tasks with VSTS because that is how we implement TDSP at Microsoft. If another code-hosting platform is used for your group, the tasks that need to be completed by the team lead generally do not change. But the way to complete these tasks is going to be different.
+>[AZURE.NOTE] We outline the steps needed to set up a TDSP team environment using Azure DevOps in the following instructions. We specify how to accomplish these tasks with Azure DevOps because that is how we implement TDSP at Microsoft. If another code-hosting platform is used for your group, the tasks that need to be completed by the team lead generally do not change. But the way to complete these tasks is going to be different.
 
 
 ## Repositories and directories
 
 This tutorial uses abbreviated names for repositories and directories. These names make it easier to follow the operations between the repositories and directories. This notation (**R** for Git repositories and **D** for local directories on your DSVM) is used in the following sections:
 
-- **R2**: The GroupUtilities repository on Git that your group manager has set up on your VSTS group server.
+- **R2**: The GroupUtilities repository on Git that your group manager has set up on your Azure DevOps group server.
 - **R4**: The TeamUtilities repository on Git that your team lead has set up.
 - **R5**: The Project repository on Git that has been set up by your project lead.
 - **D2**: The local directory cloned from R2.
@@ -59,7 +59,7 @@ The second, **TeamUtilities** repository, prerequisite is optional, depending on
 
 - Git must be installed on your machine. If you are using a Data Science Virtual Machine (DSVM), Git has been pre-installed and you are good to go. Otherwise, see the [Platforms and tools appendix](platforms-and-tools.md#appendix).  
 - If you are using a **Windows DSVM**, you need to have [Git Credential Manager (GCM)](https://github.com/Microsoft/Git-Credential-Manager-for-Windows) installed on your machine. In the README.md file, scroll down to the **Download and Install** section and click the *latest installer*. This takes you to the latest installer page. Download the .exe installer from here and run it. 
-- If you are using **Linux DSVM**, create an SSH public key on your DSVM and add it to your group VSTS server. For more information about SSH, see the **Create SSH public key** section in the [Platforms and tools appendix](platforms-and-tools.md#appendix). 
+- If you are using **Linux DSVM**, create an SSH public key on your DSVM and add it to your group Azure DevOps server. For more information about SSH, see the **Create SSH public key** section in the [Platforms and tools appendix](platforms-and-tools.md#appendix). 
 - If your team and/or project lead has created some Azure file storage that you need to mount to your DSVM, you should get the Azure file storage information from them. 
 
 ## Step 1-3: Clone group, team, and project repositories to local machine

articles/machine-learning/team-data-science-process/project-lead-tasks.md

@@ -28,7 +28,7 @@ A **Project Lead** manages the daily activities of individual data scientists on
 
 This topic currently covers tasks 1,2 and 6 of this workflow for project leads.
 
->[AZURE.NOTE] We outline the steps needed to set up a TDSP team environment for a project using Visual Studio Team Services (VSTS) in the following instructions. We specify how to accomplish these tasks with VSTS because that is how we implement TDSP at Microsoft. If another code-hosting platform is used for your group, the tasks that need to be completed by the team lead generally do not change. But the way to complete these tasks is going to be different.
+>[AZURE.NOTE] We outline the steps needed to set up a TDSP team environment for a project using Azure DevOps in the following instructions. We specify how to accomplish these tasks with Azure DevOps because that is how we implement TDSP at Microsoft. If another code-hosting platform is used for your group, the tasks that need to be completed by the team lead generally do not change. But the way to complete these tasks is going to be different.
 
 
 ## Repositories and directories
@@ -47,18 +47,18 @@ The prerequisites are satisfied by completing the tasks assigned to your group m
 
 To summarize here, the following requirements need to meet before you begin the team lead tasks: 
 
-- Your **group VSTS server** (or group account on some other code-hosting platform) has been set up by your group manager.
+- Your **group Azure DevOps server** (or group account on some other code-hosting platform) has been set up by your group manager.
 - Your **TeamProjectTemplate repository** (R3) has been set up under your group account by your team lead on the code-hosting platform you plan to use.
 - You have been **authorized** by your team lead to create repositories on your group account for your team.
 - Git must be installed on your machine. If you are using a Data Science Virtual Machine (DSVM), Git has been pre-installed and you are good to go. Otherwise, see the [Platforms and tools appendix](platforms-and-tools.md#appendix).  
 - If you are using a **Windows DSVM**, you need to have [Git Credential Manager (GCM)](https://github.com/Microsoft/Git-Credential-Manager-for-Windows) installed on your machine. In the README.md file, scroll down to the **Download and Install** section and click the *latest installer*. This takes you to the latest installer page. Download the .exe installer from here and run it. 
-- If you are using **Linux DSVM**, create an SSH public key on your DSVM and add it to your group VSTS server. For more information about SSH, see the **Create SSH public key** section in the [Platforms and tools appendix](platforms-and-tools.md#appendix). 
+- If you are using **Linux DSVM**, create an SSH public key on your DSVM and add it to your group Azure DevOps server. For more information about SSH, see the **Create SSH public key** section in the [Platforms and tools appendix](platforms-and-tools.md#appendix). 
 
 
 ## 1. Create a project repository (R5)
 
-- Log in to your group VSTS server at *https://\<VSTS Server Name\>.visualstudio.com*. 
-- Under **Recent projects & teams**, click **Browse**. A window that pops up lists all team projects on the VSTS server. 
+- Log in to your group Azure DevOps server at *https://\<Azure DevOps Server Name\>.visualstudio.com*. 
+- Under **Recent projects & teams**, click **Browse**. A window that pops up lists all team projects on the Azure DevOps server. 
 
 	![2](./media/project-lead-tasks/project-leads-2-create-project-repo.png)
 
@@ -108,9 +108,9 @@ Change to that directory. Then, run the following command to clone your team pro
 
 	git clone <the HTTPS URL of the TeamProjectTemplate repository>
 
-If you are using VSTS as the code-hosting platform, typically, the *HTTPS URL of your team project template repository* is:
+If you are using Azure DevOps as the code-hosting platform, typically, the *HTTPS URL of your team project template repository* is:
 
- ***https://\<VSTS Server Name\>.visualstudio.com/\<Your team project name\>/_git/\<Your team project template repository name\>***. 
+ ***https://\<Azure DevOps Server Name\>.visualstudio.com/\<Your team project name\>/_git/\<Your team project template repository name\>***. 
 
 In this example, we have:
 
@@ -124,9 +124,9 @@ In this example, we have:
 		
 ![8](./media/project-lead-tasks/project-leads-8-clone-team-project-template-linux.png)
 
-If you are using VSTS as the code-hosting platform, typically, the *SSH URL of the team project template repository* is:
+If you are using Azure DevOps as the code-hosting platform, typically, the *SSH URL of the team project template repository* is:
 
-***ssh://\<VSTS Server Name\>@\<VSTS Server Name\>.visualstudio.com:22/\<Your Team Project Name>/_git/\<Your team project template repository name\>.*** 
+***ssh://\<Azure DevOps Server Name\>@\<Azure DevOps Server Name\>.visualstudio.com:22/\<Your Team Project Name>/_git/\<Your team project template repository name\>.*** 
 
 In this example, we have:
 
@@ -142,15 +142,15 @@ Change directory to **GitRepos**, and run the following command to clone your pr
 
 ![9](./media/project-lead-tasks/project-leads-9-clone-project-repository.png)
 
-If you are using VSTS as the code-hosting platform, typically, the _HTTPS URL of the Project repository_ is ***https://\<VSTS Server Name\>.visualstudio.com/\<Your Team Project Name>/_git/<Your project repository name\>***. In this example, we have ***https://mysamplegroup.visualstudio.com/MyTeam/_git/DSProject1***.
+If you are using Azure DevOps as the code-hosting platform, typically, the _HTTPS URL of the Project repository_ is ***https://\<Azure DevOps Server Name\>.visualstudio.com/\<Your Team Project Name>/_git/<Your project repository name\>***. In this example, we have ***https://mysamplegroup.visualstudio.com/MyTeam/_git/DSProject1***.
 
 **Linux**
 
 	git clone <the SSH URL of the Project repository>
 
 ![10](./media/project-lead-tasks/project-leads-10-clone-project-repository-linux.png)
 
-If you are using VSTS as the code-hosting platform, typically, the _SSH URL of the project repository_ is _ssh://<VSTS Server Name\>@<VSTS Server Name\>.visualstudio.com:22/<Your Team Project Name>/\_git/<Your project repository name\>. In this example, we have ***ssh://mysamplegroup@mysamplegroup.visualstudio.com:22/MyTeam/_git/DSProject1***.
+If you are using Azure DevOps as the code-hosting platform, typically, the _SSH URL of the project repository_ is _ssh://<Azure DevOps Server Name\>@<Azure DevOps Server Name\>.visualstudio.com:22/<Your Team Project Name>/\_git/<Your project repository name\>. In this example, we have ***ssh://mysamplegroup@mysamplegroup.visualstudio.com:22/MyTeam/_git/DSProject1***.
 
 ### Copy contents of D3 to D5 
 
@@ -183,9 +183,9 @@ Now you can see in _DSProject1_ folder, all the files (except the metadata in .g
 
 If your project needs some specific directories or documents, other than the ones you get from your team project template (copied to your D5 directory in the previous step), you can customize the content of D5 now. 
 
-### Add contents of DSProject1 in D5 to R5 on your group VSTS server
+### Add contents of DSProject1 in D5 to R5 on your group Azure DevOps server
 
-You now need to push contents in **_DSProject1_** to _R5_ repository in your team project on your group's VSTS server. 
+You now need to push contents in **_DSProject1_** to _R5_ repository in your team project on your group's Azure DevOps server. 
 
 
 - Change to directory **D5**.