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/dev-box/how-to-customize-dev-box-setup-tasks.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,17 +198,18 @@ Creating new tasks in a catalog allows you to create customizations tailored to
198
198
199
199
You can use secrets from your Azure Key Vault in your yaml configurations to clone private repositories, or with any custom task you author that requires an access token.
200
200
201
-
To configure your Key Vault secrets for use in your yaml configurations, follow these steps:
201
+
To configure your Key Vault secrets for use in your yaml configurations,
202
202
203
-
1. Ensure that your dev center project’s managed identity has the Key Vault Reader role and Key Vault Secrets User role on your key vault.
204
-
1. Learn how to [Configure a managed identity for a dev center](../deployment-environments/how-to-configure-managed-identity.md#configure-a-managed-identity-for-a-dev-center).
205
-
1. Learn how to [Grant the managed identity access to the key vault secret](../deployment-environments/how-to-configure-managed-identity.md#grant-the-managed-identity-access-to-the-key-vault-secret).
203
+
1. Ensure that your dev center project’s managed identity has the Key Vault Reader role and Key Vault Secrets User role on your key vault.
206
204
207
-
1. Grant the Secrets User role to each user or user group who should be able to consume this secret during the customization of a dev box.
205
+
1. Grant the Secrets User role to each user or user group who should be able to consume the secret during the customization of a dev box. The user or group includes the managed identity for the dev center, your own user account, and any user or group who need the secret during the customization of a dev box.
208
206
209
-
1. Grant the Secrets User role to your own user account.
207
+
For more information, see:
208
+
- Learn how to [Configure a managed identity for a dev center](../deployment-environments/how-to-configure-managed-identity.md#configure-a-managed-identity-for-a-dev-center).
209
+
- Learn how to [Grant the managed identity access to the key vault secret](../deployment-environments/how-to-configure-managed-identity.md#grant-the-managed-identity-access-to-the-key-vault-secret).
210
210
211
-
You can reference the secret in your yaml configuration in this format, using the git-clone task as an example:
211
+
212
+
You can reference the secret in your yaml configuration in the following format, using the git-clone task as an example:
0 commit comments