rebranding devops projects to devops starter for aks

Author: iamsrivatsa

articles/devops-project/_img/azure-devops-starter-aks/search-devops-starter.png

@@ -1,22 +1,23 @@
 ---
-title: 'Tutorial: Deploy ASP.NET Core apps to Azure Kubernetes Service with Azure DevOps Projects'
-description: Azure DevOps Projects makes it easy to get started on Azure. With DevOps Projects, you can deploy your ASP.NET Core app with the Azure Kubernetes Service (AKS) in a few quick steps.
+title: 'Deploy ASP.NET Core apps to Azure Kubernetes Service with Azure DevOps Starter'
+description: Azure DevOps Starter makes it easy to get started on Azure. With DevOps Starter, you can deploy your ASP.NET Core app with the Azure Kubernetes Service (AKS) in a few quick steps.
 ms.author: mlearned
 ms.manager: gwallace
 ms.prod: devops
 ms.technology: devops-cicd
 ms.topic: tutorial
-ms.date: 07/09/2018
+ms.date: 03/24/2020
 author: mlearned
 monikerRange: 'vsts'
 ---
 
 
-# Tutorial: Deploy ASP.NET Core apps to Azure Kubernetes Service with Azure DevOps Projects
+# Deploy ASP.NET Core apps to Azure Kubernetes Service with Azure DevOps Starter
 
-Azure DevOps Projects presents a simplified experience where you can bring your existing code and Git repo or choose a sample application to create a continuous integration (CI) and continuous delivery (CD) pipeline to Azure. 
+Azure DevOps Starter presents a simplified experience where you can bring your existing code and Git repo or choose a sample application to create a continuous integration (CI) and continuous delivery (CD) pipeline to Azure. 
+
+DevOps Starter also:
 
-DevOps Projects also:
 * Automatically creates Azure resources, such as Azure Kubernetes Service (AKS).
 * Creates and configures a release pipeline in Azure DevOps that sets up a build and release pipeline for CI/CD.
 * Creates an Azure Application Insights resource for monitoring.
@@ -25,7 +26,7 @@ DevOps Projects also:
 In this tutorial, you will:
 
 > [!div class="checklist"]
-> * Use DevOps Projects to deploy an ASP.NET Core app to AKS
+> * Use DevOps Starter to deploy an ASP.NET Core app to AKS
 > * Configure Azure DevOps and an Azure subscription 
 > * Examine the AKS cluster
 > * Examine the CI pipeline
@@ -37,21 +38,19 @@ In this tutorial, you will:
 
 * An Azure subscription. You can get one free through [Visual Studio Dev Essentials](https://visualstudio.microsoft.com/dev-essentials/).
 
-## Use DevOps Projects to deploy an ASP.NET Core app to AKS
+## Use DevOps Starter to deploy an ASP.NET Core app to AKS
 
-DevOps Projects creates a CI/CD pipeline in Azure Pipelines. You can create a new Azure DevOps organization or use an existing organization. DevOps Projects also creates Azure resources, such as an AKS cluster, in the Azure subscription of your choice.
+DevOps Starter creates a CI/CD pipeline in Azure Pipelines. You can create a new Azure DevOps organization or use an existing organization. DevOps Starter also creates Azure resources, such as an AKS cluster, in the Azure subscription of your choice.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
-1. In the left pane, select **Create a resource**.
-
-1. In the search box, type **DevOps Projects**, and then select **Create**.
+1. In the search box, type **DevOps Starter**, and then select. Click on **Add** to cerate a new one.
 
-   	![The DevOps Projects dashboard](_img/azure-devops-project-github/fullbrowser.png)
+    ![The DevOps Starter dashboard](_img/azure-devops-starter-aks/search-devops-starter.png)
 
 1. Select **.NET**, and then select **Next**.
 
-1. Under **Choose an application framework**, select **ASP.NET Core**.
+1. Under **Choose an application framework**, select **ASP.NET Core** and then select **Next**.
 
 1. Select **Kubernetes Service**, and then select **Next**. 
 
@@ -63,84 +62,67 @@ DevOps Projects creates a CI/CD pipeline in Azure Pipelines. You can create a ne
 
 1. Select your Azure subscription.
 
-1. To view additional Azure configuration settings and to identify the number of nodes for the AKS cluster, select **Change**.  
-	This pane displays various options for configuring the type and location of Azure services.
+1. To view additional Azure configuration settings and to identify the number of nodes for the AKS cluster, select **Change**. This pane displays various options for configuring the type and location of Azure services.
 
-1. Exit the Azure configuration area, and then select **Done**.  
-	After a few minutes, the process is completed. A sample ASP.NET Core app is set up in a Git repo in your Azure DevOps organization, an AKS cluster is created, a CI/CD pipeline is executed, and your app is deployed to Azure. 
+1. Exit the Azure configuration area, and then select **Done**. After a few minutes, the process is completed. A sample ASP.NET Core app is set up in a Git repo in your Azure DevOps organization, an AKS cluster is created, a CI/CD pipeline is executed, and your app is deployed to Azure. 
 
-	After all this is completed, the Azure DevOps Project dashboard is displayed in the Azure portal. You can also go to the DevOps Projects dashboard directly from **All resources** in the Azure portal. 
+    After all this is completed, the Azure DevOps Starter dashboard is displayed in the Azure portal. You can also go to the DevOps Starter dashboard directly from **All resources** in the Azure portal. 
 
-	This dashboard provides visibility into your Azure DevOps code repository, your CI/CD pipeline, and your AKS cluster. You can configure additional CI/CD options in your Azure DevOps pipeline. At the right, select **Browse** to view your running app.
+    This dashboard provides visibility into your Azure DevOps code repository, your CI/CD pipeline, and your AKS cluster. You can configure additional CI/CD options in your Azure DevOps pipeline. At the right, select **Browse** to view your running app.
 
 ## Examine the AKS cluster
 
-DevOps Projects automatically configures an AKS cluster, which you can explore and customize. To familiarize yourself with the AKS cluster, do the following:
+DevOps Starter automatically configures an AKS cluster, which you can explore and customize. To familiarize yourself with the AKS cluster, do the following:
 
-1. Go to the DevOps Projects dashboard.
+1. Go to the DevOps Starter dashboard.
 
-1. At the right, select the AKS service.  
-	A pane opens for the AKS cluster. From this view you can perform various actions, such as monitoring container health, searching logs, and opening the Kubernetes dashboard.
+1. At the right, select the AKS service. A pane opens for the AKS cluster. From this view you can perform various actions, such as monitoring container health, searching logs, and opening the Kubernetes dashboard.
 
-1. At the right, select **View Kubernetes dashboard**.  
-	Optionally, follow the steps to open the Kubernetes dashboard.
+1. At the right, select **View Kubernetes dashboard**. Optionally, follow the steps to open the Kubernetes dashboard.
 
 ## Examine the CI pipeline
 
-DevOps Projects automatically configures a CI/CD pipeline in your Azure DevOps organization. You can explore and customize the pipeline. To familiarize yourself with it, do the following:
+DevOps Starter automatically configures a CI/CD pipeline in your Azure DevOps organization. You can explore and customize the pipeline. To familiarize yourself with it, do the following:
 
-1. Go to the DevOps Projects dashboard.
+1. Go to the DevOps Starter dashboard.
 
-1. At the top of the DevOps Projects dashboard, select **Build Pipelines**.  
-	A browser tab displays the build pipeline for your new project.
+1. At the top of the DevOps Starter dashboard, select **Build Pipelines**.  A browser tab displays the build pipeline for your new project.
 
-1. Point to the **Status** field, and then select the ellipsis (...).  
-	A menu displays several options, such as queueing a new build, pausing a build, and editing the build pipeline.
+1. Point to the **Status** field, and then select the ellipsis (...).  A menu displays several options, such as queueing a new build, pausing a build, and editing the build pipeline.
 
 1. Select **Edit**.
 
-1. In this pane, you can examine the various tasks for your build pipeline.  
-	The build performs various tasks, such as fetching sources from the Git repo, restoring dependencies, and publishing outputs used for deployments.
+1. In this pane, you can examine the various tasks for your build pipeline. The build performs various tasks, such as fetching sources from the Git repo, restoring dependencies, and publishing outputs used for deployments.
 
 1. At the top of the build pipeline, select the build pipeline name.
 
 1. Change the name of your build pipeline to something more descriptive, select **Save & queue**, and then select **Save**.
 
-1. Under your build pipeline name, select **History**.  
-	This pane displays an audit trail of your recent changes for the build. Azure DevOps keeps track of any changes made to the build pipeline, and it allows you to compare versions.
+1. Under your build pipeline name, select **History**. This pane displays an audit trail of your recent changes for the build. Azure DevOps keeps track of any changes made to the build pipeline, and it allows you to compare versions.
 
-1. Select **Triggers**.  
-	DevOps Projects automatically creates a CI trigger, and every commit to the repo starts a new build. Optionally, you can choose to include or exclude branches from the CI process.
+1. Select **Triggers**. DevOps Starter automatically creates a CI trigger, and every commit to the repo starts a new build. Optionally, you can choose to include or exclude branches from the CI process.
 
-1. Select **Retention**.  
-    Depending on your scenario, you can specify policies to keep or remove a certain number of builds.
+1. Select **Retention**. Depending on your scenario, you can specify policies to keep or remove a certain number of builds.
 
 ## Examine the CD release pipeline
 
-DevOps Projects automatically creates and configures the necessary steps to deploy from your Azure DevOps organization to your Azure subscription. These steps include configuring an Azure service connection to authenticate Azure DevOps to your Azure subscription. The automation also creates a release pipeline, which provides the CD to Azure. To learn more about the release pipeline, do the following:
+DevOps Starter automatically creates and configures the necessary steps to deploy from your Azure DevOps organization to your Azure subscription. These steps include configuring an Azure service connection to authenticate Azure DevOps to your Azure subscription. The automation also creates a release pipeline, which provides the CD to Azure. To learn more about the release pipeline, do the following:
 
-1. Select **Build and Release**, and then select **Releases**.  
-	DevOps Projects creates a release pipeline to manage deployments to Azure.
+1. Select **Build and Release**, and then select **Releases**.  DevOps Starter creates a release pipeline to manage deployments to Azure.
 
-1. Select the ellipsis (...) next to your release pipeline, and then select **Edit**.  
-	The release pipeline contains a *pipeline*, which defines the release process.
+1. Select the ellipsis (...) next to your release pipeline, and then select **Edit**. The release pipeline contains a *pipeline*, which defines the release process.
 
-1. Under **Artifacts**, select **Drop**.  
-	The build pipeline you examined in the previous steps produces the output that's used for the artifact. 
+1. Under **Artifacts**, select **Drop**. The build pipeline you examined in the previous steps produces the output that's used for the artifact. 
 
-1. At the right of the **Drop** icon, select **Continuous deployment trigger**.  
-	This release pipeline has an enabled CD trigger, which executes a deployment every time a new build artifact is available. Optionally, you can disable the trigger so that your deployments require manual execution. 
+1. At the right of the **Drop** icon, select **Continuous deployment trigger**. This release pipeline has an enabled CD trigger, which executes a deployment every time a new build artifact is available. Optionally, you can disable the trigger so that your deployments require manual execution. 
 
 1. At the right, select **View releases** to display a history of releases.
 
-1. Select the ellipsis (...) next to a release, and then select **Open**.  
-	You can explore several menus, such as a release summary, associated work items, and tests.
+1. Select the ellipsis (...) next to a release, and then select **Open**. You can explore several menus, such as a release summary, associated work items, and tests.
 
-1. Select **Commits**.  
-	This view shows code commits that are associated with this deployment. Compare releases to view the commit differences between deployments.
+1. Select **Commits**. This view shows code commits that are associated with this deployment. Compare releases to view the commit differences between deployments.
 
-1. Select **Logs**.  
-	The logs contain useful information about the deployment process. You can view them both during and after deployments.
+1. Select **Logs**. The logs contain useful information about the deployment process. You can view them both during and after deployments.
 
 ## Commit changes to Azure Repos and automatically deploy them to Azure 
 
@@ -155,28 +137,27 @@ You're now ready to collaborate with a team on your app by using a CI/CD process
 
 1. Make a change to the file, such as adding some text within one of the div tags. 
 
-1. At the top right, select **Commit**, and then select **Commit** again to push your change.  
-	After a few moments, a build starts in Azure DevOps and a release executes to deploy the changes. Monitor the build status on the DevOps Projects dashboard or in the browser with your Azure DevOps organization.
+1. At the top right, select **Commit**, and then select **Commit** again to push your change. After a few moments, a build starts in Azure DevOps and a release executes to deploy the changes. Monitor the build status on the DevOps Starter dashboard or in the browser with your Azure DevOps organization.
 
 1. After the release is completed, refresh your app to verify your changes.
 
 ## Clean up resources
 
-If you are testing, you can avoid accruing billing charges by cleaning up your resources. When they are no longer needed, you can delete the AKS cluster and related resources that you created in this tutorial. To do so, use the **Delete** functionality on the DevOps Projects dashboard.
+If you are testing, you can avoid accruing billing charges by cleaning up your resources. When they are no longer needed, you can delete the AKS cluster and related resources that you created in this tutorial. To do so, use the **Delete** functionality on the DevOps Starter dashboard.
 
 > [!IMPORTANT]
-> The following procedure permanently deletes resources. The *Delete* functionality destroys the data that's created by the project in DevOps Projects in both Azure and Azure DevOps, and you will be unable to retrieve it. Use this procedure only after you've carefully read the prompts.
+> The following procedure permanently deletes resources. The *Delete* functionality destroys the data that's created by the project in DevOps Starter in both Azure and Azure DevOps, and you will be unable to retrieve it. Use this procedure only after you've carefully read the prompts.
 
-1. In the Azure portal, go to the DevOps Projects dashboard.
-2. At the top right, select **Delete**. 
-3. At the prompt, select **Yes** to *permanently delete* the resources.
+1. In the Azure portal, go to the DevOps Starter dashboard.
+1. At the top right, select **Delete**. 
+1. At the prompt, select **Yes** to *permanently delete* the resources.
 
 ## Next steps
 
 You can optionally modify these build and release pipelines to meet the needs of your team. You can also use this CI/CD pattern as a template for your other pipelines. In this tutorial, you learned how to:
 
 > [!div class="checklist"]
-> * Use DevOps Projects to deploy an ASP.NET Core app to AKS
+> * Use DevOps Starter to deploy an ASP.NET Core app to AKS
 > * Configure Azure DevOps and an Azure subscription 
 > * Examine the AKS cluster
 > * Examine the CI pipeline