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-customizations-connect-resource-repository.md
+16-20Lines changed: 16 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.custom:
12
12
- ai-seo-date:05/10/2025
13
13
- ai-gen-description
14
14
ms.topic: how-to
15
-
ms.date: 07/18/2025
15
+
ms.date: 07/22/2025
16
16
---
17
17
18
18
# 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
85
85
86
86
## Authenticate to Azure resources with service principals
87
87
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.
89
89
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.
93
91
94
92
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.
95
93
@@ -111,7 +109,6 @@ Create a Service Principal with required role assignments, and use it to log in
111
109
Now you can authenticate in customization tasks, hydrating the service principal password from the Key Vault at customization time.
112
110
113
111
### Example: Download a file from Azure Storage
114
-
115
112
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:
116
113
117
114
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
142
139
--auth-mode login
143
140
```
144
141
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.
146
143
147
144
### 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.
149
146
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.
151
148
152
-
#### Add a service principal to Azure DevOps organization
149
+
#### Add a service principal to an Azure DevOps organization
153
150
154
151
To add a service principal to your Azure DevOps organization:
155
152
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**.
158
155
1. On the **Users** page, select **Add users**.
159
156
1. In the **Add new users** dialog, enter the following information:
160
157
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":::
162
159
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.
167
164
168
165
1. Complete the process to grant the necessary permissions.
169
166
170
167
For details on how to add users to DevOps organizations, see [Add organization users and manage access](/azure/devops/organizations/accounts/add-organization-users).
171
168
172
169
## Related content
173
170
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).
177
173
- Learn how to [Use service principals & managed identities in Azure DevOps](/azure/devops/integrate/get-started/authentication/service-principal-managed-identity).
0 commit comments