You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-developer-cli/ade-integration.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Azure Developer CLI support for Azure Deployment Environments
3
3
description: Learn how to integrate the Azure Developer CLI with Azure Deployment Environments
4
4
author: alexwolfmsft
5
5
ms.author: alexwolf
6
-
ms.date: 9/14/2024
6
+
ms.date: 01/09/2026
7
7
ms.topic: reference
8
8
ms.custom: devx-track-azdevcli
9
9
ms.service: azure-dev-cli
@@ -15,7 +15,7 @@ The Azure Developer CLI (azd) provides support for [Azure Deployment Environment
15
15
16
16
## Prerequisites
17
17
18
-
Verify you have completed the following prerequisites to work with Azure Deployment Environments using `azd`:
18
+
To work with Azure Deployment Environments using `azd`, verify you completed the following prerequisites:
19
19
20
20
*[Installed `azd` locally](/azure/developer/azure-developer-cli/install-azd) or have access to `azd` via Cloud Shell
21
21
*[Created and configured an Azure Deployment Environment](/azure/deployment-environments/quickstart-create-and-configure-devcenter) with a dev center, project, and template catalog
@@ -33,7 +33,7 @@ You can configure `azd` to provision and deploy resources to your deployment env
33
33
azd config set platform.type devcenter
34
34
```
35
35
36
-
When `platform.type` is set to `devcenter`, all `azd` remote environment state and provisioning will leverage new dev center components. This configuration also means that the `infra` folder in your local templates will effectively be ignored. Instead, `azd`will use one of the infrastructure templates defined in your dev center catalog for resource provisioning.
36
+
When `platform.type` is set to `devcenter`, all `azd` remote environment state and provisioning leverage new dev center components. This configuration also means that the `infra` folder in your local templates is ignored. Instead, `azd`uses one of the infrastructure templates defined in your dev center catalog for resource provisioning.
37
37
38
38
You can also disable dev center support via the following command:
39
39
@@ -55,15 +55,15 @@ azd init
55
55
56
56
### azd up
57
57
58
-
The `azd up` command will package, provision, and deploy your application to Azure Deployment Environments. However, the provision stage of the `azd up` command will use the curated infrastructure-as-code templates in your remote dev center, while the deployment stage will deploy the source code in your `azd` template. While dev center mode is enabled, `azd`will ignore the `infra` folder in your local `azd` template and only provision resources using the dev center templates. The command will also prompt you for any necessary values, such as the Azure Deployment Environment project or environment type.
58
+
The `azd up` command packages, provisions, and deploys your application to Azure Deployment Environments. However, the provision stage of the `azd up` command uses the curated infrastructure-as-code templates in your remote dev center, while the deployment stage deploys the source code in your `azd` template. While dev center mode is enabled, `azd`ignores the `infra` folder in your local `azd` template and only provision resources using the dev center templates. The command will also prompt you for any necessary values, such as the Azure Deployment Environment project or environment type.
59
59
60
60
```bash
61
61
azd up
62
62
```
63
63
64
64
### azd template list
65
65
66
-
The `azd template list` command will display the available infrastructure templates in your dev center catalog, rather than showing templates from the default AZD Awesome gallery. [Catalogs](/azure/deployment-environments/concept-environments-key-concepts#catalogs) provide a set of curated and approved infrastructure-as-code templates your development teams can use to create environments.
66
+
The `azd template list` command displays the available infrastructure templates in your dev center catalog, rather than showing templates from the default AZD Awesome gallery. [Catalogs](/azure/deployment-environments/concept-environments-key-concepts#catalogs) provide a set of curated and approved infrastructure-as-code templates your development teams can use to create environments.
67
67
68
68
```bash
69
69
azd template list
@@ -73,23 +73,23 @@ azd template list
73
73
74
74
### azd provision
75
75
76
-
The `azd provision` command will create new dev center environments. The command will prompt you for any missing values, such as the environment type or project. When the command runs, it will use the associated infrastructure template to provision the correct set of Azure resources for that environment. While dev center mode is enabled, `azd`will ignore the `infra` folder in your local `azd` template and only provision resources using the dev center templates.
76
+
The `azd provision` command creates new dev center environments. The command prompts you for any missing values, such as the environment type or project. When the command runs, it uses the associated infrastructure template to provision the correct set of Azure resources for that environment. While dev center mode is enabled, `azd`ignores the `infra` folder in your local `azd` template and only provision resources using the dev center templates.
77
77
78
78
```bash
79
79
azd provision
80
80
```
81
81
82
82
### azd env list
83
83
84
-
The `azd env list` command will display the same list of environments you would see in the developer portal.
84
+
The `azd env list` command displays the same list of environments you would see in the developer portal.
85
85
86
86
```bash
87
87
azd env list
88
88
```
89
89
90
90
## Tagging resources for Azure Deployment Environments
91
91
92
-
`azd` provisioning for Azure Deployment Environments relies on curated templates from the dev center catalog. Templates in the catalog may or may not assign tags to provisioned Azure resources for you to associate your app services with in the `azure.yaml` file. If the templates do not assign tags, you can address this issue in one of two ways:
92
+
`azd` provisioning for Azure Deployment Environments relies on curated templates from the dev center catalog. Templates in the catalog may or may not assign tags to provisioned Azure resources for you to associate your app services with in the `azure.yaml` file. If the templates don't assign tags, you can address this issue in one of two ways:
93
93
94
94
* Work with your dev center catalog administrator to ensure the provisioned Azure resources include tags to associate them with services defined in your `azure.yaml` file.
95
95
* Specify the `resourceName` in your `azure.yaml` file instead of using tags:
@@ -121,7 +121,7 @@ You can define `azd` settings for your dev centers in multiple places. Settings
121
121
122
122
### Environment variables
123
123
124
-
The following environment variables will be discovered and used by `azd`:
124
+
`azd` discovers and uses the following environment variables:
0 commit comments