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/concept-what-are-team-customizations.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,10 +52,12 @@ When creating tasks, determine which need to run in a system context and which r
52
52
Individual developers can upload a customization file when creating their dev box to control the development environment. Developers should use individual customizations only for personal settings and apps. Tasks specified in the individual customization file run only in the user context, after sign-in.
53
53
Developers use individual customizations only for personal settings and apps.
54
54
Sharing common YAML files among developer teams is inefficient, leads to errors, and violates compliance policies. Dev Box team customizations allow developer team leads and IT admins to preconfigure customization files, eliminating the need for developers to find and upload these files when creating a dev box.
55
-
55
+
56
+
## How do customizations work?
57
+
Team customizationa and indivudual customizations are both YAML-based files that specify a list of tasks to apply when creating a dev box. Select the appropriate tab to learn more about how each type of customization works.
56
58
57
59
# [Team customizations](#tab/team-customizations)
58
-
## How do team customizations work?
60
+
###How do team customizations work?
59
61
60
62
You can use team customizations to define a shared Dev Box configuration for each of your development teams without having to invest in setting up an imaging solution like Packer or Azure virtual machine (VM) image templates. Team customizations provide a lightweight alternative that allows central platform engineering teams to delegate Dev Box configuration management to the teams that use them.
61
63
@@ -66,7 +68,7 @@ When you configure Dev Box team customizations for your organization, careful pl
66
68
67
69
:::image type="content" source="media/concept-what-are-team-customizations/dev-box-customizations-workflow.svg" alt-text="Diagram that shows the workflow for Dev Box team customizations, including steps for planning, configuring, and deploying customizations." lightbox="media/concept-what-are-team-customizations/dev-box-customizations-workflow.svg":::
68
70
69
-
### Configure your Dev Box service for team customizations
71
+
####Configure your Dev Box service for team customizations
70
72
71
73
To set up your Dev Box service to support team customizations, follow these steps:
72
74
@@ -97,14 +99,13 @@ To set up your Dev Box service to support team customizations, follow these step
97
99
98
100
For more information, see [Write a team customization file](how-to-write-customization-file.md).
Individual developers can attach a YAML-based customization file when creating their dev box to control the development environment. Developers use individual customizations only for personal settings and apps.
104
105
105
106
:::image type="content" source="media/concept-what-are-team-customizations/individual-customizations-workflow.png" alt-text="Diagram that shows the workflow for Dev Box individual customizations, including steps for planning, configuring, and deploying customizations." lightbox="media/concept-what-are-team-customizations/individual-customizations-workflow.png":::
106
107
107
-
### Configure your Dev Box service for individual customizations
108
+
####Configure your Dev Box service for individual customizations
108
109
109
110
To set up your Dev Box service to support individual customizations, follow these steps:
0 commit comments