Merge pull request #299617 from RoseHJM/mdb-customizations-iteration-2

MDB - Customizations - change individual customizations to user customizations

Author: JillGrant615

.openpublishing.redirection.json

@@ -227,7 +227,7 @@
     },
     {
       "source_path": "articles/databox-online/azure-stack-edge-2301-release-notes.md",
-      "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2301-release-notes",
+      "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2301-release-notes"
     },
     {
       "source_path": "articles/network-watcher/nsg-flow-logs-rest.md",
@@ -2393,7 +2393,7 @@
       "source_path_from_root": "/articles/app-service/manage-disaster-recovery.md",
       "redirect_url": "/azure/architecture/web-apps/guides/multi-region-app-service/multi-region-app-service",
       "redirect_document_id": false
-    },       
+    },
     {
       "source_path_from_root": "/articles/public-multi-access-edge-compute-mec/tutorial-create-vm-using-python-sdk.md",
       "redirect_url": "/previous-versions/azure/public-multi-access-edge-compute-mec/tutorial-create-vm-using-python-sdk",
@@ -6875,49 +6875,49 @@
       "redirect_document_id": false
     },
     {
-         "source_path": "articles/storage/files/storage-files-enable-soft-delete.md",
+      "source_path": "articles/storage/files/storage-files-enable-soft-delete.md",
       "redirect_url": "/azure/storage/files/storage-files-prevent-file-share-deletion",
       "redirect_document_id": false
-     },
-     {
+    },
+    {
       "source_path": "articles/defender-for-iot/organizations/release-notes-archive.md",
       "redirect_url": "/azure/defender-for-iot/organizations/release-notes-ot-monitoring-sensor-archive",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-portal.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-powershell.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-cli.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-template.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-terraform.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/nat-gateway/quickstart-create-nat-gateway-bicep.md",
       "redirect_url": "/azure/nat-gateway/quickstart-create-nat-gateway",
-       "redirect_document_id": false
-     },
-     {
+      "redirect_document_id": false
+    },
+    {
       "source_path": "articles/defender-for-iot/organizations/eiot-sensor.md",
       "redirect_url": "/azure/defender-for-iot/organizations/concept-enterprise",
       "redirect_document_id": false
     }
   ]
-}
+}

articles/dev-box/.openpublishing.redirection.dev-box.json

@@ -94,6 +94,11 @@
       "source_path_from_root": "/articles/dev-box/how-to-write-customization-file.md",
       "redirect_url": "/azure/dev-box/how-to-write-image-definition-file",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/dev-box/how-to-write-individual-customization-file.md",
+      "redirect_url": "/azure/dev-box/how-to-write-user-customization-file",
+      "redirect_document_id": false
     }
   ]
 }

articles/dev-box/concept-what-are-team-customizations.md

@@ -7,7 +7,7 @@ ms.service: dev-box
 ms.custom:
   - ignite-2024
 ms.topic: concept-article
-ms.date: 04/18/2025
+ms.date: 05/09/2025
 
 #customer intent: As a Dev Center Admin or Project Admin, I want to understand how to use Dev Box customizations so that I can create efficient, ready-to-code configurations for my development teams.
 ---
@@ -24,9 +24,9 @@ Dev Box customizations let you:
 - Enforce organizational security policies.
 - Ensure consistency across dev boxes.
 
-Microsoft Dev Box offers two ways to use customizations. Team customizations are used to create a shared configuration for a team of developers. Individual customizations are used to create a personal configuration for an individual developer. The following table summarizes the differences between the two types of customizations.
+Microsoft Dev Box offers two ways to use customizations. Team customizations are used to create a shared configuration for a team of developers. User customizations are used to create a personal configuration for an individual developer. The following table summarizes the differences between the two types of customizations.
 
-| Feature                     | Team customizations       | Individual customizations |
+| Feature                     | Team customizations       | User customizations |
 |-----------------------------|---------------------------|---------------------------|
 | **Configure on**            | Dev box pool             | Dev box                   |
 | **Customizations apply to** | All dev boxes in pool    | Individual dev box        |
@@ -50,14 +50,14 @@ User customizations can only use system tasks if the user is an administrator, o
 When you're creating tasks, determine which of them need to run in a system context and which of them can run in a user context (after sign-in). 
 When creating tasks, determine which need to run in a system context and which run in a user context after sign-in.
 
-## Differences between team customizations and individual customizations
+## Differences between team customizations and user customizations
 
-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.
-Developers use individual customizations only for personal settings and apps.
+Individual developers can upload a customization file when creating their dev box to control the development environment. Developers should use user customizations only for personal settings and apps. Tasks specified in the user customization file run only in the user context, after sign-in.
+Developers use user customizations only for personal settings and apps.
 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.
 
 ## How do customizations work?
-Team customization and individual 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.
+Team customization and user 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.
 
 # [Team customizations](#tab/team-customizations)
 ### How do team customizations work?
@@ -76,64 +76,63 @@ When you configure Dev Box team customizations for your organization, careful pl
 To set up your Dev Box service to support team customizations, follow these steps:
 
 1. **Configure your dev center**:
-    a. Enable project-level catalogs.
-    b. Assign permissions for project admins.
+   1. Enable project-level catalogs.
+   1. Assign permissions for project admins.
 
 1. **Decide whether to use a catalog with custom reusable components**:
-    a. **Built-in**:
-    b. Use PowerShell or WinGet statements.
-    c. **Catalog**:
-    d. Host in Azure Repos or GitHub.
-    e. Add tasks.
-    f. Attach to a dev center.
+   1. **Built-in**:
+      1. Use PowerShell or WinGet statements.
+   1. **Catalog**:
+      1. Host in Azure Repos or GitHub.
+      1. Add tasks.
+      1. Attach to a dev center.
 
 1. **Create a customization file**:
-    a. Create a YAML file named `imagedefinition.yaml`.
+   1. Create a YAML file named `imagedefinition.yaml`.
 
 1. **Specify an image in a dev box pool**:
-    a. Create or modify a dev box pool and specify `imagedefinition.yaml` as the image definition.
+   1. Create or modify a dev box pool and specify `imagedefinition.yaml` as the image definition.
 
 1. **Choose how you'll use the image definition**:
-    a. Build the image each time you create a dev box.
-    b. Optimize the image for team customizations.
+   1. Build the image each time you create a dev box.
+   1. Optimize the image for team customizations.
 
 1. **Create a dev box**:
-    a. Use the developer portal to create your dev box from the configured pool.
+   1. Use the developer portal to create your dev box from the configured pool.
 
-For more information, see [Write a team customization file](how-to-write-customization-file.md).
+For more information, see [Write an image definition file for Dev Box team customizations](how-to-write-image-definition-file.md).
 
-# [Individual customizations](#tab/individual-customizations)
-### How do individual customizations work?
-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.  
+# [User customizations](#tab/user-customizations)
+### How do user customizations work?
+Individual developers can attach a YAML-based customization file when creating their dev box to control the development environment. Developers use user customizations only for personal settings and apps.  
 
-:::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":::
+:::image type="content" source="media/concept-what-are-team-customizations/dev-box-user-customizations-workflow.svg" alt-text="Diagram that shows the workflow for Dev Box user customizations, including steps for planning, configuring, and deploying customizations." lightbox="media/concept-what-are-team-customizations/dev-box-user-customizations-workflow.svg":::
 
-#### Configure your Dev Box service for individual customizations
+#### Configure your Dev Box service for user customizations
 
-To set up your Dev Box service to support individual customizations, follow these steps:
+To set up your Dev Box service to support user customizations, follow these steps:
 
 1. **Use a PowerShell and WinGet tasks**:
-    a. Platform supports PowerShell and WinGet.
-    b. No catalog required.
-    c. No further configuration required.
+   1. Platform supports PowerShell and WinGet.
+   1. No catalog required.
+   1. No further configuration required.
 
 1. **Create a customization file**:
-    a. Create a YAML-based customization file.
+   1. Create a YAML-based customization file.
 
 1. **Create a dev box**:
-    a. Use the developer portal to create your dev box from the configured pool.
-    b. Upload and validate your customization file during the dev box creation process.
+   1. Use the developer portal to create your dev box from the configured pool.
+   1. Upload and validate your customization file during the dev box creation process.
 
 1. **Dev box creation**:
-    a. The dev box is created with the specified customizations.
+   1. The dev box is created with the specified customizations.
 
-For more information, see [Write an individual customization file](how-to-write-customization-file.md).
+For more information, see [Write a user customization file for a dev box](how-to-write-user-customization-file.md).
 
 ---
 
 ## Related content
 
 - [Quickstart: Create a dev box by using team customizations](quickstart-team-customizations.md)
-- [Write a customization file for a dev box](how-to-write-customization-file.md)
 - [Configure imaging for Dev Box team customizations](how-to-configure-customization-imaging.md)
 

articles/dev-box/how-to-use-secrets-customization-files.md

@@ -1,6 +1,6 @@
 ---
 title: Use key vault secrets in customization files
-description: Learn how to use Azure Key Vault secrets in team and individual customization files to clone private repositories.
+description: Learn how to use Azure Key Vault secrets in team and user customization files to clone private repositories.
 author: RoseHJM
 ms.author: rosemalcolm
 ms.service: dev-box
@@ -46,9 +46,9 @@ tasks:
       pat: '{{KEY_VAULT_SECRET_URI}}'
 ```
 
-## Use key vault secrets in individual customization files
+## Use key vault secrets in user customization files
 
-To clone a private Azure Repos repository from an individual customization file, you don't need to configure a secret in Azure Key Vault. If you want to clone a private Azure Repos repository from an individual customization file, you don't need to configure a secret in Azure Key Vault. Instead, you can use `{{ado}}` or `{{ado://your-ado-organization-name}}` as a parameter. This parameter fetches an access token on your behalf when you're creating a dev box. The access token has read-only permission to your repository.
+To clone a private Azure Repos repository from a user customization file, you don't need to configure a secret in Azure Key Vault. If you want to clone a private Azure Repos repository from a user customization file, you don't need to configure a secret in Azure Key Vault. Instead, you can use `{{ado}}` or `{{ado://your-ado-organization-name}}` as a parameter. This parameter fetches an access token on your behalf when you're creating a dev box. The access token has read-only permission to your repository.
 
 The `git-clone` task in the quickstart catalog uses the access token to clone your repository. Here's an example:
 

articles/dev-box/how-to-write-image-definition-file.md

@@ -10,7 +10,7 @@ ms.custom:
   - ai-gen-description
   - ai-seo-date:04/18/2025
 ms.topic: how-to
-ms.date: 04/18/2025
+ms.date: 05/09/2025
 
 #customer intent: As a Dev Center Admin or Project Admin, I want to create image definition files so that my development teams can create customized dev boxes.
 ---
@@ -22,9 +22,9 @@ ms.date: 04/18/2025
 
 The Dev Box customizations feature helps you streamline the setup of cloud-based development environments. Getting developers started on a new project or team can be complex and time-consuming. Customizations let you configure ready-to-code workstations with applications, tools, repositories, code libraries, packages, and build scripts. This article guides you through the process of creating, testing, and editing an image definition file for your dev box using Visual Studio Code (VS Code). 
 
-There are two ways to use customizations in Microsoft Dev Box. Team customizations create a shared configuration for a team of developers. Individual customizations create a personal configuration for an individual developer. The following table summarizes the differences between the two types of customizations.
+There are two ways to use customizations in Microsoft Dev Box. Team customizations create a shared configuration for a team of developers. User customizations create a personal configuration for an individual developer. The following table summarizes the differences between the two types of customizations.
 
-| Feature                     | Team customizations       | Individual customizations       |
+| Feature                     | Team customizations       | User customizations       |
 |-----------------------------|---------------------------|---------------------------------|
 | Configure on               | Dev box pool             | Dev box                           |
 | Customizations apply to    | All dev boxes in pool    | Individual dev box                |