Skip to content

Commit 922b2bc

Browse files
author
RoseHJM
committed
Updating steps
1 parent bf812ae commit 922b2bc

File tree

2 files changed

+17
-20
lines changed

2 files changed

+17
-20
lines changed

articles/dev-box/how-to-customizations-connect-resource-repository.md

Lines changed: 16 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom:
1212
- ai-seo-date:05/10/2025
1313
- ai-gen-description
1414
ms.topic: how-to
15-
ms.date: 07/18/2025
15+
ms.date: 07/22/2025
1616
---
1717

1818
# Connect to Azure resources or clone private repositories by using customizations
@@ -85,11 +85,9 @@ To learn how to let trusted Microsoft services bypass the firewall, see [Configu
8585

8686
## Authenticate to Azure resources with service principals
8787

88-
You can use service principals to authenticate to Azure resources in your customizations. Service principals are a secure way to access Azure resources without using user credentials.
88+
Service principals let you securely authenticate to Azure resources exposing user credentials. You can create a Service Principal, assign the necessary role assignments, and use it to authenticate in a customization tasks, hydrating its credentials at customization time using the existing secrets feature. The next section explains the steps.
8989

90-
Create a Service Principal with required role assignments, and use it to log in in a customizations tasks, hydrating its credentials at customization time using the existing secrets feature. The next section provides the necessary steps.
91-
92-
1. Create a service principal in Azure Active Directory (Azure AD) and assign it the necessary roles for the resources you want to access.
90+
1. Create a service principal in Azure Active Directory (Azure AD), and assign it the necessary roles for the resources you want to use.
9391

9492
The output is a JSON object containing the service principal's *appId*, *displayName*, *password*, and *tenant*, which are used for authentication and authorization in Azure automation scenarios.
9593

@@ -111,7 +109,6 @@ Create a Service Principal with required role assignments, and use it to log in
111109
Now you can authenticate in customization tasks, hydrating the service principal password from the Key Vault at customization time.
112110

113111
### Example: Download a file from Azure Storage
114-
115112
The following example shows you how to download a file from storage account. The YAML snippet defines a Dev Box customization that performs two main tasks:
116113

117114
1. Installs the Azure CLI using the winget package manager.
@@ -142,36 +139,35 @@ The following example shows you how to download a file from storage account. The
142139
--auth-mode login
143140
```
144141

145-
This setup allows automated, secure access to Azure resources during Dev Box provisioning, without exposing credentials in the script.
142+
This setup lets you automate secure use of Azure resources during Dev Box provisioning without exposing credentials in the script.
146143

147144
### Example: Download an artifact from Azure DevOps
148-
You can also download build artifacts from Azure DevOps (ADO) by using a service principal for authentication. To do this, add the service principal's Application ID (appId) as a user in your Azure DevOps organization and assign it to the **Readers** group. This provides the necessary permissions to access build artifacts.
145+
Download build artifacts from Azure DevOps (ADO) by using a service principal for authentication. Add the service principal's Application ID (appId) as a user in your Azure DevOps organization, and assign it to the **Readers** group. This step gives the necessary permissions to use build artifacts.
149146

150-
Once configured, you can use the service principal credentials in your customization tasks to authenticate and download artifacts securely from Azure DevOps.
147+
After you configure these steps, use the service principal credentials in customization tasks to authenticate and download artifacts securely from Azure DevOps.
151148

152-
#### Add a service principal to Azure DevOps organization
149+
#### Add a service principal to an Azure DevOps organization
153150

154151
To add a service principal to your Azure DevOps organization:
155152

156-
1. Sign in to your Azure DevOps organization and open **Organization settings**.
157-
1. In the left menu, select **Users**.
153+
1. Sign in to your Azure DevOps organization, and open **Organization settings**.
154+
1. In the menu, select **Users**.
158155
1. On the **Users** page, select **Add users**.
159156
1. In the **Add new users** dialog, enter the following information:
160157

161-
:::image type="content" source="media/how-to-customizations-connect-resource-repository/dev-box-customizations-devops-add-user.png" alt-text="Screenshot of the Add new users dialog in Azure DevOps, showing fields for user email, access level, project, and group assignment." lightbox="media/how-to-customizations-connect-resource-repository/dev-box-customizations-devops-add-user.png":::
158+
:::image type="content" source="media/how-to-customizations-connect-resource-repository/dev-box-customizations-devops-add-user.png" alt-text="Screenshot of the Add new users dialog in Azure DevOps, showing fields for user email, access level, project, and group assignment." lightbox="media/how-to-customizations-connect-resource-repository/dev-box-customizations-devops-add-user.png":::
162159

163-
- **Users**: Service principal's Application ID (appId) as the user email.
164-
- **Access Level**: Select **Basic**.
165-
- **Add to project**: Select the project where you want to add the service principal.
166-
- **Azure DevOps groups**: Assign the service principal to the **Readers** group.
160+
- **Users**: Enter the service principal's Application ID (appId) as the user email.
161+
- **Access Level**: Select **Basic**.
162+
- **Add to project**: Select the project where you want to add the service principal.
163+
- **Azure DevOps groups**: Assign the service principal to the **Readers** group.
167164

168165
1. Complete the process to grant the necessary permissions.
169166

170167
For details on how to add users to DevOps organizations, see [Add organization users and manage access](/azure/devops/organizations/accounts/add-organization-users).
171168

172169
## Related content
173170

174-
- [Microsoft Dev Box customizations](concept-what-are-dev-box-customizations.md)
175-
- [Configure Dev Box imaging](how-to-configure-dev-box-imaging.md)
176-
- Learn how to [add and configure a catalog from GitHub or Azure Repos](../deployment-environments/how-to-configure-catalog.md).
171+
- Learn how to [Set and retrieve a secret from Azure Key Vault using the Azure portal](/azure/key-vault/secrets/quick-create-portal).
172+
- Learn how to [Add and configure a catalog from GitHub or Azure Repos](../deployment-environments/how-to-configure-catalog.md).
177173
- Learn how to [Use service principals & managed identities in Azure DevOps](/azure/devops/integrate/get-started/authentication/service-principal-managed-identity).

articles/dev-box/toc.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,7 @@ items:
9191
- name: Configure tasks for customizations
9292
href: how-to-configure-customization-tasks.md
9393
- name: Connect to Azure resources and repositories
94+
displayName: customizations, secrets, Azure Key Vault
9495
href: how-to-customizations-connect-resource-repository.md
9596
- name: Add and Manage Catalogs
9697
href: how-to-configure-catalog.md

0 commit comments

Comments
 (0)