Extended message, added to more articles.

Author: RoseHJM

articles/dev-box/concept-dev-box-deployment-guide.md

@@ -13,6 +13,8 @@ ms.custom: template-concept
 
 # Microsoft Dev Box deployment guide
 
+[!INCLUDE [note-build-2025](includes/note-build-2025.md)]
+
 In this article, you learn about the process, configuration options, and considerations for planning and implementing a Microsoft Dev Box deployment.
 
 The deployment of Microsoft Dev Box requires the [involvement of different roles](#organizational-roles-and-responsibilities) within your organization. Each role has particular responsibilities and requirements. Before you start the implementation of Microsoft Dev Box, it's important to [collect all requirements](#define-your-requirements-for-microsoft-dev-box) from the different roles, as they influence the configuration settings for the different components in Microsoft Dev Box. Once you have outlined your requirements, you can then go through the [deployment steps to roll out Dev Box](#deploy-microsoft-dev-box) in your organization.

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

@@ -14,6 +14,8 @@ ms.date: 02/05/2025
 
 # Configure imaging for Dev Box team customizations
 
+[!INCLUDE [note-build-2025](includes/note-build-2025.md)]
+
 Using a customization file simplifies the creation of dev boxes for your team. With dev box customizations, you can create a shared team customization by creating a file called an *image definition*. Creating a reusable image from this image definition optimizes customizations and saves time during dev box creation. In this article, you learn how to configure a pool to use an image definition and build reusable images for your development teams.
 
 To configure imaging for Microsoft Dev Box team customizations, enable project-level catalogs and configure catalog sync settings for the project. Then, attach a catalog that contains a definition file to your project, configure a dev box pool to use an image definition, and verify that the customizations apply to a new dev box. When the customizations apply correctly, you can choose to build a reusable image, which makes the creation of new dev boxes quicker.

articles/dev-box/how-to-hibernate-your-dev-box.md

@@ -14,6 +14,8 @@ ms.topic: how-to
 
 # Hibernate a dev box in Microsoft Dev Box
 
+[!INCLUDE [note-build-2025](includes/note-build-2025.md)]
+
 In this article, you learn how to hibernate and resume a dev box in Microsoft Dev Box. 
 
 Hibernation is a power-saving state that saves your running applications to your hard disk and then shuts down the virtual machine (VM). When you resume the VM, all your previous work is restored. 

articles/dev-box/overview-what-is-microsoft-dev-box.md

@@ -14,6 +14,8 @@ adobe-target: true
 
 # What is Microsoft Dev Box?
 
+[!INCLUDE [note-build-2025](includes/note-build-2025.md)]
+
 Microsoft Dev Box gives developers self-service access to ready-to-code cloud workstations called *dev boxes*. You can configure dev boxes with tools, source code, and prebuilt binaries that are specific to a project, so developers can immediately start work. You can create cloud development environments for your developer teams by using a customized image, or a preconfigured image from Azure Marketplace, complete with Visual Studio already installed. 
 
 If you're a developer, you can use multiple dev boxes in your day-to-day workflows. Access and manage your dev boxes through the developer portal.