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-configure-customization-tasks.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,17 +17,6 @@ ms.date: 02/06/2026
17
17
18
18
When you create tasks for Microsoft Dev Box customizations, you can define specific actions for your dev boxes to help ensure a consistent and efficient development environment. Creating new tasks in a catalog allows you to define reusable components tailored to your development teams and add guardrails around the configurations that are possible. This article guides you through creating a catalog for customization tasks, adding tasks, and attaching the catalog to a dev center or project.
19
19
20
-
## Prerequisites
21
-
22
-
To complete the steps in this article, you must have:
23
-
24
-
- A dev center configured with a dev box project.
25
-
- An existing catalog in GitHub or Azure Repos.
26
-
27
-
For permissions required to configure customizations, see [Permissions for customizations](concept-what-are-dev-box-customizations.md#permissions-for-customizations).
28
-
29
-
## What are tasks?
30
-
31
20
A task performs a specific action, like installing software. Each task consists of one or more PowerShell scripts, along with a task.yaml file that provides parameters and defines how the scripts run. You can also include a PowerShell command in the task.yaml file.
32
21
33
22
You can store a collection of curated tasks in a catalog attached to your dev center, with each task in a separate folder. Dev Box supports using a GitHub repository or an Azure Repos repository as a catalog. Dev Box scans a specified folder of the catalog recursively to find task definitions.
@@ -42,6 +31,15 @@ Microsoft provides a quickstart catalog to help you get started with customizati
42
31
- Configure applications like installing Visual Studio extensions.
43
32
- Run PowerShell scripts.
44
33
34
+
## Prerequisites
35
+
36
+
To complete the steps in this article, you must have:
37
+
38
+
- A dev center configured with a dev box project.
39
+
- An existing catalog in GitHub or Azure Repos.
40
+
41
+
For permissions required to configure customizations, see [Permissions for customizations](concept-what-are-dev-box-customizations.md#permissions-for-customizations).
42
+
45
43
## Create tasks in a catalog
46
44
47
45
Tasks, such as installing software or running scripts, are organized into a catalog. You create and manage tasks in a catalog, define new tasks, and attach your catalog to a dev center. With Microsoft's quickstart catalog, you can get started with common tasks like installing software, deploying DSC, cloning repositories, and configuring applications.
0 commit comments