|
| 1 | +--- |
| 2 | +title: Retirement of DevOps Starter for Azure | Microsoft Docs |
| 3 | +description: Retirement of Azure Devops Starter and Migration |
| 4 | +services: devops-project |
| 5 | +documentationcenter: '' |
| 6 | +author: moala |
| 7 | +manager: moala |
| 8 | +editor: |
| 9 | +ms.assetid: |
| 10 | +ms.service: az-devops-project |
| 11 | +ms.topic: overview |
| 12 | +ms.tgt_pltfrm: na |
| 13 | +ms.workload: |
| 14 | +ms.date: 09/16/2022 |
| 15 | +ms.author: moala |
| 16 | + |
| 17 | +--- |
| 18 | +# Retirement of DevOps Starter |
| 19 | + |
| 20 | +Azure DevOps Starter will be retired March 31, 2023. The corresponding REST APIs for [Microsoft.DevOps](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/devops/resource-manager/Microsoft.DevOps/) and [Microsoft.VisualStudio/accounts/projects](/rest/api/visualstudio/projects) resources will be retired as well. |
| 21 | +Customers are encouraged to use [Azure Developer CLI](/azure/developer/azure-developer-cli/overview?tabs=nodejs) instead. |
| 22 | + |
| 23 | +## Azure Developer CLI |
| 24 | + |
| 25 | +The replacement [Azure Developer CLI (azd)](/azure/developer/azure-developer-cli/overview?tabs=nodejs) is a developer command-line tool for building cloud apps. It provides commands that map to key stages in your workflow: code, build, deploy, monitor, repeat. You can use Azure CLI to create, provision, and deploy a new application in a single step. |
| 26 | + |
| 27 | +## Comparison between Azure DevOps and Azure Developer CLI |
| 28 | + |
| 29 | +| DevOps Starter | Azure Developer CLI | |
| 30 | +| ------------------------------------------ | ------------------------------------------- | |
| 31 | +| Deploy to Azure with few clicks | A single step to deploy to Azure | |
| 32 | +| Configures code, deployment, monitoring | Configures code, deployment, monitoring | |
| 33 | +| Provides sample application to get started | Provides sample applications to get started | |
| 34 | +| Allows user’s repo to be deployed | Allows user’s repo to be deployed | |
| 35 | +| UI-based experience in Azure portal | CLI-based experience | |
| 36 | + |
| 37 | +## Migration: |
| 38 | + |
| 39 | +There is no migration required because DevOps Starter does not store any information, it just helps users with their Day 0 getting started experience on Azure. Moving forward the recommended way for users to get started on Azure will be [Azure Developer CLI](/azure/developer/azure-developer-cli/overview?tabs=nodejs). |
| 40 | + |
| 41 | + |
| 42 | +1. For choosing language, framework and target service, choose an appropriate [template](https://github.com/search?q=org:azure-samples%20topic:azd-templates) from azd repo and run the command `azd up --template \<template-name\>` |
| 43 | + |
| 44 | +2. For provisioning Azure service resources, run the command `azd provision` |
| 45 | + |
| 46 | +3. For creating CI/CD pipelines, run the command `azd pipeline config` |
| 47 | + |
| 48 | +4. For application insights monitoring, run the command `azd monitor` |
| 49 | + |
| 50 | +For existing application deployments, **DevOps starter does not store any information itself** and users can use following to get same information: |
| 51 | + |
| 52 | +1. Azure resource details in Azure portal – In Azure portal, visit the resource page for which you had configured DevOps starter. |
| 53 | + |
| 54 | +2. To see pipeline and deployment information, go to the corresponding GitHub Actions workflow or Azure pipeline to view runs and deployments. |
| 55 | + |
| 56 | +3. To see monitoring details in Application insights, go to application insights for your Azure resource and look at the monitoring charts. |
| 57 | + |
| 58 | +## FAQ |
| 59 | + |
| 60 | +### What is the difference between DevOps starter and Azure developer CLI? |
| 61 | + |
| 62 | +Both are tools, which enable quick setting up of application deployment to Azure and configure CI/CD pipeline for the same. They enable users to quickly get started with Azure. |
| 63 | + |
| 64 | +Azure Developer CLI provides more developer-friendly commands in contrast to the UI wizard for DevOps Starter. This also means better clarity with config-as-code. |
| 65 | + |
| 66 | +### Will I lose my application or the Azure resources if I am not able to access DevOps starter? |
| 67 | + |
| 68 | +No. Application code, deployments, and Azure resources that host the application will still be available. DevOps Starter does not store any of these resources. |
| 69 | + |
| 70 | +### Will I lose the CI/CD pipeline that I created using DevOps Starter? |
| 71 | + |
| 72 | +No. You can still manage CI/CD pipelines in GitHub Actions or Azure Pipelines. |
| 73 | + |
0 commit comments