Added other Preview limitations

Author: RoseHJM

articles/dev-box/how-to-configure-customization-imaging.md

@@ -126,6 +126,9 @@ To build an image from a customization file, follow these steps:
 1. Track progress 
 
    :::image type="content" source="./media/how-to-configure-customization-imaging/customizations-image-build-progress-small.png" alt-text="Screenshot of the Image definition page, with the image status Progressing highlighted." lightbox="./media/how-to-configure-customization-imaging/customizations-image-build-progress.png":::  
+
+> [!IMPORTANT]
+> When optimizing your image definition into an image, a dev box is created to run your customization file and generate an image. During this process, this Dev Box is connected to a virtual network managed by Microsoft, and tasks that require access to on premise resources might fail. Support for specifying a custom network for an image build is coming soon. 
  
 When the build completes successfully, the dev box pool automatically uses the image for new dev boxes. You don't need to do any extra configuration to assign the image to the pool. You can now create dev boxes from the pool, and the customizations are applied to each dev box.
 

articles/dev-box/how-to-create-customization-tasks-catalog.md

@@ -61,6 +61,8 @@ To configure your Key Vault secrets for use in your yaml configurations,
 1. Ensure that your dev center project's managed identity has the Key Vault Reader role and Key Vault Secrets User role on your key vault.
 
 1. Grant the Secrets User role for the Key Vault secret to each user or user group who should be able to consume the secret during the customization of a dev box. The user or group granted the role must include the managed identity for the dev center, your own user account, and any user or group who needs the secret during the customization of a dev box.
+ 
+For more information on using key vault secrets in a customization file, see [Clone a private repository using a customization file](how-to-write-customization-file.md#clone-a-private-repository-using-a-customization-file).
 
 ## Attach a catalog 
 You can attach a catalog to a project to make tasks accessible to the developer team. To attach a catalog to a project, follow the steps in this article: [Add and configure a catalog from GitHub or Azure Repos](../deployment-environments/how-to-configure-catalog.md).

articles/dev-box/how-to-write-customization-file.md

@@ -51,7 +51,11 @@ tasks:
       directory: C:\Workspaces
 ```
 
-There are two ways to use a customization file: team customizations which apply to a whole team, and individual customizations which apply to a single dev box.
+There are two ways to use a customization file: individual customizations which apply to a single dev box, and team customizations which apply to a whole team.
+
+### Individual Customization files
+- Contain tasks that are applied when a dev box is created.
+- Uploaded by the developer when they create a dev box.
 
 ### Team Customization files
 - Contain tasks that are applied when a dev box is created.
@@ -61,9 +65,11 @@ There are two ways to use a customization file: team customizations which apply
 - Are uploaded to the repository that hosts your catalog.
 - Are automatically used when you create a dev box from a configured pool. 
 
-### Individual Customization files
-- Contain tasks that are applied when a dev box is created.
-- Uploaded by the developer when they create a dev box.
+> [!IMPORTANT]
+> Image definitions can only use Dev Box marketplace images as base images. To get a list of images that your DevCenter has access to, use this az cli command:
+> ```bash
+> az devcenter admin image list --dev-center-name CustomizationsImagingHQ --resource-group TeamCustomizationsImagingRG --query "[].name"
+> ```
 
 ## Create a customization file