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
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,20 +144,24 @@ tasks:
144
144
This setup allows automated, secure access to Azure resources during Dev Box provisioning, without exposing credentials in the script.
145
145
146
146
### Example: Download an artifact from Azure DevOps
147
-
You can also download build artifacts from Azure DevOps (ADO) by using a service principal for authentication. First, add the service principal as a user in your Azure DevOps organization and then assign it to the *Readers* group. This grants the necessary permissions to access build artifacts.
148
-
149
-
- Add the service principal's Application ID (appId) as a user in your Azure DevOps organization.
150
-
- Assign the service principal to the **Readers** group to provide read access to artifacts.
147
+
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.
151
148
152
149
Once configured, you can use the service principal credentials in your customization tasks to authenticate and download artifacts securely from Azure DevOps.
153
150
154
-
To add a service principal to your Azure DevOps organization and the Readers group:
151
+
To add a service principal to your Azure DevOps organization: and the Readers group:
155
152
156
153
1. Go to your Azure DevOps organization settings.
157
-
2. Select **Users** and click **Add users**.
158
-
3. Enter the service principal's Application ID (appId) as the user email.
159
-
4. Assign the user to the **Readers** group.
160
-
5. Complete the process to grant the necessary permissions.
154
+
1. Select **Users** and click **Add users**.
155
+
1. Enter the service principal's Application ID (appId) as the user email.
0 commit comments