Skip to content

Commit 801fdcb

Browse files
committed
edits
1 parent b74ce2a commit 801fdcb

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

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

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ To create and configure a dev center in Azure Deployment Environments:
7171
az devcenter admin devcenter create -n <devcenterName>
7272
```
7373

74-
After a few minutes, the output indicates that it was created:
74+
After a few minutes, the output indicates that the dev center was created:
7575

7676
```output
7777
{
@@ -100,13 +100,13 @@ You need an Azure Key Vault to store the GitHub personal access token (PAT) that
100100
1. Create a key vault:
101101

102102
```azurecli
103-
# Change the name to something Globally unique
103+
# Use a globally unique name
104104
az keyvault create -n <keyvaultName>
105105
```
106106

107107
> [!NOTE]
108108
> You might get the following error:
109-
`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.
109+
`Code: VaultAlreadyExists Message: The vault name 'kv-devcenter' 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.
110110

111111
1. Assign yourself the Key Vault Secrets Officer RBAC role:
112112

@@ -121,29 +121,29 @@ You need an Azure Key Vault to store the GitHub personal access token (PAT) that
121121

122122
## Attach an identity to the dev center
123123

124-
After you create a dev center, attach an [identity](concept-environments-key-concepts.md#identities) to the dev center. You can attach either a system-assigned managed identity or a user-assigned managed identity. Learn about the two [types of identities](how-to-configure-managed-identity.md#add-a-managed-identity).
124+
After you create a dev center, attach an [identity](concept-environments-key-concepts.md#identities) to the dev center. You can attach either a system-assigned managed identity or a user-assigned managed identity. For information, see [Add a managed identity](how-to-configure-managed-identity.md#add-a-managed-identity).
125125

126126
In this quickstart, you configure a system-assigned managed identity for your dev center.
127127

128128
### Attach a system-assigned managed identity
129129

130-
To attach a system-assigned managed identity to your dev center:
130+
Attach a system-assigned managed identity to your dev center:
131131

132132
```azurecli
133133
az devcenter admin devcenter update -n <devcenterName> --identity-type SystemAssigned
134134
```
135135

136-
### Give the system-assigned managed identity access to the key vault secret
136+
### Grant the system-assigned managed identity access to the key vault secret
137137

138-
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 (RBAC) or vault access policy. In this quickstart, you use RBAC:
138+
Make sure that the identity has access to the key vault secret that contains the GitHub PAT for accessing your repository. Key vaults support two methods of access: Azure role-based access control (RBAC) and vault access policy. In this quickstart, you use RBAC:
139139

140140
```azurecli
141-
az role assignment create --role "Key Vault Secrets Officer" --assignee <devCenterManagedIdentityObjectID> --scope /subscriptions/<subscriptionID>/resourcegroups/<resourceGroupName/providers/Microsoft.KeyVault/vaults/<keyVaultName>
141+
az role assignment create --role "Key Vault Secrets Officer" --assignee <devCenterManagedIdentityObjectID> --scope /subscriptions/<subscriptionID>/resourcegroups/<resourceGroupName>/providers/Microsoft.KeyVault/vaults/<keyVaultName>
142142
```
143143

144144
## Add a catalog to the dev center
145145

146-
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.
146+
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 grants your development teams access to the templates and allows them to quickly create consistent environments.
147147

148148
In this quickstart, you attach a GitHub repository that contains samples created and maintained by the Azure Deployment Environments team.
149149

@@ -160,7 +160,7 @@ You can use this [sample catalog](https://github.com/Azure/deployment-environmen
160160
161161
1. Navigate to your repository, select **<> Code**, and then copy the clone URL.
162162
1. Make a note of the branch that you're working in.
163-
1. Take a note of the folder that contains your environment definitions.
163+
1. Make a note of the folder that contains your environment definitions.
164164

165165
:::image type="content" source="media/how-to-create-configure-dev-center/github-info.png" alt-text="Screenshot that shows the GitHub repo with branch, copy URL, and folder highlighted." lightbox="media/how-to-create-configure-dev-center/github-info.png":::
166166

@@ -173,11 +173,11 @@ You can use this [sample catalog](https://github.com/Azure/deployment-environmen
173173
echo $SECRETID
174174
```
175175

176-
1. Add the catalog.
176+
1. Add the catalog:
177177

178178
```azurecli
179179
# Sample catalog example
180-
REPO_URL="https://github.com/Azure/deployment-environments.git"
180+
REPO_URL="<clone URL that you copied earlier>"
181181
az devcenter admin catalog create --git-hub path="/Environments" branch="main" secret-identifier=$SECRETID uri=$REPO_URL -n <catalogName> -d <devcenterName>
182182
```
183183

@@ -205,7 +205,7 @@ Use an environment type to help you define the different types of environments y
205205

206206
## Next steps
207207

208-
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.
208+
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, go to the next quickstart:
209209

210210
> [!div class="nextstepaction"]
211211
> [Create and configure a project by using the Azure CLI](how-to-create-configure-projects.md)

0 commit comments

Comments
 (0)