Freshness pass

Author: cdpark

articles/deployment-environments/how-to-create-configure-dev-center.md

@@ -1,40 +1,40 @@
 ---
-title: Create and configure a dev center for Azure Deployment Environments by using the Azure CLI
+title: Create and configure a dev center by using the Azure CLI
 titleSuffix: Azure Deployment Environments
-description: Learn how to create and access an environment in an Azure Deployment Environments project using Azure CLI.
+description: Learn how to create and access a dev center for Azure Deployment Environments project using the Azure CLI.
 author: renato-marciano
 ms.author: remarcia
 ms.service: deployment-environments
 ms.custom: devx-track-azurecli, build-2023
 ms.topic: quickstart
-ms.date: 04/28/2023
+ms.date: 11/29/2023
 ---
 
-# Create and configure a dev center for Azure Deployment Environments by using the Azure CLI
+# Create and configure a dev center by using the Azure CLI
 
-This quickstart shows you how to create and configure a dev center in Azure Deployment Environments.
-
-A platform engineering team typically sets up a dev center, attaches external catalogs to the dev center, creates projects, and provides access to development teams. Development teams create [environments](concept-environments-key-concepts.md#environments) by using [environment definitions](concept-environments-key-concepts.md#environment-definitions), connect to individual resources, and deploy applications.
+This quickstart guide shows you how to create and configure a dev center in Azure Deployment Environments.
 
+A platform engineering team typically sets up a dev center, attaches external catalogs to the dev center, creates projects, and provides access to development teams. Development teams can then create [environments](concept-environments-key-concepts.md#environments) by using [environment definitions](concept-environments-key-concepts.md#environment-definitions), connect to individual resources, and deploy applications.
 
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - Azure role-based access control role with permissions to create and manage resources in the subscription, such as [Contributor](../role-based-access-control/built-in-roles.md#contributor) or [Owner](../role-based-access-control/built-in-roles.md#owner).
 - [Install the Azure CLI](/cli/azure/install-azure-cli).
-- [Install dev center CLI extension](how-to-install-devcenter-cli-extension.md)
-- A GitHub Account and a [Personal Access Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) with Repo Access. 
+- [Install the dev center CLI extension](how-to-install-devcenter-cli-extension.md)
+- A GitHub account and a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) with repo access. 
 
 ## Create a dev center
-To create and configure a Dev center in Azure Deployment Environments by using the Azure portal:
+
+To create and configure a dev center in Azure Deployment Environments:
 
 1. Sign in to the Azure CLI:
 
     ```azurecli
     az login
     ```
 
-1. Install the Azure Dev Center extension for the CLI.
+1. Install the Azure CLI *devcenter* extension.
 
    ```azurecli
    az extension add --name devcenter --upgrade
@@ -43,10 +43,10 @@ To create and configure a Dev center in Azure Deployment Environments by using t
 1. Configure the default subscription as the subscription in which you want to create the dev center:
 
    ```azurecli
-   az account set --subscription <name>
+   az account set --subscription <subscriptionName>
    ```
 
-1. Configure the default location as the location in which you want to create the dev center. Make sure to choose an [available regions for Azure Deployment Environments](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=deployment-environments&regions=all):
+1. Configure the default location where you want to create the dev center. Make sure to choose an [available region for Azure Deployment Environments](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=deployment-environments&regions=all):
 
    ```azurecli
    az configure --defaults location=eastus
@@ -55,31 +55,31 @@ To create and configure a Dev center in Azure Deployment Environments by using t
 1. Create the resource group in which you want to create the dev center:
 
    ```azurecli
-   az group create -n <group name>
+   az group create -n <resourceGroupName>
    ```
 
 1. Configure the default resource group as the resource group you created:
 
    ```azurecli
-   az config set defaults.group=<group name>
+   az config set defaults.group=<resourceGroupName>
    ```
 
 1. Create the dev center:
 
    ```azurecli
-   az devcenter admin devcenter create -n <devcenter name>
+   az devcenter admin devcenter create -n <devcenterName>
    ```
 
-   After a few minutes, you'll get an output that it's created:
+   After a few minutes, the output indicates that it was created:
 
    ```output
    {
       "devCenterUri": "https://...",
-      "id": "/subscriptions/.../<devcenter name>",
+      "id": "/subscriptions/.../<devcenterName>",
       "location": "eastus",
       "name": "<devcenter name>",
       "provisioningState": "Succeeded",
-      "resourceGroup": "<group name>",
+      "resourceGroup": "<resourceGroupName>",
       "systemData": {
          "createdAt": "...",
          "createdBy": "...",
@@ -92,24 +92,25 @@ To create and configure a Dev center in Azure Deployment Environments by using t
 > [!NOTE]
 > You can use `--help` to view more details about any command, accepted arguments, and examples. For example, use `az devcenter admin devcenter create --help` to view more details about creating a dev center.
 
-## Adding personal access token to Key Vault
-You need an Azure Key Vault to store the GitHub personal access token (PAT) that is used to grant Azure access to your GitHub repository. 
+## Add a personal access token to Azure Key Vault
 
-1. Create a Key Vault:
+You need an Azure Key Vault to store the GitHub personal access token (PAT) that's used to grant Azure access to your GitHub repository.
+
+1. Create a key vault:
 
    ```azurecli
    # Change the name to something Globally unique
-   az keyvault create -n <kv name>
+   az keyvault create -n <keyvaultName>
    ```
 
    > [!NOTE]
-   > You may get the following Error: 
+   > You might get the following error: 
    `Code: VaultAlreadyExists Message: The vault name 'kv-devcenter-unique' is already in use. Vault names are globally unique so it is possible that the name is already taken.` You must use a globally unique key vault name.
 
-1. Add GitHub personal access token (PAT) to Key Vault as a secret:
+1. Add the GitHub PAT to Key Vault as a secret:
 
    ```azurecli
-   az keyvault secret set --vault-name <kv name> --name GHPAT --value <PAT> 
+   az keyvault secret set --vault-name <kv name> --name GHPAT --value <personalAccessToken> 
    ```
 
 ## Attach an identity to the dev center
@@ -118,91 +119,96 @@ After you create a dev center, attach an [identity](concept-environments-key-con
 
 In this quickstart, you configure a system-assigned managed identity for your dev center. 
 
-## Attach a system-assigned managed identity
+### Attach a system-assigned managed identity
 
 To attach a system-assigned managed identity to your dev center:
 
    ```azurecli
-   az devcenter admin devcenter update -n <devcenter name> --identity-type SystemAssigned
+   az devcenter admin devcenter update -n <devcenterName> --identity-type SystemAssigned
    ```
 
-### Assign the system-assigned managed identity access to the key vault secret
-Make sure that the identity has access to the key vault secret that contains the personal access token to access your repository. Key Vaults support two methods of access; Azure role-based access control or Vault access policy. In this quickstart, you use a vault access policy.
+### Give the system-assigned managed identity access to the key vault secret
+
+Make sure that the identity has access to the key vault secret that contains the GitHub PAT to access your repository. Key Vaults support two methods of access; Azure role-based access control or vault access policy. In this quickstart, you use a vault access policy.
 
-1. Retrieve Object ID of your dev center's identity:
+1. Retrieve the Object ID of your dev center's identity:
 
     ```azurecli
-   OID=$(az ad sp list --display-name <devcenter name> --query [].id -o tsv)
+   OID=$(az ad sp list --display-name <devcenterName> --query [].id -o tsv)
    echo $OID
    ```
 
-1. Add a Key Vault Policy to allow dev center to get secrets from Key Vault:
+1. Add a Key Vault policy to allow the dev center to get secrets from Key Vault:
 
    ```azurecli
-   az keyvault set-policy -n <kv name> --secret-permissions get --object-id $OID
+   az keyvault set-policy -n <keyvaultName> --secret-permissions get --object-id $OID
    ```
 
 ## Add a catalog to the dev center
-Azure Deployment Environments supports attaching Azure DevOps repositories and GitHub repositories. You can store a set of curated IaC templates in a repository. Attaching the repository to a dev center as a catalog gives your development teams access to the templates and enables them to quickly create consistent environments.
+
+Azure Deployment Environments supports attaching Azure DevOps repositories and GitHub repositories. You can store a set of curated IaC templates in a repository. Attaching the repository to a dev center as a catalog gives your development teams access to the templates and allows them to quickly create consistent environments.
 
 In this quickstart, you attach a GitHub repository that contains samples created and maintained by the Azure Deployment Environments team.
 
 To add a catalog to your dev center, you first need to gather some information.
 
 ### Gather GitHub repo information
+
 To add a catalog, you must specify the GitHub repo URL, the branch, and the folder that contains your environment definitions. You can gather this information before you begin the process of adding the catalog to the dev center.
 
+You can use this [sample catalog](https://github.com/Azure/deployment-environments) as your repository. Make a fork of the repository for the following steps.
+
 > [!TIP]
-> If you are attaching an Azure DevOps repository, use these steps: [Get the clone URL of an Azure DevOps repository](how-to-configure-catalog.md#get-the-clone-url-for-your-azure-devops-repository).
+> If you're attaching an Azure DevOps repository, use these steps: [Get the clone URL of an Azure DevOps repository](how-to-configure-catalog.md#get-the-clone-url-for-your-azure-devops-repository).
 
-1. On your [GitHub](https://github.com) account page, select **<> Code**, and then select copy.
-1. Take a note of the branch that you're working in.
+1. Navigate to your repository, select **<> Code**, and then select copy.
+1. Make a note of the branch that you're working in.
 1. Take a note of the folder that contains your environment definitions. 
 
      :::image type="content" source="media/how-to-create-configure-dev-center/github-info.png" alt-text="Screenshot that shows the GitHub repo with Code, branch, and folder highlighted.":::
 
 ### Add a catalog to your dev center
 
 1. Retrieve the secret identifier:
-   
+
    ```azurecli
-   SECRETID=$(az keyvault secret show --vault-name <kv name> --name GHPAT --query id -o tsv)
+   SECRETID=$(az keyvault secret show --vault-name <keyvaultName> --name GHPAT --query id -o tsv)
    echo $SECRETID
    ```
 
-1. Add Catalog:
+1. Add the catalog. Replace `$REPO_URL` with the URL that you copied from your GiHub fork:
 
    ```azurecli
-   # Sample Catalog example
+   # Sample catalog example
    REPO_URL="https://github.com/Azure/deployment-environments.git"
-   az devcenter admin catalog create --git-hub path="/Environments" branch="main" secret-identifier=$SECRETID uri=$REPO_URL -n <catalog name> -d <devcenter name>
+   az devcenter admin catalog create --git-hub path="/Environments" branch="main" secret-identifier=$SECRETID uri=$REPO_URL -n <catalogName> -d <devcenterName>
    ```
 
-1. Confirm that the catalog is successfully added and synced:
+1. Confirm that the catalog was successfully added and synced:
 
    ```azurecli
-   az devcenter admin catalog list -d <devcenter name> -o table
+   az devcenter admin catalog list -d <devcenterName> -o table
    ```
 
 ## Create an environment type
 
 Use an environment type to help you define the different types of environments your development teams can deploy. You can apply different settings for each environment type.
 
-1. Create an Environment Type:
+1. Create an environment type:
 
    ```azurecli
-   az devcenter admin environment-type create -d <devcenter name> -n <environment type name> 
+   az devcenter admin environment-type create -d <devcenterName> -n <environmentTypeName> 
    ```
 
-1. Confirm that the Environment type is created:
+1. Confirm that the environment type was created:
 
    ```azurecli
-   az devcenter admin environment-type list -d <devcenter name> -o table 
+   az devcenter admin environment-type list -d <devcenterName> -o table 
    ```
 
 ## Next steps
 
 In this quickstart, you created a dev center and configured it with an identity, a catalog, and an environment type. To learn how to create and configure a project, advance to the next quickstart.
 
 > [!div class="nextstepaction"]
-> [Create and configure a project with Azure CLI](how-to-create-configure-projects.md)
+> [Create and configure a project by using the Azure CLI](how-to-create-configure-projects.md)