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/deployment-environments/how-to-create-configure-dev-center.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ To create and configure a dev center in Azure Deployment Environments:
71
71
az devcenter admin devcenter create -n <devcenterName>
72
72
```
73
73
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:
75
75
76
76
```output
77
77
{
@@ -100,13 +100,13 @@ You need an Azure Key Vault to store the GitHub personal access token (PAT) that
100
100
1. Create a key vault:
101
101
102
102
```azurecli
103
-
# Change the name to something Globally unique
103
+
# Use a globally unique name
104
104
az keyvault create -n <keyvaultName>
105
105
```
106
106
107
107
> [!NOTE]
108
108
> 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.
110
110
111
111
1. Assign yourself the Key Vault Secrets Officer RBAC role:
112
112
@@ -121,29 +121,29 @@ You need an Azure Key Vault to store the GitHub personal access token (PAT) that
121
121
122
122
## Attach an identity to the dev center
123
123
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).
125
125
126
126
In this quickstart, you configure a system-assigned managed identity for your dev center.
127
127
128
128
### Attach a system-assigned managed identity
129
129
130
-
To attach a system-assigned managed identity to your dev center:
130
+
Attach a system-assigned managed identity to your dev center:
131
131
132
132
```azurecli
133
133
az devcenter admin devcenter update -n <devcenterName> --identity-type SystemAssigned
134
134
```
135
135
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
137
137
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:
139
139
140
140
```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>
142
142
```
143
143
144
144
## Add a catalog to the dev center
145
145
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.
147
147
148
148
In this quickstart, you attach a GitHub repository that contains samples created and maintained by the Azure Deployment Environments team.
149
149
@@ -160,7 +160,7 @@ You can use this [sample catalog](https://github.com/Azure/deployment-environmen
160
160
161
161
1. Navigate to your repository, select **<> Code**, and then copy the clone URL.
162
162
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.
164
164
165
165
:::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":::
166
166
@@ -173,11 +173,11 @@ You can use this [sample catalog](https://github.com/Azure/deployment-environmen
@@ -205,7 +205,7 @@ Use an environment type to help you define the different types of environments y
205
205
206
206
## Next steps
207
207
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:
209
209
210
210
> [!div class="nextstepaction"]
211
211
> [Create and configure a project by using the Azure CLI](how-to-create-configure-projects.md)
0 commit comments