Quickstart: Deploy an Azure Developer CLI template

A local development environment is a great choice for traditional development workflows. You'll clone the template repository down onto your device and run commands against a local installation of azd.

Prerequisites

Initialize the project

1. In File Explorer or a terminal, create a new empty directory, and change into it.

2. Run the azd init command and specify the template you want to use as a parameter:

   azd init --template todo-nodejs-mongo
   

   azd init --template todo-python-mongo
   

   azd init --template todo-csharp-cosmos-sql
   

   azd init --template todo-java-mongo
   

   Enter an environment name when prompted, such as azdquickstart, which sets a naming prefix for the resource group that will be created to hold the Azure resources. What is an Environment Name in azd?

   After you specify the environment, azd clones the template project to your machine and initializes the project.

Provision and deploy the app resources

1. Run the azd auth login command and azd launches a browser for you to complete the sign-in process.

   azd auth login
   

2. Run the azd up command:

   azd up
   

3. Once you are signed-in to Azure, you will be prompted for the following information:

   Parameter	Description
   Azure Location	The Azure location where your resources will be deployed.
   Azure Subscription	The Azure Subscription where your resources will be deployed.

   Select your desired values and press enter. The azd up command handles the following tasks for you using the template configuration and infrastructure files:

   • Creates and configures all necessary Azure resources (azd provision), including:
   • Access policies and roles for your account
   • Service-to-service communication with Managed Identities
   • Packages and deploys the code (azd deploy)

   When the azd up command completes successfully, the CLI displays two links to view resources created:

   • ToDo API app
   • ToDo web app frontend

   

   Note

   You can call azd up as many times as you like to both provision and deploy updates to your application.

Codespaces are a great option for developers who prefer to work in containerized cloud environments and avoid installing tools or dependencies locally.

Set up your Codespace

2. Above the file list, click Use this template > Open in a Codespace.

With Codespaces, all pre-requisites are installed for you, including the azd Visual Studio Code extension.

Run the template

1. Once your Codespace is created, right-click azure.yaml in the root directory. From the options, select up (provision resources, and deploy code to Azure).

   

2. When you run the azd up command, you'll be prompted to provide the following information and to sign in using a web browser and an authentication code:

   

   Parameter	Description
   Environment Name	Prefix for the resource group that will be created to hold all Azure resources. What is an Environment Name in azd? You can always create a new environment with azd env new.
   Azure Location	The Azure location where your resources will be deployed.
   Azure Subscription	The Azure Subscription where your resources will be deployed.

   This process may take some time to complete, as the azd up command handles the following tasks:

   • Creates and configures all necessary Azure resources (azd provision).
   • Configures access policies and roles for your account.
   • Implements service-to-service communication with Managed Identities.
   • Packages and deploys the code (azd deploy).

   Once you've provided the necessary parameters and the azd up command completes, the CodeSpaces terminal displays two Azure portal links to view resources created:

   • ToDo API app
   • ToDo web app frontend

   

What happened?

Upon successful completion of the azd up command:

• The Azure resources referenced in the template's README.md file have been provisioned to the Azure subscription you specified after you ran azd up. You can now view those Azure resources via the Azure portal.
• The app has been built and deployed to Azure. Using the web app URL output from the azd up command, you can browse to the fully functional app.

A DevContainer is a Docker image that includes all of the prerequisites you need to work with the azd template on your local machine. They're a great choice for developers who prefer containerized environments that still run on a local device instead of a cloud service like GitHub Codespaces.

Prerequisites

Initialize the project

1. Open a terminal, create a new empty directory, and change into it.

2. Run the following command to initialize the project:

   azd init --template todo-nodejs-mongo
   

   azd init --template todo-python-mongo
   

   azd init --template todo-csharp-cosmos-sql
   

   azd init --template todo-java-mongo
   

   When you run the azd init command, you'll be prompted to provide the following information:

   Parameter	Description
   Environment Name	Prefix for the resource group that will be created to hold all Azure resources. What is an Environment Name in azd? You can always create a new environment with azd env new.

Open the DevContainer

1. Open the project in VS Code.
2. Press F1 and choose: Remote-Containers: Rebuild and Reopen in Container

Run up command

Run the following command:

azd up

When you run the azd up command, you'll be prompted to provide the following information:

The azd up command may take some time to run as it completes the following steps:

• Creates and configures all necessary Azure resources (azd provision), including:
  • Access policies and roles for your account
  • Service-to-service communication with Managed Identities
• Packages and deploys the code (azd deploy)

Once you've provided the necessary parameters and the azd up command completes, the CLI displays two Azure portal links to view resources created:

• ToDo API app
• ToDo web app frontend